Skip to content

Butter CMS MCP connector

The Butter CMS connector lets Claude, ChatGPT, Cursor, Microsoft Copilot and other AI clients read and write your Butter CMS pages, blog posts, collections, authors, categories and tags, with each person signed in as themselves and every change logged.

  • Connects with an API key
  • Free 14-day trial
  • No credit card
Claude Elaichi connected

List Butter CMS pages updated in the last week.

Working in Butter CMS with Elaichi

  • List all Butter CMS pages
  • Get single Butter CMS page by ID
  • List all Butter CMS pages searches
Ask anything…
Governance / Audit log Last 24 hours
Butter CMS List all Butter CMS pages searches Emily Carter · Claude · 9:41 AM Done
Butter CMS Get single Butter CMS page by ID Emily Carter · Claude · 9:41 AM Done
Butter CMS List all Butter CMS pages Emily Carter · Claude · 9:41 AM Done
Butter CMS Create a Butter CMS page Megan Brooks · ChatGPT · 9:38 AM Done
Butter CMS Update a Butter CMS page by ID Ryan Hayes · Cursor · 9:35 AM Done

How to connect Butter CMS to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Butter CMS MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Butter CMS MCP connector for Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

    https://api.elaichi.ai/mcp
  2. 2

    Start Claude Code and run /mcp.

  3. 3

    Pick elaichi, then sign in and approve in the browser.

Terminal

$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp

Use --scope project instead to share it with the repository through .mcp.json.

Butter CMS MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

Butter CMS MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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.

Butter CMS MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

    https://api.elaichi.ai/mcp
  3. 3

    Create a new connection, sign in and approve, then press Add to agent.

  4. 4

    Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL
https://api.elaichi.ai/mcp
Authentication
OAuth 2.0
Type
Dynamic discovery

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

Connect Butter CMS to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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.

What teams do with Butter CMS through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Butter CMS is logged.

  • Content

    Draft a blog post from an outline

    Hand the agent a brief and let it create the post in Butter CMS with the right author, category and tags already set. Review it in Butter CMS before it goes anywhere.

  • Marketing

    Refresh a landing page after a launch

    Ask for the pricing or product page by name and have the new copy applied to it in place, so the page reflects what shipped this week.

  • SEO

    Find posts missing categories or tags

    Pull every post in Butter CMS, spot the ones with no category or a thin set of tags, and fix them in a single pass.

  • Product

    Update release notes stored as content

    Keep changelog entries, feature descriptions and FAQ items in Butter CMS collections current by changing only the fields that moved.

  • Support

    Check what the help page actually says

    Before answering a customer, ask what the published page or post in Butter CMS says on a topic, and flag it for a rewrite if it is out of date.

  • Marketing

    Summarize what published this month

    Read the Butter CMS blog feed and turn it into a plain list of what went live, who wrote it and which topics it covered, ready for the newsletter.

Try asking

  • “List Butter CMS pages updated in the last week.”
  • “Draft a blog post about our new pricing page.”
  • “Which Butter CMS posts are still unpublished?”

See all 25 Butter CMS tools →

What connecting Butter CMS gets you

6 screens from Elaichi, each doing one job for your Butter CMS account.

Elaichi Agent

Ask Elaichi to work across your apps.

List Butter CMS pages updated in the last week.

Draft a blog post about our new pricing page.

Which Butter CMS posts are still unpublished?

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask about pages and posts, get answers.

Plain language questions run against live Butter CMS pages, posts and content entries.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

Claude, ChatGPT, Cursor and Microsoft Copilot share one endpoint.

Connect any MCP client to Butter CMS over OAuth, no SDK, no shared key.

ElaichiTools
Tool Action Description
List all Butter CMS pages List Retrieve a paginated list of ButterCMS pages for a given page type, or all Single Pages when page_type is `*`. Returns: slug, name, page_type, published, updated, fields. Field filtering and ordering apply to Page Type endpoints, not Single Pages. Required: page_type.
Create a Butter CMS page Create Create a new ButterCMS page via the Write API with support for multiple locales and automatic media uploads. The page type schema must already exist in your account; pages are created as draft by default and processing is asynchronous. Returns: status. Required: title, slug, page_type, fields.
Update a Butter CMS page by ID Update Update an existing ButterCMS page via the Write API using a partial PATCH (PUT is supported for backwards compatibility). Only included fields are modified; title and slug are immutable. Page updates are asynchronous; scheduling is not supported. Returns: status, examples, name. Required: id, page_type.
Get single Butter CMS page by ID Get Retrieve a specific ButterCMS page by page type and slug (id). Use `*` as page_type to look up a Single Page when the type is unknown. Returns: slug, name, page_type, published, updated, fields. Required: page_type, id.
List all Butter CMS pages searches List Search ButterCMS pages by text query, returning matching pages sorted by relevancy. Only direct page content is searched; references are excluded from search but still included in the response based on levels. Returns: slug, name, page_type, published, updated, fields. Required: query.

Tool catalog

