pulsemcp Safe content atomic mcp-remote

AppSignal

This MCP server integrates with AppSignal's application performance monitoring platform through their GraphQL API, providing comprehensive incident management and log analysis capabilities for debugging production applications. Built by PulseMCP using TypeScript with the MCP SDK, it offers 15 tools including exception incident tracking, anomaly detection, performance monitoring, and flexible log searching with severity filtering and time-based queries. The implementation features dynamic tool management where app selection tools (get_apps, select_app_id) enable the full monitoring toolkit, supports both environment variable configuration for locked deployments and interactive app selection for multi-application monitoring, and includes robust error handling with pagination support for large datasets. Particularly valuable for DevOps teams investigating production issues, developers debugging application errors, and building AI assistants that need real-time access to application health metrics and detailed incident analysis without context switching between monitoring dashboards.

Cognium trust score

50%

Tier

Unverified

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: devops-ci
Source: PulseMCP
Repository: github.com/pulsemcp/mcp-servers/tree/HEAD/experimental/appsignal
Author type: human
Updated: 2026-04-29

View source Find related skills

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

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"