Project-scoped MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| project_mcp_statusA | Report the discovered project manifest, server names, connection state and tool counts. Does not return credentials. |
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 a single tool there is no possibility of tool selection confusion, and its purpose (reporting manifest, server names, connection state, tool counts) is clearly stated.
The single name project_mcp_status uses a clean namespaced snake_case convention, though it is noun-based rather than the more typical verb_noun pattern.
One tool is too thin even for a project-scoping/discovery server; the surface exposes only a read-only status report with no capability to act on the discovered servers.
The server reports connection state and tool counts but offers no tools to connect to, list, or invoke the discovered project servers, leaving users at a dead end after status inspection.