smart-glitchtip-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Pino log level (logs go to stderr). | info |
| GLITCHTIP_URL | No | Default GlitchTip instance URL. Required in stdio mode. | |
| MCP_HTTP_PATH | No | Endpoint path when MCP_TRANSPORT=http. | /mcp |
| MCP_HTTP_PORT | No | HTTP port when MCP_TRANSPORT=http. | 8080 |
| MCP_TRANSPORT | No | Transport mode. Use 'stdio' for local agents or 'http' for a shared deployment. | stdio |
| MCP_AUTH_TOKEN | No | Shared secret for HTTP clients that do not bring their own GlitchTip token. Required in HTTP mode when GLITCHTIP_TOKEN is set. | |
| GLITCHTIP_TOKEN | No | Default GlitchTip API token. If set in HTTP mode, MCP_AUTH_TOKEN must also be set. | |
| GLITCHTIP_TOOLSETS | No | Comma-separated list of enabled toolsets. Use 'all' to enable all toolsets. | organizations,issues,events,projects |
| GLITCHTIP_READ_ONLY | No | Set to 'false' to enable tools that change or delete data. | true |
| MCP_RESPONSE_BUDGET | No | Maximum size of a tool result in characters; longer results are truncated. | 20000 |
| GLITCHTIP_TIMEOUT_MS | No | Timeout in milliseconds for requests to GlitchTip. | 15000 |
| GLITCHTIP_DEFAULT_ORG | No | Default organization slug. | |
| GLITCHTIP_ALLOWED_URLS | No | Comma-separated list of allowed GlitchTip origins for the X-GlitchTip-Url header. Empty means only GLITCHTIP_URL is allowed. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| whoamiA | Show which GlitchTip instance and user this server is acting as, the instance version, and the scopes of the token in use. Call this first when a tool fails with a permission error. Needs no scope. |
| list_organizationsA | List organizations the token can see, with slug, name and creation date. Scope: org:read, org:write or org:admin. |
| get_organizationA | Get one organization: slug, name, its projects and teams (counts and slugs), and the access scopes you hold in it. Scope: org:read, org:write or org:admin. |
| list_organization_environmentsA | List environment names used in an organization's events (e.g. production, staging). Scope: org:read, org:write or org:admin. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct concern: whoami handles identity/permissions, list_organizations provides an overview, get_organization drills into a single org's details, and list_organization_environments focuses on a specific attribute. There is no meaningful overlap or ambiguity between them.
All tools use snake_case and follow a clear verb_noun pattern (list_*, get_*). whoami is a standard, recognizable exception that still fits the command-style naming. The convention is consistent and predictable.
With only 4 tools, the server is tightly scoped to read-only organization exploration. Each tool adds distinct value without bloat, and the count is well within the ideal range for a focused MCP server.
The surface covers the essential read paths: identity check, list organizations, retrieve a single organization, and list environments. Missing mutation (create/update/delete) and deeper project/team detail tools, but the server appears intentionally read-only for this niche. Minor gaps exist but agents can complete basic workflows.