buslet
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BUSLET_DIR | No | Absolute path to the buslet state directory. Defaults to `<cwd>\.buslet`; `buslet mcp-config` pins this to an absolute path so the MCP server connects to the correct state directory regardless of the client's working directory. | <cwd>\.buslet |
| BUSLET_NAME | Yes | Identity/name for this agent on the buslet bus. MCP tools have no `from` parameter, so this env var determines who the server speaks as. | |
| BUSLET_TOKEN | No | Optional agent token, e.g. from `buslet auth add NAME`, used to bind the MCP server to a specific identity and scope. If omitted, the admin token in `bus.json` is used. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo issues