Read blog posts, authors, categories, tags, pages and collection items in ButterCMS. For developers and content teams that manage a site in ButterCMS. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"buttercms": {
"url": "https://buttercms.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"buttercms": {
"type": "http",
"url": "https://buttercms.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
Search the blog posts and read the full post with its author and tags.
buttercms_search_posts buttercms_get_post
List the authors, categories and tags to see how the content is organized.
buttercms_list_authors buttercms_list_categories buttercms_list_tags
List or search the pages and read one page with its fields.
buttercms_list_pages buttercms_search_pages buttercms_get_page
Read the collection items by key, for example a list of FAQ entries or team members.
buttercms_get_collections buttercms_list_collection_items buttercms_get_collection_item
The login page asks for your ButterCMS Read API token.
Find it in the ButterCMS dashboard → Settings → General → API Tokens. Each site has its own token. The token is used only to read your content on your behalf and to derive a private account id.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your ButterCMS Read API token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the ButterCMS connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
buttercms_list_posts | read | List blog posts List published blog posts, newest first, with optional filters by author, category or tag. Use exclude_body to get short results. Read API: GET /posts/. |
buttercms_get_post | read | Get a blog post Get one blog post by slug, with the full body, metadata, and the next and previous posts. Read API: GET /posts/{slug}/. |
buttercms_search_posts | read | Search blog posts Full-text search in blog post titles, bodies and summaries. Results are sorted by relevance. Read API: GET /posts/search/. |
buttercms_list_authors | read | List authors List all blog authors. Set include to 'recent_posts' to embed the recent posts of each one. Read API: GET /authors/. |
buttercms_get_author | read | Get an author Get one blog author by slug. Set include to 'recent_posts' to embed the recent posts. Read API: GET /authors/{slug}/. |
buttercms_list_categories | read | List categories List all blog categories. Set include to 'recent_posts' to embed the recent posts of each one. Read API: GET /categories/. |
buttercms_get_category | read | Get a category Get one blog category by slug. Set include to 'recent_posts' to embed the recent posts. Read API: GET /categories/{slug}/. |
buttercms_list_tags | read | List tags List all blog tags. Set include to 'recent_posts' to embed the recent posts of each one. Read API: GET /tags/. |
buttercms_get_tag | read | Get a tag Get one blog tag by slug. Set include to 'recent_posts' to embed the recent posts. Read API: GET /tags/{slug}/. |
buttercms_list_pages | read | List pages List pages of one page type, or all Single Pages with page_type '*'. Filtering and ordering work only for a real page type. Read API: GET /pages/{page_type}/. |
buttercms_get_page | read | Get a page Get one page by page type and slug. Use '*' as page_type for a Single Page. Read API: GET /pages/{page_type}/{page_slug}/. |
buttercms_search_pages | read | Search pages Search the direct content of pages by text. Results are sorted by relevance. Read API: GET /pages/search/. |
buttercms_get_collections | read | Get collections by key Get the items of one or more collections at once. Every key must be an existing collection key. Read API: GET /content/?keys=a,b. |
buttercms_list_collection_items | read | List collection items List the items of one collection, with paging, ordering and field filters. Each item meta.id is the item id. Read API: GET /content/{collection_key}/. |
buttercms_get_collection_item | read | Get a collection item Get one collection item by its numeric id. Read API: GET /content/{collection_key}/{item_id}/. |
buttercms_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
buttercms_request_feature | Request a missing feature Tell usefulapi that the user needs something the ButterCMS tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
buttercms_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on ButterCMS (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $39/month or $390/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
buttercms_cancel_subscription | Cancel the Pro subscription Cancel the caller's ButterCMS Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run buttercms_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this ButterCMS server only. Subscribe with buttercms_upgrade (it returns a Stripe Checkout link). Cancel any time with buttercms_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running buttercms_upgrade before then undoes the cancel. Or write to [email protected].
Find a blog post by keyword. Audit the blog structure. Review the pages of a site. Read the content of a collection. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by ButterCMS. The server calls the ButterCMS API with your own ButterCMS access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your ButterCMS Read API token. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your ButterCMS Read API token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the ButterCMS API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in ButterCMS.
All 15 ButterCMS tools are marked read-only.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this ButterCMS server only. Cancel any time: Pro then runs to the end of the paid period. Run buttercms_usage_status to see how many calls you used.
Ask the AI to run buttercms_upgrade: it returns a Stripe Checkout link. To cancel, run buttercms_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with buttercms_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.