mcp-multisource
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_ROLE | No | Access control role: 'viewer', 'contributor', or 'admin'. Unrecognised values fail closed to 'viewer'. | viewer |
| MAX_RETRIES | No | Maximum number of retries for retryable errors. | |
| GITHUB_TOKEN | No | GitHub fine-grained personal access token. Requires at least Contents: read, Issues: read+write, Metadata: read, and Pull requests: read permissions. | |
| NOTION_TOKEN | No | Notion integration secret. The integration must be explicitly shared with at least one page in Notion. | |
| ALLOWED_REPOS | No | Comma-separated list of GitHub repositories allowed for this deployment. Empty means unscoped. Matching is case-insensitive. | |
| LINEAR_API_KEY | No | Linear personal API key. Do not prefix it with 'Bearer'. | |
| ALLOWED_LINEAR_TEAMS | No | Comma-separated list of Linear team keys or IDs allowed for this deployment. Empty means unscoped. | |
| ALLOWED_NOTION_PAGES | No | Comma-separated list of Notion page IDs allowed for this deployment. Dashes are stripped before comparison. Empty means unscoped. | |
| HTTP_TIMEOUT_SECONDS | No | HTTP timeout in seconds for outbound requests to source APIs. | |
| BREAKER_RESET_SECONDS | No | Cooldown in seconds before an open circuit breaker transitions to half-open. |
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 |
|---|---|
| release_readinessB | Cross-source snapshot: open GitHub PRs/issues for a repo, matching Notion specs, and Linear tracked work. Returns partial results with a |
| system_healthC | Per-source health: reachable, circuit state, rate budget, last error. |
| access_policyA | Show this session's role, capabilities and resource scopes. |
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 3 tools
Each tool addresses a completely distinct concern: release_readiness provides aggregated cross-source data, system_health reports on source connectivity/status, and access_policy describes permissions. There is no overlap or ambiguity between their purposes.
All tool names follow the same snake_case noun_noun pattern (release_readiness, system_health, access_policy), which is predictable and readable. No mixed conventions or vague verbs appear.
Three tools is a well-scoped count for a focused multisource status server. Each tool earns its place and the set feels neither bloated nor too thin.
The server covers the core lifecycle of reading cross-source release readiness, monitoring source health, and checking access. A minor gap is the lack of a tool to query a specific source in detail or perform any mutating action, but agents can work around this with release_readiness and system_health.