aha-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for SSE transport | 3000 |
| LOG_LEVEL | No | Logging level (debug, info, warn, error) | info |
| TRANSPORT | No | Transport type (stdio or sse) | stdio |
| AHA_DOMAIN | Yes | Your Aha! domain (e.g., yourcompany.aha.io) | |
| AHA_API_TOKEN | Yes | Your Aha! API token |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_recordA | Get an Aha! feature or requirement by reference number |
| get_pageC | Get an Aha! page by reference number with optional relationships |
| search_documentsC | Search for Aha! documents |
| create_featureB | Create a new feature in Aha! |
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 clearly targets a different resource or action: get_record for features/requirements, get_page for pages, search_documents for broader search, and create_feature for creation. There is slight overlap in that search_documents could return records/pages, but the retrieval purposes are distinct.
All tool names follow a consistent verb_noun pattern with lowercase and underscores: get_record, get_page, search_documents, create_feature. This makes the set predictable and easy to navigate.
Four tools is well-suited for a focused server that provides basic read, search, and create operations. There is no unnecessary bloat, and every tool serves a clear purpose.
The server covers reading records and pages, searching, and creating features, but lacks update/delete operations and support for creating other record types like requirements or pages. This leaves notable gaps for full lifecycle management.