How to Use the Aha! MCP in CrewAI

Q: How do I pass the Aha! MCP Server URL to my CrewAI agents?

You can pass the HTTP endpoint directly into the mcps list when defining your agent. This simple setup automatically exposes all five product management tools to that specific agent. It requires zero boilerplate code to get started.

Q: Can I restrict which Aha! MCP tools a specific CrewAI agent can use?

Yes, you can use MCPServerHTTP from the crewai.mcp module along with a toolfilter. This lets you limit a research agent to reading data while restricting write access to your manager agent. It enforces clean role boundaries.

Deploy a team of collaborative CrewAI agents to manage and audit your Aha! product backlog autonomously.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Aha! MCP to CrewAI

Create your Vinkius account to connect Aha! to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Aha! with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Collaborative Backlog Grooming with CrewAI

The `list_ideas` tool acts as the primary data source for your planning agents to analyze customer feedback. One specialized agent can gather the ideas, while a second agent evaluates them against your strategic goals. This multi-agent setup ensures that backlog grooming does not fall on a single developer. By using this MCP Server, your crew collaborates in shared memory to keep your product roadmap clean and actionable.

Autonomous Feature Auditing

The `get_feature` tool allows your QA and product agents to inspect specific requirements and verify implementation details. Your agent can compare the feature description against live codebase commits to ensure alignment. You configure this by adding the server URL to your agent's `mcps` array during initialization. This native integration lets your crew query deep product specifications without writing custom API connectors.

Automated Release Coordination

The `list_releases` tool provides your coordination agents with the exact launch dates and feature lists scheduled for deployment. A release manager agent uses this data to write changelogs and prepare internal teams. This eliminates manual status meetings by letting autonomous agents compile progress reports. Your crew runs in the background, keeping your external documentation perfectly synced with your development roadmap.

Setup guide

Set up Aha! MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke Aha! tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="Aha! Analyst",
    goal="Access and analyze Aha! data via MCP.",
    backstory="Expert analyst with direct Aha! access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent Aha! transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="Aha! Analyst",
        goal="Access and analyze Aha! data via MCP.",
        backstory="Expert analyst with direct Aha! access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Aha! transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Aha!. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Aha! now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Aha! MCP in CrewAI

You can pass the HTTP endpoint directly into the `mcps` list when defining your agent. This simple setup automatically exposes all five product management tools to that specific agent. It requires zero boilerplate code to get started.

Yes, you can use `MCPServerHTTP` from the `crewai.mcp` module along with a `tool_filter`. This lets you limit a research agent to reading data while restricting write access to your manager agent. It enforces clean role boundaries.

Agents use a shared memory system to pass context back and forth during a crew run. When one agent fetches feature details, that information becomes part of the shared context. Other agents can then analyze it without making redundant API calls.

Yes, you can run your crew sequentially or hierarchically depending on your operational needs. This allows you to run fast, linear checks or complex, multi-layered backlog audits.

Vinkius secures all MCP transactions using sandboxed V8 isolates that process requests ephemerally. Your product features, release timelines, and backlog ideas are never cached or exposed to external networks. The connection uses a single-token entry point to prevent credential leaks.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript