AppSignal
Official AppSignal MCP server that provides AI assistants with access to AppSignal's application performance monitoring platform through a proxy architecture that forwards requests to AppSignal's hosted API endpoints. Built by AppSignal using TypeScript and the Model Context Protocol SDK, the implementation acts as a local proxy server that handles API key authentication and forwards MCP requests to https://appsignal.com/api/mcp, supporting tools, prompts, and resources for monitoring application performance, error tracking, and system metrics. The proxy design allows developers to integrate AppSignal's APM capabilities into their AI workflows through stdio communication while maintaining secure API access, serving teams building monitoring dashboards, developers requiring programmatic access to application performance data, and AI assistants needing real-time insights into application health and performance metrics.
Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately.
View full trust & usage report →Metadata
- Version
- 1.0.0
- Skill type
- atomic
- Execution layer
- mcp-remote
- Category
- ai-ml
- Source
- PulseMCP
- Repository
- github.com/appsignal/appsignal-mcp
- Author type
- human
- Updated
- 2026-04-25
Use via MCP
Resolve AppSignal from your agent
Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.
One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.
claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp --scope user for --scope project to commit it to .mcp.json.