klaxon
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STATE_SECRET | No | Secret for Slack state (generated with `openssl rand -hex 32`). | |
| KLAXON_USE_MCP | No | Set to '1' to load tools via MCP stdio instead of in-process. | 0 |
| PUBLIC_BASE_URL | No | Public base URL (e.g., ngrok HTTPS origin) for Slack OAuth. | |
| ANTHROPIC_API_KEY | No | API key for Anthropic (optional; without it the agent echoes). | |
| TOKEN_ENCRYPTION_KEY | No | Key for encrypting Slack tokens (generated with Fernet). |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_issuesA | Search incident issues by text, kind, status, or severity. |
| get_issueA | Get full details for an issue by public_id (e.g. INC-0001). |
| issue_statsA | Aggregate issue counts by status, kind, severity, or source. Optional since/until are ISO-8601 timestamps. |
| create_issueB | Create a new incident issue. labels is comma-separated; features_json is a JSON object. |
| update_issueC | Update fields on an existing issue. |
| update_issue_statusC | Change an issue's status and optionally add a comment. |
| add_commentC | Add a comment to an issue. |
| simulate_upstream_ingestC | Simulate an upstream system creating an issue (source=upstream). |
| create_github_issueA | Simulate opening a GitHub issue for an incident (logged as a side effect only). |
| list_side_effectsB | List simulated side effects, optionally filtered by issue public_id. |
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 10 tools
Most tools have distinct purposes, but create_issue, create_github_issue, and simulate_upstream_ingest could be confused without careful reading. Descriptions clarify the differences, so ambiguity is limited.
Most names follow a verb_noun pattern (search_issues, get_issue, create_issue), but issue_stats breaks the pattern by using a noun phrase instead of get_issue_stats. Otherwise naming is consistent and predictable.
Ten tools cover the core incident issue workflow without redundancy, staying within a reasonable and focused scope.
The toolset covers create, read, search, update, status changes, comments, and simulated integrations. It lacks an explicit delete/archive operation, but that may be intentionally excluded from the domain.