API keys for automations

A Slack bot, or an AI agent your team hosts cannot sign in through a browser. For those, create an API key: keys let a server-side agent use the Jimo MCP without a browser login.

A key is a service account owned by the project, not by the person who created it. It keeps working if that person leaves, ensuring continuity for your automations.

This is not the Jimo REST API (Settings → Integrations → API). Those credentials do not work here, and an MCP key does not work there.

Create a Key

1

Open the API Keys card

Go to Settings → Integrations → Model Context Protocol and click + New key.

2

Name it after the job

One key per automation, so a single job can be revoked alone. The field suggests "Release Automation".

3

Choose what the key can do

Under What this key can do, tick the permissions the job needs: Read project data and analytics, Manage Experiences, Teach my Jimo Agent, Build and run my Jimo Agent. They work exactly like the assistant permissions.

4

Set Custom Access

Under Custom Access, choose what the key may reach, independent of who created it: view experiences and their analytics, create and edit experiences, publish and pause experiences, view posts and post analytics, create and edit posts, publish posts, view end users' identities.

The AI Agent group covers the agent:

• View the agent setup and conversations

• Edit pages, skills and settings

• Delete pages and skills

• Manage AI knowledge

Ticking Build and run my Jimo Agent grants view and edit. Delete pages and skills stays unticked until someone opts in, the same as deleting experiences or posts. A read-only key can view the agent setup and its knowledge, it cannot change them.

5

Copy the Client ID and Client secret

The secret is shown once. Store it in your secret manager right away.

How a Key Works

Your script exchanges the Client ID and Client secret for a short-lived access token (about 30 minutes), then calls the same endpoint an assistant uses:

https://mcp.usejimo.com/mcp

Good to know:

• Content created by a key has no author, and webhooks it triggers carry no user.

• The same preview and confirm rules apply to keys as to assistants.

• Up to 10 keys per project.

Rotation and Revocation

Action	Effect
Rotate	Issues a new secret. The previous one keeps working for 24 hours, or until you click Retire previous secret, so you can swap secrets without downtime.
Revoke	Disables the key and every token minted from it immediately.
Permissions	Fixed at creation. To change them, revoke and create a new key.

A key created before October 7, 2026 cannot gain Build and run my Jimo Agent: create a new one.

Never share a Client secret, including with Jimo support.

Next Steps

• Managing Access, Usage & Limits: where keys are listed, rotated, and revoked.

• Tools Reference: what a key can call, depending on its permissions.