appsignal-mcp
AppSignal MCP
Documentation
AppSignal MCP
A Model Context Protocol (MCP) server for AppSignal monitoring API integration. This server allows AI assistants to directly query and fetch error and performance data from AppSignal through the MCP protocol.
Features
- Fetch details about specific error or performance samples
- Search for errors, performance samples, or both with flexible filters
- Integration with AppSignal's Error and Performance Monitoring APIs
Prerequisites
- Bun runtime
- AppSignal account and API token
- Application ID from your AppSignal dashboard
Installation
# Clone the repository
git clone https://github.com/pauldub/appsignal-mcp.git
cd appsignal-mcp
# Install dependencies
bun installConfiguration
Create a `.env` file in the root directory with your AppSignal credentials:
# Server configuration
PORT=3000
LOG_LEVEL=info
# AppSignal configuration
APPSIGNAL_API_TOKEN=your-api-tokenUsage
Starting the Server
# Run the server
bun start
# Development mode with auto-reload
bun dev
# Run tests
bun test
# Build a standalone executable
bun run buildCLI Options
appsignal-mcp --appsignal-api-token your-tokenAvailable options:
- `--appsignal-api-token ` - AppSignal API token
- `--log-level ` - Logging level (debug, info, warn, error)
- `--port ` - Server port number
MCP Tools
1. get_sample
Gets details about a specific sample by ID (error or performance).
Parameters:
- `sampleId` (string, required): The AppSignal sample ID
- `appId` (string, required): The AppSignal application ID
2. search_samples
Searches for samples in an application with optional filters.
Parameters:
- `appId` (string, required): The AppSignal application ID
- `sample_type` (string, optional): Type of samples to search - "all", "errors", or "performance" (defaults to "errors")
- `exception` (string, optional): Filter by exception name (e.g., "NoMethodError") - only applicable for error samples
- `action_id` (string, optional): Filter by action name (e.g., "BlogPostsController-hash-show")
- `since` (string/number, optional): Start timestamp in UTC (timestamp or ISO format)
- `before` (string/number, optional): End timestamp in UTC (timestamp or ISO format)
- `limit` (number, optional): Maximum number of samples to return (defaults to 10)
- `count_only` (boolean, optional): Only return the count, not the samples
Claude Integration
To use this MCP server with Claude, create a `.mcp.json` file in your Claude Code workspace:
{
"mcpServers": {
"appsignal-mcp": {
"type": "stdio",
"command": "bun",
"args": [
"run",
"start"
],
"env": {
"APPSIGNAL_API_TOKEN": "your-api-token"
}
}
}
}License
MIT
Frequently asked questions
What is appsignal-mcp?
appsignal-mcp is AppSignal MCP
How do I install appsignal-mcp?
Open the GitHub repository and follow its README. Most MCP servers are added to your client's MCP config, then called by your agent.
Is appsignal-mcp open source?
Yes — it is hosted on GitHub at https://github.com/pauldub/appsignal-mcp and has 5 stars.
Related MCP tools
Model Context Protocol Servers
The Open-Source Multimodal AI Agent Stack: Connecting Cutting-Edge AI Models and Agent Infra
A MCP for Claude Desktop / Claude Code / Windsurf / Cursor to build n8n workflows for you
MCP server to provide Figma layout information to AI coding agents like Cursor
The world's best AI personal assistant for email. Open source app to help you reach inbox zero fast.
Instant is the best backend for AI-coded apps. You get auth, permissions, storage, presence, and streams — everything you need to ship apps your users will love.
Run your own MCP server? See who uses it and what to fix.
Measure it with TrackMCP