All help

Connect AI assistants, Zapier and your own code

MCP and Zapier keys, API access, and what a key can do.

AI assistants such as Claude, Zapier, and your own scripts can work in the app for you: list your clients and their accounts, write drafts, schedule or publish posts, check how posts went and read a client’s figures. Settings → API and AI assistants has two sections, each with its own kind of key.

What comes with which plan

  • MCP and Zapier (AI assistants and Zapier) come with the Partner program, and are on during the free trial. They are not in Studio, Agency or the business plan: the section then shows a lock.
  • API access (the API, for your own code) is included in the Partner program, with no add-on fee. It is off during the free trial unless support has switched it on.

Get API access

  1. Open Settings → API and AI assistants. Under API access you see what it is and its price in your currency.
  2. Click Contact us. Contact support opens with the subject filled in; send it.
  3. Support switches it on for your workspace and invoices it separately. There is no checkout.
  4. When it’s on, Create API key and the API reference show under API access.

If API access is switched off later, your API keys stop working at once. They are kept, and work again when it is switched back on.

Two kinds of key

  • An MCP and Zapier key works with AI assistants (MCP) and Zapier only. It doesn’t work with the API.
  • An API key works with the API only. It doesn’t work with MCP or Zapier.
  • Keys made before 14 November 2026 are MCP and Zapier keys.

Create a key

  1. Open Settings → API and AI assistants. Click Create MCP and Zapier key under MCP and Zapier, or Create API key under API access.
  2. Name it after the tool that will use it, such as Claude or Zapier, so you know which key to revoke later.
  3. Choose when it Stops working: Never, In 30 days, In 90 days or In a year.
  4. Click Create key, then Copy key. You won’t see the key again, so keep it somewhere safe, such as a password manager.
A key acts as you. It can do what your login can do, for the clients you work on, so anyone who has it can too. It stops working if your access is removed.
  • Each person can have up to 20 keys. Last used shows when each one was last used.
  • Owners see everyone’s keys and can revoke any of them. Members see their own.
  • Client logins can’t have keys.

Connect an AI assistant

Assistants that support MCP connect with one of your MCP and Zapier keys. The assistant can then list clients and their accounts, write drafts, schedule or publish posts, check how posts went, read a client’s figures, see what went out or failed lately, and add photos and videos from a link.

Claude Desktop: open Settings → Developer → Edit config, paste this into claude_desktop_config.json with your key in place of YOUR_KEY, then restart Claude. It needs Node.js on your computer.

claude_desktop_config.json
{
  "mcpServers": {
    "social": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.metronoms.com/mcp", "--header", "Authorization:${AUTH_HEADER}"],
      "env": { "AUTH_HEADER": "Bearer YOUR_KEY" }
    }
  }
}

Claude Code: run this in a terminal, with your key in place of YOUR_KEY.

Terminal
claude mcp add --transport http social https://api.metronoms.com/mcp --header "Authorization: Bearer YOUR_KEY"

Other assistants: the server address is https://api.metronoms.com/mcp, the transport is Streamable HTTP, and the header is Authorization: Bearer YOUR_KEY. Most assistants take these in a settings file, for example:

Server settings
{
  "url": "https://api.metronoms.com/mcp",
  "transport": "streamable-http",
  "headers": { "Authorization": "Bearer YOUR_KEY" }
}

Connect Zapier

When Zapier asks for a key, paste an MCP and Zapier key. Zapier can start a Zap when a post goes out or fails, when a monthly report is ready or when a lead comes into the CRM, and it can create a draft or schedule a post.

Ask for drafts until you trust the assistant: a draft is never published until someone schedules it in the app. Assistants are told to save drafts unless you clearly ask to schedule or publish, and to check with you before publishing straight away.

What it can and can’t do

  • Posts go through the same checks as the post window (text length, photo and video rules for each network) and your approval rules, so a post may wait for approval.
  • A post without a link gets the client’s website as its link, as in the post window (see The website link). To leave it off, ask the assistant to (it sends addWebsiteLink: false), or set Add the Website Link to No in Zapier.
  • TikTok posts are saved as drafts only. TikTok asks a person to choose who can see the video and agree to its terms, so you finish them in the post window.
  • It can cancel a scheduled post or delete a draft, but not a post that has gone out. It can’t connect accounts or change settings.

Credits and limits

  • Posts made through an assistant, Zapier or the API use credits like any other: a post to X uses 2 credits, or 15 with a link. Nothing else here costs credits.
  • Settings → Billing shows this month’s API requests, assistant actions, posts made and the credits they used, under API and AI assistants.
  • Each key can make 120 requests a minute and 10,000 a day.

Revoke a key

In Settings → API and AI assistants, click Revoke next to the key, then Revoke key. Anything using it stops working straight away. This can’t be undone.

Build your own

With API access on, the API reference lists every request, with examples.

If something goes wrong

API access is included in the Partner program. Book a meeting at metronoms.com/partner-program to talk about it.

The API was called, or an API key asked for, in a workspace whose plan doesn’t include it. API access comes with the Partner program: book a meeting.

This key works with MCP and Zapier only. Create an API key in Settings → API and AI assistants.

An MCP and Zapier key was used with the API. With API access on, create an API key and use that one.

This key works with the API only. Create an MCP and Zapier key in Settings → API and AI assistants.

An API key was used in an assistant or in Zapier. Create an MCP and Zapier key and use that one.

MCP and Zapier: included in the Partner program. Book a meeting at metronoms.com/partner-program to talk about it.

The workspace is on Studio, Agency or the business plan, or its free trial ended on one. The keys are kept and work again in the Partner program.

That API key isn’t valid. Check you copied all of it, or create a new one in Settings → API and AI assistants.

Copy the whole key again: it starts with mtr_live_. If it’s lost, create a new one; keys are shown only once.

This API key was revoked. Create a new one in Settings → API and AI assistants.

Someone revoked it. Create a new key and put it in the tool or assistant in place of the old one.

This API key has expired. Create a new one in Settings → API and AI assistants.

It reached the date chosen under Stops working. Create a new key.

This API key stopped working because the person who created it no longer has access to this workspace.

Keys belong to the person who made them. Someone with access creates a new key.

Too many requests with this key (the limit is 120 a minute). Wait 12 seconds and try again.

The tool is sending too fast. It works again after the wait; slow the tool down if it happens often.

Connect AI assistants, Zapier and your own code · Help