What are the prerequisites for using Scout Monitoring MCP?
You need a Scout Monitoring account, an API key (created on the Settings page, not the Agent Key), and Docker installed.
@scoutapp
Basic information
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, a
Add this server to your MCP-compatible client using the configuration below.
{
"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"
}
}
}
}List available Scout APM applications, with optional filtering by last active date
Get individual metric data (response_time, throughput, etc.) for a specific application
Get all endpoints for an application with aggregated performance metrics
Get timeseries metrics for a specific endpoint in an application
Get recent traces for an app filtered to a specific endpoint
Get an individual trace with all spans and detailed execution information
Get recent error groups for an app, optionally filtered by endpoint
Get performance insights including N+1 queries, memory bloat, and slow queries
Scout Monitoring MCP is a locally run MCP server that accesses Scout APM performance and error data via Scout’s API. It provides traces, errors, and line-of-code information to AI assistants for frameworks like Rails, Django, FastAPI, and Laravel.
Use the provided Docker image with your Scout API key. Configure the server in your AI assistant (Cursor, Claude Code, Claude Desktop, VS Code Copilot) by specifying a docker run command with the SCOUT_API_KEY environment variable. Alternatively, run the interactive setup wizard via npx @scout_apm/wizard to guide configuration. The server uses STDIO transport and requires Docker.
You need a Scout Monitoring account, an API key (created on the Settings page, not the Agent Key), and Docker installed.
No. The MCP server will not start without an API key set either in the environment or via a command‑line argument.
Cursor, Claude Code (CLI), Claude Desktop, and VS Code Copilot are supported. A setup wizard automates configuration for these platforms.
Yes. It is recommended to set a generous token limit for MCP output, e.g., `MAX_MCP_OUTPUT_TOKENS=50000`, since the tools can return large responses.

DocuWriter is an AI-powered platform for creating, updating and managing complete, structured documentation for entire codebases. Teams can connect repositories and generate documentation covering architecture, modules,

Automated codebase documentation for GitHub: searchable docs, MCP context for AI agents, doc drift detection, and Friday Cleanup PRs.

Liro connects your AI coding tool (Cursor, Claude Code, VS Code, Windsurf, Codex, Gemini CLI) to 258 production React, TypeScript and Tailwind CSS components. Your agent searches the library, reads each component's props

Local-first credential broker for MCP. AI coding agents (Claude Code, Cursor, Codex…) call APIs, SSH and databases through scoped presets; secrets stay in your OS keychain and never enter the agent's context.

One case file per task — shared by every session, agent and person that touches it. Self-hosted MCP server and live board. MIT.
Comments