Starter
For one person starting with their main account.
$6$5/mo
billed monthly $60 billed annually, save 17%
Try free for 7 daysTry free for 7 days- 2 connectors at once
- 2 accounts across them
- 1 seat
- Unlimited conversations
Codex can’t see your accounts today. Add HeyMetra and it can.
An MCP server lets Codex read your accounts as it answers. HeyMetra is one, for your marketing and revenue accounts.
Every account here can be connected and asked about from Codex.
Not in the grid because nothing is read from them: Slack, Telegram and Email are destinations. Each one lets Codex send to the place you linked. A message goes out as soon as it is sent. Switch on Ask before sending to approve each one first; an email to an address you did not save always waits for you.
Codex will load a server per account from config.toml and call them one after another. What it cannot know is that the store's refund and the subscription platform's cancellation are the same customer leaving. Put the accounts behind one connection and every one of them answers in the same session from one sign-in.
Held against the two alternatives worth naming: HeyMetra vs AdKit, an MCP server for ad accounts alone, and HeyMetra vs Supermetrics, which lands a copy of the data somewhere rather than answering out of the account.
“How many leads came in this week, and where did they come from?”
Zoho CRM
“How did subscription revenue move day by day this month?”
Adapty
“How many units did I sell on Amazon last week, and for how much?”
Amazon Seller Central
“How many chats came in last week, and how many did nobody answer?”
Zoho SalesIQ
“Which campaigns have we sent recently?”
Zoho Marketing Automation
Your assistant tells you in one line what it will change, and nothing reaches the account until you say yes in the chat. HeyMetra cannot undo a change afterwards.
Why Codex: Terminal-first. Useful when the question comes up while you are already in a shell.
Worth knowing for Codex: Under an [mcp_servers.<name>] section, then codex mcp login.
1[mcp_servers.heymetra]
2url = "https://mcp.heymetra.com/mcp"
$ codex mcp login heymetra
Authorize the accounts you want reachable. This happens once, in HeyMetra, and is the part that is the same wherever you ask. No HeyMetra account yet? The trial covers this step.
Try free for 7 daysPut it in ~/.codex/config.toml.
[mcp_servers.heymetra] url = "https://mcp.heymetra.com/mcp"
Ask Codex something that needs one of the accounts. The model picks the tool; you never name it.
These interfaces move, and this one has moved before. Where a step here disagrees with what is on your screen, trust the screen. Then check Codex's own documentation, which is what these steps were written from. And tell us, so the page stops being wrong for the next person.
There is no second model to buy here. The answering happens in Codex; HeyMetra supplies the accounts and asks you before anything in them changes.
For one person starting with their main account.
$6$5/mo
billed monthly $60 billed annually, save 17%
Try free for 7 daysTry free for 7 daysMost popular
For a small team running several accounts together.
$19$15.83/mo
billed monthly $190 billed annually, save 17%
Try free for 7 daysTry free for 7 daysFor teams and agencies with many accounts to connect.
$49$40.83/mo
billed monthly $490 billed annually, save 17%
Try free for 7 daysTry free for 7 daysFor organizations with custom scale and security needs.
Contact us
Contact sales~/.codex/config.toml. The server is one entry in it, and the key that holds the address is url. It is TOML rather than JSON, which is what every other file on these pages is: the server is a [mcp_servers.heymetra] section with url = "…" under it, and a JSON object pasted in its place will not parse at all.
Under an [mcp_servers.<name>] section, then codex mcp login. Everything else is the same as it is anywhere else: one address, the sign-in you already have, and the tools appear.
Yes. Codex reads MCP servers from its own config file, under an mcp_servers section.
Codex reads MCP servers from its own config file, under an mcp_servers section. After that, Codex discovers the tools the server exposes and decides which to call while it answers you. You never name a tool.
Yes. A local one runs as a process on your own machine and stops when you close Codex. A remote one runs on the operator’s infrastructure and is reached over HTTP, so there is nothing to install and nothing to keep running, and the credentials live with the operator.
Only if you said it may. Connecting an account to HeyMetra asks that question once: read-only, or may the assistant propose changes there too. An account left read-only carries no tool that can change anything, and Search Console and Jira connect read-only with no option to change. Where you said yes, Codex tells you in one line what it will change and waits; nothing reaches the account until you say yes in the chat. A message to a channel you linked goes out when it is sent, unless you switch on Ask before sending.
The same connection, from any of them. What differs is where the setting lives and what that app calls it: Codex says “MCP servers”.
Add it to HeyMetra once, then ask about it in the AI assistant you already pay for. Add the next one when you need it.
An MCP connector is one authorized account behind an MCP server. How a standard connector differs from a custom one, and when you need the second.