portfolio-drift-mcp
Wraps portfolio-drift-agent as MCP tools, letting LLM clients audit a portfolio of projects against GitHub conversationally.
README
portfolio-drift-mcp
MCP server that wraps portfolio-drift-agent — lets LLM clients (Claude Desktop, Claude Code, custom agents) audit a portfolio of projects against GitHub conversationally instead of round-tripping through a terminal.
Why this exists
If you maintain a portfolio of projects (a resume, a profile site, an internal project tracker) the source records drift the moment the underlying repos evolve. portfolio-drift-agent audits that drift via CLI. This server exposes the same audit as MCP tools so an LLM agent can call it mid-conversation:
"Before I push this PR, audit Beacon's own record on my portfolio. If the tech stack is missing anything that just shipped, propose patches and dry-run them."
The model can call audit_single_project, read the response, then call apply_drift_patches with dry_run=true — all without a human typing a command.
Tools
| Tool | Args | Purpose |
|---|---|---|
audit_portfolio_drift |
adapter?, limit?, model? |
Full audit. Use limit for quick scans — the full ~25-project audit takes 2-3 min. |
audit_single_project |
project_id, adapter?, model? |
Single project, ~10 seconds. |
apply_drift_patches |
patches[], dry_run=true |
HITL apply. Dry-run prints intent; pass dry_run=false to actually mutate Beacon. |
Every tool returns a structured envelope:
{ "ok": true, ...payload }
// or
{ "ok": false, "error_kind": "config|network|not_found|upstream", "error": "..." }
error_kind lets the calling LLM branch deterministically (re-prompt for missing config vs. retry on network vs. give up on not-found) without parsing tracebacks.
Install
pip install git+https://github.com/odanree/portfolio-drift-mcp
Then register in your MCP client (Claude Code example):
claude mcp add portfolio-drift python -m drift_mcp.server \
--env ANTHROPIC_API_KEY=sk-ant-... \
--env BEACON_JWT=... \
--env BEACON_API_URL=https://beacon.danhle.net \
--env GITHUB_TOKEN=ghp_...
Claude Desktop config (in ~/Library/Application Support/Claude/claude_desktop_config.json or the Windows equivalent):
{
"mcpServers": {
"portfolio-drift": {
"command": "python",
"args": ["-m", "drift_mcp.server"],
"env": {
"ANTHROPIC_API_KEY": "sk-ant-...",
"BEACON_JWT": "...",
"BEACON_API_URL": "https://beacon.danhle.net",
"GITHUB_TOKEN": "ghp_..."
}
}
}
}
Environment
| Var | Default | When required |
|---|---|---|
BEACON_API_URL |
https://beacon.danhle.net |
Always |
BEACON_JWT |
— | Audit with adapter="beacon"; apply with dry_run=false |
ANTHROPIC_API_KEY |
— | All audit tools |
GITHUB_TOKEN |
(unauth) | Optional. Raises GitHub rate limit 60/hr → 5000/hr — strongly recommended for non-trivial portfolios. |
DRIFT_MODEL |
claude-sonnet-4-6 |
Anthropic model id used by the analyzer |
DRIFT_STALE_DAYS |
180 |
Project is flagged stale if its last commit is older than this |
Env is read on tool invocation, not at server start — missing config returns a structured config error rather than crashing the server.
Tests
pip install -e .[dev]
pytest
13 tests cover: missing env → structured config error, unknown adapter rejection, full audit happy path with mocked Anthropic + Beacon + GitHub via respx, drift counting, single-project not_found path, dry-run vs apply branching, and patch validation. No network calls in CI.
License
MIT — see LICENSE.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.