slm-mesh
by qualixar
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SLM_MESH_HOST | No | Broker bind address. Use 0.0.0.0 for remote access. | 127.0.0.1 |
| SLM_MESH_PORT | No | Broker HTTP port | 7899 |
| SLM_MESH_DEAD_MS | No | Time before stale peer removed | 60000 |
| SLM_MESH_WS_PORT | No | WebSocket server port | 7900 |
| SLM_MESH_DATA_DIR | No | Data directory | ~/.slm-mesh/ |
| SLM_MESH_STALE_MS | No | Time before peer marked stale | 30000 |
| SLM_MESH_DISCOVERY | No | Enable mDNS auto-discovery on LAN | true |
| SLM_MESH_HEARTBEAT_MS | No | Heartbeat interval in milliseconds | 15000 |
| SLM_MESH_LOCK_TTL_MIN | No | Default lock timeout in minutes | 10 |
| SLM_MESH_SHARED_SECRET | No | Bearer token for WebSocket auth. Must match on all machines for multi-machine setup. |
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 | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/qualixar/slm-mesh'
If you have feedback or need assistance with the MCP directory API, please join our Discord server