MCP tools for AI agents
Wystan ships an MCP server that Cursor, Claude Code, Cline, and Aider call to get precise codebase context — the same data your engineering leaders see, never your raw source. Your agent stops guessing about your code.
What your agent gets
Function-level accuracy. The agent pulls the feature map and reads only the symbols that matter, instead of grepping whole directories.
Who owns this code and where the bug-fix churn concentrates — one tool call, not a Slack thread.
Which features a diff touches, the co-changed-but-missing files, and a low/medium/high risk level — surfaced before the PR.
Production errors (Sentry) and usage (PostHog) joined to each feature automatically — your agent sees what's actually breaking.
Set it up
The MCP is a hosted, OAuth-secured server. Claude Code, Claude Desktop, Cursor (1.0+), VS Code (1.101+) and Codex CLI speak remote MCP natively — add the URL, sign in once in the browser, done. In Claude Code:
claude mcp add --transport http wystan https://app.wystan.ai/api/mcpFor Cursor that's ~/.cursor/mcp.json:
{
"mcpServers": {
"wystan": { "url": "https://app.wystan.ai/api/mcp" }
}
}Deployment modes (Hosted / Local / VPC) are covered on the Getting started page; runtime joins on Integrations.
The 13 tools
All read-only. They read precomputed scan fields — the engine does the work at scan time, the server just serves it. The same 13 names exist in every deployment mode.
list_featuresEvery feature with name, display name, path count, health, and coverage.find_featureFuzzy-match a single feature by name or alias; returns its paths, flows, health, coverage, impact, and description.get_feature_filesThe file paths that make up a feature.get_flow_filesThe file paths that make up one flow inside a feature.get_repo_summaryRepo-level counts (features, flows, files), top hotspots, average coverage, and the scan timestamp.get_hotspotsThe highest bug-fix-ratio / churn files or features (limit defaults to 5).get_feature_ownersOwners and bus factor for a feature.analyze_change_impactBlast radius for a set of changed files — which features and flows they touch, co-changed-but-missing files, and recommendations. Engine-free path overlap.get_regression_riskA low / medium / high / critical risk level from bug-fix ratio weighted by path overlap of the touched features.find_symbols_in_flowPrecise functions and classes per file for a flow, with line ranges and deeplinks (falls back to file paths when symbols are absent).find_symbols_for_featureThe same symbol-level detail, aggregated across all of a feature's flows.get_feature_errorsProduction errors mapped to a feature via Sentry (hosted); returns a graceful unavailable result on local MCP.get_feature_pageviewsPostHog traffic and usage for a feature (hosted); graceful unavailable result on local MCP.Works with your agents
Any MCP-compatible client — Cursor, Claude Code, Cline, Aider, Continue, and Claude.ai web (hosted mode). Drop the server into the config, restart the agent, and start asking questions that previously needed a senior engineer.
Always fresh
After every push an incremental scan re-maps only what changed, so the agent's context never goes stale — and PR branches get their own current scan, separate from main. The tools return precomputed, feature-grained answers, so the agent reads the symbols that matter instead of grepping whole directories.