Connect Aha! to Claude Code

Make Claude create features and move releases forward in Aha!. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Aha! to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Aha!, you add a Aha! MCP server: a small hosted service that exposes Aha!'s data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Aha! account. No API keys pasted into config files.

claude mcp add --transport http aha https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Aha! once connected?

Full read-write Aha! access lets Claude create features and requirements in the right release, update workflow status and assignees, promote or merge ideas, add comments to capture decisions, and tag work for the right initiative. The roadmap upkeep that used to mean tab-switching happens where your product work already lives, with you approving the changes.

Create a feature in a chosen release with name, description, and tags set
Update a feature's workflow status or assignee as work progresses
Add a requirement under an existing feature to capture scope
Promote an idea into a feature, or link it to one already planned
Add a comment to a feature or idea to record context and decisions
Search features and ideas by query and propose batched status updates

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Aha! access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Aha! API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Aha! changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Aha! connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Aha! connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Aha! account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Aha!'s side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Aha!?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Aha! account it signs in with. Revoking access is one click in Aha!.

More on the Aha! connector

Aha! connector for claude.ai Todoist + Claude Code Teamwork + Claude Code Shortcut + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us