Scout Monitoring Mcp

Created By
Scout Monitoring Official8 months ago
Scout Monitoring's local MCP server empowers AI Assistants by integrating application performance and error data directly into their workflows. It allows AI models to access traces, errors with line-of-code information, and performance insights like N+1 queries, slow endpoints, and memory bloat from various frameworks including Rails, Django, and FastAPI. This direct data access enables AI Assistants to identify and suggest fixes for performance problems and errors right within your editor and codebase, significantly enhancing development efficiency and reducing debugging time.
Overview

What is Scout Monitoring MCP?

Scout Monitoring MCP is a local server that integrates application performance and error data into AI Assistants' workflows, enabling them to access detailed performance insights and error traces directly within the development environment.

How to use Scout Monitoring MCP?

To use Scout Monitoring MCP, set up a Scout Monitoring account, obtain an API key, and run the provided Docker image to access performance data. You can also use an interactive setup wizard to configure the server easily.

Key features of Scout Monitoring MCP?

  • Direct integration of performance and error data into AI Assistants.
  • Access to traces, errors with line-of-code information, and performance insights.
  • Support for various frameworks including Rails, Django, and FastAPI.
  • Tools for generating GitHub/GitLab issues and JIRA tickets based on performance data.

Use cases of Scout Monitoring MCP?

  1. Identifying and fixing performance issues in real-time during development.
  2. Generating detailed error reports and insights for better debugging.
  3. Enhancing development efficiency by surfacing performance problems directly in the codebase.

FAQ from Scout Monitoring MCP?

  • What frameworks are supported?

Scout Monitoring MCP supports Rails, Django, FastAPI, and more.

  • Is there a setup wizard?

Yes, an interactive setup wizard is available to simplify configuration.

  • Do I need an API key?

Yes, an API key is required to access Scout Monitoring data.

Server Config

{
  "mcpServers": {
    "scout-apm": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "--env",
        "SCOUT_API_KEY",
        "scoutapp/scout-mcp-local"
      ],
      "env": {
        "SCOUT_API_KEY": "your_scout_api_key_here"
      }
    }
  }
}
Project Info
Created At
8 months ago
Updated At
8 months ago
Author Name
Scout Monitoring Official
Star
-
Language
-
License
-
Category
monitoring

Recommend Servers

View All
Thousand Api

13 hours ago
Mercury X402 Mcp

9 hours ago
GovQL
@Alex Stout

# govql-mcp-server An MCP (Model Context Protocol) server for [GovQL](https://govql.us) — gives AI clients like Claude Desktop, Claude Code, and Cursor direct access to the US Congressional GraphQL API at [api.govql.us/graphql](https://api.govql.us/graphql) without bespoke HTTP wiring. For the design rationale (why FastMCP-Python, the passthrough+curated philosophy, roadmap through v0.4), see [design.md](https://github.com/govql/govql/blob/main/mcp-server/docs/design.md). ## What you can do with it Ask an agent questions like: - *"How did Vermont's two senators vote on the most recent nomination?"* - *"Which legislators in the 118th Congress switched parties during their service?"* - *"Compare Senator Sanders' voting record to Senator Murkowski's on cloture votes in the most recent Congress."* The agent picks the right tool, writes the GraphQL query against the live schema, and parses the response — no manual API wrangling. ## Install The server runs as a per-client subprocess over stdio. Pick your client: ### Claude Desktop Edit `claude_desktop_config.json` (Settings → Developer → Edit Config): ```json { "mcpServers": { "govql": { "command": "uvx", "args": ["govql-mcp-server"] } } } ``` Restart Claude Desktop. The `govql` tools appear in the tools panel. ### Claude Code Add to `.mcp.json` in your project (or `~/.mcp.json` for global): ```json { "mcpServers": { "govql": { "command": "uvx", "args": ["govql-mcp-server"] } } } ``` ### Cursor Settings → MCP → Add Server. Use the same `command` / `args` as above. ### Other clients Any MCP-compatible client that supports stdio servers will work. The command is `uvx govql-mcp-server` with no required arguments. ## Tools | Tool | Purpose | |---|---| | `execute_graphql` | Run any GraphQL query against the GovQL endpoint. Returns the result plus an `last_ingest` timestamp so the agent can reason about data freshness. | | `list_types` | Returns the names and kinds of every type in the GovQL schema. Optional `kind` filter (`"OBJECT"`, `"INPUT_OBJECT"`, `"ENUM"`, etc.) to narrow further. Start here when you don't know what's queryable. | | `describe_type` | Returns one type's full details — fields, arg signatures, input fields, enum values. Call after `list_types` to learn the shape of a specific type before writing a query. | ## Configuration All env vars are optional — the package is zero-config for end users. | Env var | Default | Purpose | |---|---|---| | `GOVQL_ENDPOINT` | `https://api.govql.us/graphql` | Endpoint to query. Override to point at a local dev stack. | | `GOVQL_TIMEOUT_MS` | `30000` | Per-request HTTP timeout. | | `LOG_LEVEL` | `INFO` | Logging level. Logs go to stderr only (stdout is reserved for the MCP transport). | ## Limits (enforced by the upstream API) - Max query depth: 10 - Max query complexity: ~10 billion points (`first: N` multiplies child cost by N — keep page sizes reasonable on deeply nested queries) - Rate limit: 100 requests / 60 s per source IP A depth or complexity violation surfaces as a GraphQL `errors` entry in the tool response so the agent can adjust and retry. ## Data freshness Every `execute_graphql` response includes a `last_ingest` ISO timestamp. Vote data refreshes hourly; legislator data refreshes daily. ## Status Version 0.1.0 ships three foundational tools: a GraphQL passthrough (`execute_graphql`) and two narrow schema-discovery tools (`list_types`, `describe_type`). Curated higher-level tools (`find_legislator`, `get_voting_record`, `compare_voters`, etc.) are planned for subsequent releases — see [design.md](https://github.com/govql/govql/blob/main/mcp-server/docs/design.md) for the roadmap. ## Links - [GovQL project site](https://govql.us) - [GraphQL API](https://api.govql.us/graphql) - [Source / issues](https://github.com/govql/govql)

2 days ago