portfolio-drift-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BEACON_JWT | No | Required for audit with adapter='beacon' and apply with dry_run=false | |
| DRIFT_MODEL | No | Anthropic model ID used by the analyzer | claude-sonnet-4-6 |
| GITHUB_TOKEN | No | Optional. Raises GitHub rate limit from 60/hr to 5000/hr | |
| BEACON_API_URL | No | The URL of the Beacon API | https://beacon.danhle.net |
| DRIFT_STALE_DAYS | No | Number of days after which a project is considered stale | 180 |
| ANTHROPIC_API_KEY | Yes | Required for all audit tools |
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 |
|---|---|
| audit_portfolio_driftB | Audit every project in the portfolio against its GitHub repo. |
| audit_single_projectA | Audit one project by id. Faster than the full audit (~10 seconds). |
| apply_drift_patchesA | Apply curated drift suggestions to Beacon (HITL). |
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 has a clearly distinct purpose: full audit, single project audit, and applying patches. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern with snake_case (audit_portfolio_drift, audit_single_project, apply_drift_patches), making them predictable.
With only 3 tools, the server is tightly scoped to its purpose—auditing drift and applying fixes—without unnecessary bloat or deficiency.
The tool surface covers the full lifecycle: comprehensive audit, targeted audit, and patching. No obvious gaps for the stated domain.