Semurg
Officialby One-Semurg
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SEMURG_AUTH | No | Alternative place for the token in the Claude Desktop configuration, where the mcp-remote bridge is launched with --header "Authorization:${SEMURG_AUTH}". Set it to the value "Bearer <token>" with your node's API token in place of <token>. | |
| SEMURG_API_TOKEN | No | The API token stored on your node. Used when connecting Claude Code or another MCP client: the header is sent as "Authorization: Bearer ${SEMURG_API_TOKEN}" to the node's streamable HTTP endpoint at /v1/mcp (a fresh node serves http://127.0.0.1:4000/v1/mcp; behind your own TLS proxy use its https address). Claude Code reads the token from this environment variable when it starts. |
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 recent community issues