Waydev MCP
Ask Claude. Waydev answers.
Connect Waydev to Claude, Cursor or your internal assistant through MCP. Ask about AI ROI, delivery or agents in plain language and get answers grounded in your engineering data, no dashboard required.
Claude · Waydev MCP
Example
How did our AI investment pay off last quarter?
Querying Waydev MCP: get_metric · ai_cost_per_merged_pr, lead_time_for_changes
AI returned 3.1× last quarter. Payments drove most of the gain; Platform is lagging on cycle time.
The Problem
Leaders live in chat now. Their metrics do not.
Dashboards go unopened
Executives ask questions in Slack and AI assistants, not in BI tools.
Answers need context
Generic assistants guess. They do not know your teams, baselines or AI spend.
Data must stay governed
Pasting exports into chat leaks data and loses access control.
What You Get
Your engineering data, inside the assistants you already use.
How It Works
Live in your stack, not another spreadsheet.
1
Enable MCP
Turn on the Waydev MCP server in your workspace settings.
2
Add it to your assistant
Add the Waydev connector in Claude, Cursor or your MCP client and sign in.
3
Ask anything
Ask about spend, delivery, quality or agents. Waydev returns grounded answers.
Waydev reads engineering metadata through read-only APIs. Source code content is never ingested. Visit the Trust Center
FAQ
Questions engineering leaders ask
Which assistants are supported?
Any MCP client that supports Streamable HTTP. Waydev includes setup for Claude Desktop, Claude Code, Cursor, VS Code with GitHub Copilot, ChatGPT, Codex and Windsurf. Claude Desktop connectors require a Claude Pro, Max, Team or Enterprise plan.
Is data sent to the model provider?
Only the metrics needed to answer the question, as with Waydev’s in-app AI. Data is not used for training.
Do we need to build anything?
No. Setup is a connector and a sign in. Docs are at docs.waydev.co.
Keep Exploring
