MCP Server
Meet Typo MCP Server - your engineering intelligence, connected directly to your local AI tools.
Typo MCP Server lets you integrate your data directly into your workflow. Instead of switching tabs to navigate multiple dashboards, you can query your metrics, diagnose issues, and build reports without ever leaving your local AI assistant.
Whether you’re keeping an eye on cycle times, identifying stuck tickets, or extracting contributor trends, the MCP Server connects your Typo metrics to your conversational AI - so insights are always right where you work.
🔍 What can Typo MCP Server do?
The MCP Server empowers your local AI assistant to pull live engineering metrics on demand. You can use it for:
Metric Queries: Ask your AI assistant about cycle times, team performance, or active blockers. Every response pulls straight from your Typo metrics.
On-Demand Context: Identify delivery risks instantly. Surface long PR wait times, stuck tickets, or unresolved incidents so you can unblock your team faster.
Custom Reporting: Turn conversational queries into structured dashboards. Extract specific repo or contributor trends, refine them, and export the data wherever it needs to go.
Example prompts:
Not sure where to start? Try asking your AI assistant specific questions like:
"Create an AI effectiveness report for my team for the last month"
"Are there any stuck tickets or long PR wait times we need to unblock today?"
"Show me a summary of team performance and active blockers for the current sprint."
"Create a monthly report for all teams for all productivity metrics"
"Identify unresolved incidents that are posing a delivery risk right now."
The MCP Server uses your existing Typo data. It doesn’t add new data; it seamlessly bridges what’s already there directly to your preferred local AI tool.
⚙️ How to use Typo MCP Server
Connect: Configure the Typo MCP Server with your local AI assistant (like Claude Desktop) using your Typo credentials.
Ask: Type your question directly into your local AI tool just like you normally would.
Diagnose & Build: Review the pulled Typo metrics to diagnose active issues, or ask the AI to format the data into structured reports and exports.
Refine: Need to narrow it down? Ask a follow-up question to filter by specific repositories, tags, or contributors.
💡 Pro Tip: Be specific! Mentioning a specific repository, team name, or time range (e.g., "last 30 days") helps your AI assistant fetch and format the most precise data for your reports.
Security & Privacy
Typo MCP Server acts as a secure bridge between your Typo data and your local AI tools, maintaining the highest standards of data privacy and security. Your engineering metrics are queried securely and remain entirely under your control.
Important Notes
Data Source: The MCP Server pulls directly from your existing Typo metrics. It does not create new data; it simply surfaces your current cycle times, PRs, and delivery risks in your local environment.
Access: Your ability to query data via the MCP Server is governed by your assigned roles and permissions within Typo.
Contextual AI: Because the data is pulled directly into your local AI tool, you can seamlessly combine Typo insights with other local context your AI assistant has access to.
Need help? If a setup step isn't working, a result doesn't look right, or you're unsure how to configure your local AI tools, reach out to us via Live Chat or our Slack Channel. We are here to help you get the most out of your engineering intelligence! 🚀
Last updated