Overview
MCP is an open protocol that allows AI assistants to interact with external tools and data sources. The Whawit MCP server exposes eight tools that give AI assistants full access to:- Project knowledge base search
- DevOps analysis and log querying
- Incident details and correlated analyses
- AI-optimized prompts for fixing issues
Hosted Server
Whawit provides a hosted MCP server that requires no local installation:| Endpoint |
|---|
https://mcp.whawit.ai/sse |
Quick Setup
- Cursor
- Claude Desktop
- Windsurf
Add to
~/.cursor/mcp.json:Getting Your API Key
Generate your API key from the Whawit web app:- Go to app.whawit.ai
- Navigate to Settings > User Settings
- Generate a new API key
Available Tools
The MCP server exposes eight tools for AI assistants:whawit_context_search
Search the project knowledge base for relevant context about architecture, business logic, and implementation details.The search query to find relevant context.
The project URN to search in (e.g.,
urn:project:abc123).Types of contexts to search:
repo, project, user, other. Defaults to all.Maximum number of results to return. Range: 1-5.
Search for how authentication works in project urn:project:abc123
whawit_devops_analysis
Analyze logs, metrics, and system health from connected observability providers.What to analyze (e.g., “redis errors”, “API failures”, “high latency”).
The project URN to analyze.
Time range start (e.g.,
15m, 1h, 24h).Time range end.
Output verbosity:
concise or detailed.Check for errors in the last 15 minutes in project urn:project:abc123
whawit_project_info
Get information about a project including its integrations, contexts, and configuration.The project URN to get info for.
whawit_list_projects
List all available projects for the authenticated user. This tool takes no parameters.whawit_get_analysis_full
Get complete analysis data with full JSON payload and formatted markdown.The URN of the analysis to fetch (e.g.,
urn:history:abc123).Output format:
markdown, json, or both.Include raw log events in output.
Maximum output length in characters.
whawit_get_incident_full
Get full incident details with optional correlated analysis.The project URN to fetch incidents from.
Specific incident URN to fetch.
Filter by severity:
critical, high, medium, low. Gets first matching open incident.Include the correlated analysis if available.
whawit_generate_fix_prompt
Generate an AI-ready prompt for fixing issues identified in an analysis.The URN of the analysis to generate a fix prompt for.
Focus area:
code, infrastructure, or all.whawit_codebase_analysis_prompt
Generate a prompt for analyzing a codebase based on project context.The project URN to analyze.
Optional specific query to focus the analysis on.
Include architecture/overview contexts.
MCP Resources
The server also exposes projects as MCP resources:- Project details (name, description, URN)
- Connected providers
- Available contexts with titles and types
Authentication
The MCP server uses API key authentication via theX-API-Key header:
Transport Protocols
The Whawit MCP server supports two transport protocols:| Protocol | Endpoint | Use Case |
|---|---|---|
| SSE (Server-Sent Events) | /sse | Traditional MCP clients |
| StreamableHTTP | /mcp | Modern clients like Cursor |
Example Workflows

Using Whawit MCP tools in Cursor to analyze incidents
Investigating an Incident
-
Ask Claude to list your projects:
“List my Whawit projects”
-
Get incident details:
“Get the latest critical incident from project urn:project:abc123”
-
Generate a fix prompt:
“Generate a fix prompt for the incident analysis”
- Let Claude implement the fix based on the context
Searching Documentation
“Search the project knowledge base for how the payment processing flow works in urn:project:payments”
Running DevOps Analysis
“Analyze Redis connection errors in the last 30 minutes for urn:project:backend”
Troubleshooting
Tools not appearing in Claude/Cursor
Tools not appearing in Claude/Cursor
- Verify your MCP configuration file syntax is valid JSON
- Restart Claude Desktop or Cursor after configuration changes
- Check that the access token is valid and not expired
- Ensure the MCP server URL is reachable from your network
Authentication errors
Authentication errors
- Verify your API key is correct
- Ensure the
X-API-Keyheader is set correctly - Generate a new API key from Settings > User Settings if needed
Project not found errors
Project not found errors
- Verify the project URN format is correct (
urn:project:...) - Ensure you have access to the project in Whawit
- Run
whawit_list_projectsto see available projects

