AthenaHQ MCP connector
The AthenaHQ connector brings your AI search visibility, prompts, responses, competitors and tracked content to Claude, ChatGPT, Cursor and the Elaichi Agent, so anyone can ask how your brand shows up in AI answers.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
94 tools
How to connect
How to connect AthenaHQ to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect AthenaHQ once
-
Open Connections, choose Add connection, and pick AthenaHQ.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in AthenaHQ. AthenaHQ's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
AthenaHQ MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
AthenaHQ MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
AthenaHQ MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect AthenaHQ to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with AthenaHQ through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Marketing
Check this week's AI visibility before standup
Ask how often your brand appeared in AI responses for your tracked prompts over the last date range, and which topics moved. The answer comes from live AthenaHQ data, not a screenshot someone exported on Friday.
-
Content
Find which pages AI answers actually cite
Pull your tracked content and content hub sheets, then ask which pages earned citations and for which prompts. Plan the next brief around what already gets quoted.
-
Brand
See how each persona hears about you
Compare responses across your AthenaHQ personas and locations to see where the brand story lands and where it goes missing.
-
Product marketing
Watch competitors in the same prompts
Ask which competitors show up alongside you in AI responses for a topic, and how that has changed. Take the comparison straight into positioning work.
-
Agency
Brief a client from their saved views
Open a client's websites and saved views in AthenaHQ, ask for the highlights, and turn them into a client-ready update in minutes.
-
Leadership
Know what AI search is worth
Ask for the AI search value and credit usage for the organization and each website, so budget conversations start from real numbers.
Try asking
- “Which prompts mentioned our competitors more than us this week?”
- “Summarize this month's AI responses for our pricing topic.”
- “Which of our tracked content got cited in AI responses lately?”
Compare
Elaichi vs Zapier MCP vs Composio for AthenaHQ
All three can connect AthenaHQ to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over AthenaHQ tools | Allow or restrict single AthenaHQ tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per AthenaHQ call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
AthenaHQ tools for your AI agents
94 tools are ready to call through Elaichi's MCP endpoint the moment you connect AthenaHQ, governed by the same roles, restrictions, and audit log as everything else in Elaichi. AthenaHQ builds and runs these tools.
No tools match your search.
See it in Elaichi
What connecting AthenaHQ gets you
6 screens from the product, each doing one job for your AthenaHQ account.
The agent
Ask AthenaHQ questions in plain language.
Get live answers on prompts, responses and competitors without opening a dashboard.
- prompts
- responses
- competitors
- topics
Ask Elaichi to work across your apps.
Which prompts mentioned our competitors more than us this week?
Summarize this month's AI responses for our pricing topic.
Which of our tracked content got cited in AI responses lately?
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint brings AthenaHQ to every MCP client.
Claude, ChatGPT and Cursor share one governed endpoint, no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
94 AthenaHQ tools, with no code to write.
Prompts, responses, personas, topics, competitors, content and credits, covered out of the box.
- Open AI access
- Check public AI access
- Get prompt schedules
- Get AI search value
ElaichiToolsToolboxes
Every team gets its own AthenaHQ toolbox.
Marketing, Content and Brand each see the AthenaHQ tools scoped to their work.
- Marketing
- Content
- Brand
- Competitive intelligence
ElaichiToolboxesShared connections
Share one AthenaHQ connection, never a credential.
Teammates work through the connection you set up without ever seeing the login.
- Marketing
- Content
- Brand EMEA
- Product marketing
ElaichiConnectionsAudit log
Every AthenaHQ call names who did what.
When, who, what happened, type and resource, in an append-only log.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
Scheduled AthenaHQ digests, approved by a person.
Responses are fetched, grouped by topic, drafted, approved and posted back to AthenaHQ.
AthenaHQ digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch prompts
AthenaHQ
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
AthenaHQ
Queued
Collections and dashboards
AthenaHQ health numbers, computed without a model.
Four metrics, 14 days of responses created, a team breakdown, refreshed on schedule.
AthenaHQ health
Refreshed 4 minutes ago · every 15 minutes · from the prompts collection
Prompts
1,284 ↓ 12%
Responses
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Prompts created
Last 14 days
By team
Share of activity
Marketing 34%
Content 27%
Brand EMEA 21%
Product marketing 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect AthenaHQ to Claude?
Connect AthenaHQ in Elaichi first: AthenaHQ connects over OAuth, so you sign in to your AthenaHQ account in a browser window and approve access, with no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude asks you to sign in to Elaichi, and from then on it can work with your AthenaHQ prompts, responses and content as you.
Does AthenaHQ work with ChatGPT and Cursor as well as Claude?
Yes. Once AthenaHQ is connected in Elaichi, Claude, ChatGPT, Cursor, the Elaichi Agent and any other MCP client use the same endpoint, https://api.elaichi.ai/mcp. You connect AthenaHQ once and every client picks it up.
What can an AI agent actually do with my AthenaHQ data?
With AthenaHQ connected, an agent can read your tracked prompts and their schedules, the AI responses they produced, your personas, topics, competitors, locations and saved views, and your tracked content with the prompts that cite it. It can also report AI search value and credit usage for the organization and each website. Short, concrete asks work best, such as which competitors appeared in pricing prompts this month.
Does connecting AthenaHQ give the AI access to every website and workspace?
No. Access follows the person who signed in to AthenaHQ, so the agent sees only the websites, prompts and responses that person can already open in AthenaHQ. Elaichi can narrow that further with roles and restrictions, and it never widens it.
Can I stop an agent from deleting or changing things in AthenaHQ?
Yes. The AthenaHQ connector is mostly about reading prompts, responses, content and credits, and whatever actions exist can be restricted one by one in Elaichi. A restricted action is never advertised to Claude, ChatGPT or Cursor, so no prompt, however worded, can reach it.
What happens to an AthenaHQ connection when someone leaves?
Offboarding a person in Elaichi ends their access to AthenaHQ through every client at once. If they had shared an AthenaHQ connection with a team, it keeps working for everyone else. If you want AthenaHQ gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and the Elaichi Agent together.
Does the AthenaHQ MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. AthenaHQ is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for AthenaHQ?
Yes. Both let Claude, ChatGPT or Cursor use AthenaHQ. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every AthenaHQ call.
How is Elaichi different from Composio for AthenaHQ?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to AthenaHQ: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put AthenaHQ in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.