Aha! MCP server

What the model can do

Aha! Roadmaps: workspaces (products), features with status, release and assignee, ideas with status and votes, releases, epics, and comments on features and ideas. Can create, update and delete features, epics and ideas, promote an idea, add to-dos, and add, edit or delete comments.

Reads

• aha_list_productsAha! workspaces (products and product lines): id, reference prefix, name, type and link.
• aha_list_featuresAha! features: reference, name, workflow status, assignee, release, dates and link.
• aha_get_featureOne Aha! feature by id or reference (APP-12): name, status, assignee, release, epic, dates and its description (truncated).
• aha_list_ideasAha! ideas: reference, name, workflow status, vote count and workspace.
• aha_list_releasesReleases in one Aha! workspace: reference, name, start and release dates, whether it is the parking lot, and link.
• aha_list_epicsEpics in one Aha! workspace: reference, name, created date and link.
• aha_list_commentsComments on one Aha! feature or idea (internal comments), oldest first as Aha! returns them: author name, date and text (truncated).

Acts, when you ask

These change something in Aha!. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• aha_add_feature_commentAdds a comment to an Aha! feature, posted as the API key's user.
• aha_add_idea_commentAdds an internal (team) comment to an Aha! idea, posted as the API key's user.
• aha_add_epic_commentAdds a comment to an Aha! epic, posted as the API key's user.
• aha_update_commentReplaces the text of one Aha! comment (by its numeric id, from aha_list_comments).
• aha_delete_commentPermanently deletes one Aha! comment by its numeric id.
• aha_create_featureCreates a feature in one Aha! release (release id or reference from aha_list_releases), as the API key's user.
• aha_update_featureChanges the given fields of one Aha! feature: name, description (replaced), workflow status, assignee, release (moves it), epic or dates.
• aha_delete_featurePermanently deletes one Aha! feature, with its requirements and comments.
• aha_create_ideaCreates an idea in one Aha! workspace, visible to the team only (not submitted to an ideas portal).
• aha_update_ideaChanges the given fields of one Aha! idea: name, description (replaced), workflow status or assignee.
• aha_promote_ideaPromotes one Aha! idea to a new feature or epic in the given release, linking the two.
• aha_delete_ideaPermanently deletes one Aha! idea, with its votes and comments.
• aha_create_epicCreates an epic in one Aha! release, as the API key's user.
• aha_update_epicChanges the given fields of one Aha! epic: name, description (replaced), workflow status, assignee or dates.
• aha_delete_epicPermanently deletes one Aha! epic.
• aha_create_todoAdds a to-do to one Aha! feature, epic, release, initiative or idea, assigned to the given people (Aha! users by email), who may be notified.

Connect it

First connect Aha! on Dashboard → Connections, then add Memtro to your client once. The Aha! tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Aha! connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › What is the status of the export feature?
• › Which features are in the next release?
• › What are our most popular ideas right now?
• › Add a comment to APP-12 saying the design review is done.
• › Move APP-12 to the July release

Questions

Is this an official Aha! MCP server?

No. It is Memtro's MCP server with Memtro's Aha! connector behind it: the connector reads Aha! through its API with the credentials you connect on Dashboard → Connections, and Aha! publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Aha!?

Only when you ask, and only what it has been granted: add a comment to a feature; add an internal comment to an idea; add a comment to an epic; edit or delete a comment; create a feature in a release; update a feature's name, status, assignee, release or dates; create an idea in a workspace; update an idea's name, description, status or assignee; promote an idea to a feature or epic; create an epic in a release, or update one; add a to-do to a feature, epic, release, initiative or idea; permanently delete a feature, epic or idea. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Work management

• Clio Manage MCP server
• Linear MCP server
• Jira MCP server
• Asana MCP server
• monday.com MCP server
• Airtable MCP server