25 Butter CMS tools ready on connect.

Pages, posts, content entries and searches, every method covered without custom code.

ElaichiToolboxes
Name Source template Tools Created

Content toolbox

Butter CMS · posts and drafts

Butter CMS starter 18 Mar 4, 2026

Marketing toolbox

Butter CMS · landing pages and campaigns

— 9 Mar 2, 2026

Web engineering toolbox

Butter CMS · page schemas and builds

— 24 Feb 27, 2026

Localisation toolbox

Butter CMS · translated content entries

Butter CMS starter 6 Feb 19, 2026

SEO toolbox

Butter CMS · page metadata and searches

— 31 Jan 30, 2026

Support docs toolbox

Butter CMS · help pages and updates

— 12 Jan 22, 2026

Toolboxes

Every team gets its own toolbox.

Curate Butter CMS pages and posts tools per team and scope each toolbox separately.

ElaichiConnections
Connection Scope Status Access
BU

Butter CMS (Marketing site)

Connected by Emily Carter

Personal • Active 1 team · 6 members
BU

Butter CMS (Blog)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
BU

Butter CMS (Docs)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
BU

Butter CMS (Careers)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
BU

Butter CMS (EMEA site)

Connected by Ryan Hayes

Personal • Active Not shared
BU

Butter CMS (Product pages)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Teammates publish posts without touching credentials.

See who connected each Butter CMS account and which teams and members use it.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Butter CMS Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Butter CMS Pages Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Butter CMS Pages List Toolbox

Audit log

Every page edit has a name on it.

When, who, what happened, type and resource for each Butter CMS call.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.

Butter CMS digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch pages

    Butter CMS

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    Butter CMS

    Queued

Automations

A schedule fires, a digest posts back.

Six steps fetch Butter CMS posts, group them, draft a digest, then wait for approval.

Butter CMS health

Refreshed 4 minutes ago · every 15 minutes · from the pages collection

Live

Pages

1,284 ↓ 12%

Posts

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Pages created

Last 14 days

By team

Share of activity

Marketing site 34%

Blog 27%

Docs 21%

Careers 18%

Collections and dashboards

Butter CMS content health, counted on schedule.

Four metrics, 14 days of records created and a team breakdown, computed without a model.

For IT and engineering

Elaichi vs Zapier MCP vs Composio for Butter CMS

All three can connect Butter CMS to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Butter CMS, by what to check
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 Butter CMS tools Allow or restrict single Butter CMS 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 Butter CMS 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 Free for one person; $15 per user per month on Gold. 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.

Butter CMS tools for your AI agents

25 tools are ready to call through Elaichi's MCP endpoint the moment you connect Butter CMS, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

Questions, answered

How do I connect Butter CMS to Claude?

Connect Butter CMS in Elaichi first, which means pasting the read and write API key from your Butter CMS account settings. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in with your Elaichi account and your Butter CMS pages and posts are available in the conversation.

Does Butter CMS work with ChatGPT and Cursor as well as Claude?

Yes. Once Butter CMS is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Butter CMS once and every client picks it up.

What can an AI agent actually do with my Butter CMS data?

An agent can list and read your Butter CMS pages, blog posts, collection items, authors, categories, tags and RSS or Atom feeds, and search across pages and posts. It can create new pages, posts and collection items, update existing ones, and delete posts or collection items if you allow it. In practice that means drafting a post, updating a landing page, tidying tags or reporting on what has published, all from a chat window.

Does connecting Butter CMS give the AI access to everything in my workspace?

The AI works within whatever the Butter CMS API key you connected can reach, so a read-only key means the agent can only read. Elaichi can narrow that further by turning off individual actions for a role or a person, but it can never grant more than the key itself allows. Everything the agent does in Butter CMS is recorded against the person who asked.

Can my team share one Butter CMS connection?

Yes. One person connects Butter CMS with the API key and shares that connection with a team in Elaichi, and nobody else ever sees or handles the key. Each teammate still signs in to Elaichi as themselves, so the audit log shows exactly who created or changed each page or post.

Can I stop an agent from deleting or changing things in Butter CMS?

Yes. In Elaichi you can restrict specific actions for the Butter CMS connector, such as deleting posts or collection items, or updating pages, while leaving reading and drafting on. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT or any other client cannot run it, whatever the prompt says.

What happens to a Butter CMS connection when someone leaves?

When you offboard a person in Elaichi their access to Butter CMS through every AI client ends at once, without touching the Butter CMS account itself. A shared Butter CMS connection keeps working for everyone else on the team. If you ever want to remove Butter CMS entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client together.

Does the Butter CMS MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Butter CMS 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, Microsoft Copilot, 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 Butter CMS?

Yes. Both let Claude, ChatGPT or Cursor use Butter CMS. 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 Butter CMS call.

How is Elaichi different from Composio for Butter CMS?

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 Butter CMS: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Butter CMS in front of your team

14 days of Black, no credit card. Connect it once and pick what each team can call.

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot