Spyglass AI MCP Server
Enables LLMs to query telemetry data via the Spyglass AI agent, providing intelligent insights about application performance, errors, and bottlenecks.
README
Spyglass AI MCP Server
The Spyglass AI MCP server provides a simple interface for LLMs to query the Spyglass AI agent. The agent analyzes your telemetry data and provides intelligent insights about application performance, errors, and bottlenecks.
To install the MCP server for Cursor click the button below. It should open Cursor and prompt you to add your API Key.
Alternatively, add the following to your ~/.cursor/mcp.json file (create it if you need to) and substitute your Spyglass API Key. Then restart Cursor to apply the change.
{
"mcpServers": {
"spyglass-ai": {
"command": "uvx",
"args": ["spyglass-mcp"],
"env": {
"SPYGLASS_API_KEY": "your-key-here"
}
}
}
}
Note that you need to have uv installed first, see the docs for that here
Available Tools
call_spyglass_agent
Calls the Spyglass AI agent with a natural language query about your telemetry data.
Parameters:
query(string, required): Natural language query about your application's telemetry data
Example queries:
- "What are the slowest endpoints in the last hour?"
- "Show me all errors in the checkout service"
- "Which services have the highest error rate?"
- "What's causing high latency in my API?"
- "How many requests has my app had in the last day?"
Returns:
- Natural language analysis of the telemetry data
Configuration
Environment Variables
| Variable | Required | Default | Description |
|---|---|---|---|
SPYGLASS_API_KEY |
Yes | N/A | API Key for authentication with Spyglass agent |
SPYGLASS_AGENT_ENDPOINT |
No | https://agent.spyglass-ai.com |
Agent endpoint URL (useful for local testing) |
Command Line Arguments
| Argument | Required | Default | Description |
|---|---|---|---|
--endpoint |
No | https://agent.spyglass-ai.com |
Spyglass agent endpoint URL |
--transport |
No | stdio |
Transport type (stdio or http) |
--port |
No | 8000 |
Port for HTTP transport |
Example: Using with an MCP Client
import asyncio
from fastmcp import Client
client = Client("http://localhost:8000/mcp")
async def analyze():
async with client:
result = await client.call_tool("call_spyglass_agent", {
"query": "What are the slowest endpoints?"
})
print(result)
asyncio.run(analyze())
Logging
The MCP server logs to both stderr (captured by Cursor) and a file for debugging:
Log file location:
~/.spyglass/logs/mcp-server-YYYYMMDD.log
View logs in real-time:
tail -f ~/.spyglass/logs/mcp-server-$(date +%Y%m%d).log
The logs include:
- Server startup and configuration
- Incoming queries and responses
- API call details (with truncated tokens for security)
- Error messages and stack traces
Development
Prerequisites
- Python 3.11 or higher
- uv package manager
Setup
- Clone the repository and navigate to the project directory:
cd spyglass-mcp
- Install dependencies:
uv sync
This will create a virtual environment and install all required dependencies.
- Copy the example environment file and configure your API key:
cp env.example .env
# Edit .env and add your SPYGLASS_API_KEY
Running Locally
Run the MCP server in stdio mode (default):
uv run spyglass-mcp
Run with a custom endpoint (useful for testing against a local agent):
uv run spyglass-mcp --endpoint http://localhost:8080
Run in HTTP transport mode:
uv run spyglass-mcp --transport http --port 8000
Running Tests
Run all tests:
uv run pytest
Run tests with verbose output:
uv run pytest -v
Run a specific test file:
uv run pytest tests/test_mcp_server.py
Run tests with coverage:
uv run pytest --cov=spyglass_mcp --cov-report=term-missing
Building
Build the package for distribution:
uv build
This will create wheel and source distribution files in the dist/ directory.
Project Structure
spyglass-mcp/
├── .github/
│ └── workflows/
│ └── publish.yaml
├── src/
│ └── spyglass_mcp/
│ ├── __init__.py
│ └── main.py
├── tests/
│ ├── __init__.py
│ ├── conftest.py
│ └── test_mcp_server.py
├── CHANGELOG.md
├── env.example
├── LICENSE
├── pyproject.toml
├── README.md
└── uv.lock
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.