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
There is only one tool, so there is no risk of selecting the wrong tool; its purpose is clearly scoped to status reporting.
The single tool uses a consistent snake_case, prefixed name in a clear verb_noun-style pattern; with only one tool, no inconsistency is present.
A single tool is very thin for a server named Project-scoped MCP; it provides only status reporting with no companion operations for managing or using project-scoped servers.
The surface is limited to status reporting; there are no tools to list projects, connect to or invoke project-scoped MCP servers, or refresh discovery, leaving significant operational gaps if the domain extends beyond diagnostics.