What you can do with Aha!

Built for

Product Management, Roadmapping, Strategy Alignment, Voice of Customer

Example workflows

Summarize roadmap status

Connects product hierarchy to execution status.

Try this

List our Aha! products, then summarize active features and goals for the main product — highlight what is in progress versus not started.

Triage incoming ideas

Uses ideas plus category context for intake review.

Try this

Show recent stakeholder ideas for our product, including vote counts and categories, and group them by theme for prioritization.

Prepare a planning review

Cross-entity read for leadership sync meetings.

Try this

Pull goals, linked features, and open ideas for one product so I can prepare a quarterly planning review deck.

Capture a new idea

Shows write path when the user explicitly wants to log feedback.

Try this

Create a new Aha! idea under our product with the title and description I provide, using an appropriate workflow status.

Context to know first

What can I do with Aha! through MCPBundles?

You can read products, features, goals, ideas, users, idea categories, comments, and endorsements. You can also create or update ideas, features, and goals, or delete them when you explicitly ask.

How do features, releases, and products relate?

Products are workspaces. Features live under releases within a product. When creating a feature you need the release it belongs to; listing can be scoped with a product id.

Where do stakeholder ideas show up?

Ideas can be listed account-wide or filtered to one product. Comments and endorsements are read using the idea id; categories are configured per product.

AI Skill
SKILL.md

Domain knowledge for Aha! — workflow patterns, data models, and gotchas for your AI agent.

Aha!

Aha! is product roadmap and strategy software. Products contain features and goals; ideas come from stakeholders; users are team members.

Data Model

  • Products are product lines. Features and goals belong to products.
  • Features are product capabilities scoped to releases. Goals are strategic objectives.
  • Ideas are stakeholder suggestions. Categories, comments, and endorsements are idea-scoped — need idea id.
  • Users are team members.
  • API responses: List endpoints return stream-style responses (array wrappers). Extract ids from response structure.

Recommended read order

  1. List products to choose the product workspace.
  2. Read features, goals, and ideas for that product (pass product_id to scope lists).
  3. For one idea, read categories (product-scoped), comments, and endorsements (idea-scoped).

Writes

Create ideas under a product, features under a release, and goals under a product. Updates target the record id directly. Deletes are permanent.

Gotchas

  • Domain required: API URL is https://{domain}.aha.io. Domain is the subdomain from your Aha URL (e.g. yourcompany.aha.io → domain=yourcompany).
  • Feature create needs release_id: Features belong to releases — pick a release before creating.
  • Idea-scoped operations: Categories need product_id; comments and endorsements need idea_id.
  • Response structure: Ideas live in data.ideas; other entities in similar nested structures.
  • Pagination: Integer page (1-indexed) and per_page (default 5). Read pagination.total_pages before sweeping large lists.
  • Read-after-write lag: Aha routes writes to primary and reads to replicas — a record created moments ago may 404 on immediate fetch; retry briefly if needed.

Tools in this Server (14)

Aha Delete Feature

Permanently delete an Aha! feature by id or reference key. This cannot be undone.

Aha Delete Goal

Permanently delete an Aha! goal by id or reference key. This cannot be undone.

Aha Delete Idea

Permanently delete an Aha! idea by id or reference key. This cannot be undone.

Aha Get Features

Read Aha! features across the account or within one product. Omit id to page through features; pass id to load one feature with requirements, release,...

Aha Get Goals

Read strategic goals in Aha!. Omit id to list goals; pass id for one goal with success metrics and linked initiatives. Optional product_id limits the ...

Aha Get Idea Categories

Read idea categories configured for a product. Requires product_id — use a product id from the products read to scope categories used when triaging id...

Aha Get Idea Comments

Read comments on one idea. Requires idea_id — use an id from the ideas read. Supports pagination because long discussion threads can be large.

Aha Get Idea Endorsements

Read endorsements on one idea. Requires idea_id — use an id from the ideas read to see who supported the idea.

Aha Get Ideas

Read stakeholder ideas in Aha!. Omit id to list ideas account-wide; pass id for one idea with votes, categories, and workflow status. Optional product...

Aha Get Products

Read product workspaces in Aha!. Omit id to list products in the portfolio; pass id for one product's metadata and reference prefix.

Aha Get Users

Read team members in Aha!. Omit id to list users; pass id for one user's profile and product roles.

Aha Upsert Feature

Create or update an Aha! feature. Omit id to create under release_id (name required). Pass id to update an existing feature. New features must belong ...

Aha Upsert Goal

Create or update a strategic goal in Aha!. Omit id to create under product_id (name required). Pass id to update an existing goal.

Aha Upsert Idea

Create or update an Aha! idea. Omit id to create under product_id (name required). Pass id to update an existing idea. Updates use PUT on the idea id;...

Frequently Asked Questions

What can I do with Aha! through MCPBundles?

You can read products, features, goals, ideas, users, idea categories, comments, and endorsements. You can also create or update ideas, features, and goals, or delete them when you explicitly ask.

How do features, releases, and products relate?

Products are workspaces. Features live under releases within a product. When creating a feature you need the release it belongs to; listing can be scoped with a product id.

Where do stakeholder ideas show up?

Ideas can be listed account-wide or filtered to one product. Comments and endorsements are read using the idea id; categories are configured per product.

How do I connect Aha! to my AI agent?

Add the MCPBundles server URL to your MCP client configuration (Claude Desktop, Cursor, VS Code, etc.). The URL format is: https://mcp.mcpbundles.com/bundle/aha. Authentication is handled automatically.

How many tools does Aha! provide?

Aha! provides 14 tools that can be called by AI agents, along with a SKILL.md that gives your AI agent domain knowledge about when and how to use them.

What authentication does Aha! require?

Aha! uses API Key. Aha! requires credentials. Connect via MCPBundles and authentication is handled automatically.

Setup Instructions

Connect Aha! to any MCP client in minutes

MCP URL
https://mcp.mcpbundles.com/bundle/aha

One-click install:

The link prefills the Add custom connector dialog — you still review the values and click Add, then Connect to complete OAuth.

Or add manually

  1. Open claude.ai → Settings → Connectors.
  2. Click the + button and choose Add custom connector.
  3. Set Name to Aha! and paste the MCP URL into Remote MCP server URL.
  4. Click Add. Aha! will appear under Not connected — select it and click Connect to complete OAuth.
Name: Aha!
Remote MCP server URL: https://mcp.mcpbundles.com/bundle/aha
Authentication: OAuth

Custom connectors at claude.ai require a paid Claude plan (Pro, Max, Team, or Enterprise).

Ready to use Aha!?

Sign in to connect your credentials and start running tools from the chat.

Aha! MCP — Roadmaps, Features, Goals & Ideas in Chat