logodev-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FASTMCP_LOG_LEVEL | No | Log level for FastMCP internals and app loggers (DEBUG / INFO / WARNING / ERROR). | INFO |
| LOGODEV_MCP_KV_STORE_URL | No | Persistent-state backend URL for pvl-core subsystems. | file:///data/state |
| FASTMCP_ENABLE_RICH_LOGGING | No | Set to 'false' for plain / structured JSON log output. | true |
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_server_infoA | Report wrapper and upstream version info for logodev-mcp. Returns server_name, server_version, core_version (fastmcp-pvl-core), and (when configured) an upstream version block. Useful for verifying a deployment matches the expected build. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| summarize | Summarize ``context`` in one paragraph. See https://gofastmcp.com/servers/prompts#prompt-arguments for the full signature surface. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| status | Service status resource — JSON-serialisable dict. Templated resources take path parameters in the URI; static resources don't. See https://gofastmcp.com/servers/resources#templates for the full pattern. |
TDQS
Scored across 1 tool
There is only one tool, so there are no overlapping purposes or risk of an agent selecting the wrong tool. The tool is clearly distinct by default.
The single tool name 'get_server_info' follows a clear verb_noun pattern. However, with only one tool there is no real pattern established to judge consistency against.
A single tool that only reports version information is far below what the server name 'logodev-mcp' implies the server should offer. The tool surface feels almost empty, not a coherent developer toolset.
The server provides no functional capabilities beyond version inspection—a utility that is really just a health or metadata check. For a server named 'logodev-mcp', the tool surface has no apparent workflow, resources, or actions that would actually accomplish the intended purpose.