LSD
- typescript
3
GitHub Stars
typescript
Language
4 months ago
First Indexed
3 weeks ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
You can run and connect to the LSD MCP server to extend your client with LSD-based capabilities. This server uses a dynamic tool system called trips to teach the MCP client new skills, connect to an account, and expose MCP endpoints that you can use from your MCP client or registry.
How to use
To use the LSD MCP server, you connect your MCP client to one or more endpoints that expose LSD functionality. Start with the remote MCP endpoint to access the official LSD server, then optionally run a local stdio server to host a local instance. Authentication is managed via your account credentials, which you provide either through a configuration file or environment variables. You can also publish and interact with LSD trips to extend the MCP client’s capabilities.
How to install
Prerequisites you need locally include Node.js and a modern JavaScript runtime. You will configure and run the LSD MCP server using the following steps.
# Install Node.js if you do not have it yet
# On macOS with Homebrew
brew install node
# On Debian/Ubuntu
sudo apt-get install -y nodejs npm
# Verify installations
node -v
npm -v
Next, set up authentication so the MCP server can access your LSD account. You have two options:
{
"user": "<you@email.domain>",
"password": "<api_key>"
}
Option A: Use a configuration file in your home directory named .lsd with your email and API key.
# Create the config file in your home directory
cat > ~/.lsd << 'JSON'
{
"user": "you@example.com",
"password": "YOUR_API_KEY"
}
JSON
Option B: Set environment variables for your authentication when starting the MCP client.
export LSD_USER='you@example.com'
export LSD_PASSWORD='YOUR_API_KEY'
If you choose the environment variable approach, ensure these variables are accessible to the process running the MCP client.
Additional configuration and startup options
You can connect to an MCP registry orPulse to locate and configure servers. The LSD server can be accessed via the official Pulse endpoint, and you can also run a local stdio server alongside it for development.
// Example of a local stdio configuration to run the LSD MCP server
{
"type": "stdio",
"name": "lsd",
"command": "node",
"args": ["/<path>/<to>/mcp/build/index.js"]
}
From source
You can access an MCP server configuration example that shows how to wire a local stdio server to the MCP framework.
{
"mcpServers": {
// other MCP servers configured here...
"lsd": {
"command": "node",
"args": [
"/<path>/<to>/mcp/build/index.js"
]
}
}
}
Example of usage
This section provides practical patterns for using LSD MCP: how to interact with the server, extract LSD programs, and publish trips that extend client capabilities.
Extending capabilities with LSD
To teach the MCP client a new skill, you publish an LSD trip. A trip is a published module containing an LSD program that augments the MCP client’s behavior.
From the Bicycle browser, you can derive LSD by using the click language. Activate it with the transcriber icon or by pressing Command+k (Ctrl+k on Linux/Windows). This lets you interactively select repeating containers and fields, then edit aliases and publish the resulting LSD.
From the workbench, you can edit the generated LSD to publish a trip that describes the new capability.
Extending capabilities with TypeScript
You can leverage the internetdata SDK to bridge with the web. Start a new project using the create-your-internet scaffolding, which provides a quick path to building MCP-enabled integrations.
$ yarn create your-internet
$ npm create your-internet
Available tools
trip
A published module containing an LSD program that teaches or extends MCP client capabilities.
pluck
Interactively select repeating containers and fields in the Bicycle browser to derive LSD programs.
publish_trip
Publish an LSD trip to expose a new capability to MCP clients.
create_your_internet
Bootstrap a new Internet data integration workflow using the SDK scaffolding.