omni-kit-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KIT_MCP_NAME | No | Name for the MCP server instance. | |
| KIT_MCP_BUILTINS | No | Set to '0' to hide built-in tools (run_python, reload_tools). | 1 |
| KIT_MCP_NAMESPACE | No | Comma-separated allowlist of namespaces to expose. If set, only tools from these namespaces are visible. | |
| OMNI_KIT_MCP_BIND | No | Bind address for the bridge (default localhost). | localhost |
| OMNI_KIT_MCP_HOST | No | Host address for the front-end gateway. | localhost |
| OMNI_KIT_MCP_PORT | No | Port for the bridge. Auto-discovered when exactly one bridge is running; set to pin a process. | auto |
| KIT_MCP_TOOL_PATHS | No | Comma-separated list of paths to tool packages (used with KIT_MCP_TOOL_MODULES). | |
| KIT_MCP_INSTRUCTIONS | No | Custom instructions for the MCP server. | |
| KIT_MCP_TOOL_MODULES | No | Comma-separated list of tool package modules to register per-launch. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| refresh_toolsA | Re-discover the bridge registry and register any new tools (use after the bridge's reload_tools, after enabling a project, or after Kit restarts). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no risk of confusion. The tool's purpose is clearly described and distinct from any hypothetical other tools.
The single tool uses a clear snake_case verb_noun pattern ('refresh_tools'), which is consistent and readable. No other tools exist to create inconsistency.
The server provides only one tool, which is too few for a meaningful tool surface. The tool, while not trivial, suggests a broader scope (e.g., managing a registry) that is not supported.
The server lacks essential operations for managing a tool registry, such as listing or removing tools. The single 'refresh' tool leaves significant gaps that would cause agent failures.