Each connection is one workspace, and there is no tool to switch. Connect again and pick the other workspace on the consent screen.
MCP
The Ferndesk MCP server lets AI tools such as Claude, ChatGPT, Cursor and Codex act in your workspace as you. They can search and edit articles, stage changes for review, handle Support conversations and read reports. Its address is https://mcp.ferndesk.com. You sign in with OAuth, so there is no API key.
Owners and admins find per-client steps in Integrations > AI clients. A contributor can connect too, with the same URL. Your help center also has a separate, read-only MCP server for readers, see Search, SEO and AI tools.
Connect a client
Add the URL to your client, then sign in to Ferndesk in the browser window it opens. On the consent screen you pick the workspace and approve access.
claude mcp add --transport http ferndesk https://mcp.ferndesk.comClaude (claude.ai and desktop): add a custom connector with the URL. On Team and Enterprise, an organization owner adds it first. Anthropic's custom connectors guide has the steps.
Claude Code: run the command, start a session, run
/mcp, selectferndeskand choose Authenticate.ChatGPT: turn on Developer mode in Settings > Apps > Advanced settings, then create an app with the URL. Developer mode depends on your ChatGPT plan.
Cursor: use Add to Cursor on the AI clients page, or add the JSON above to
~/.cursor/mcp.jsonor a project's.cursor/mcp.json.Codex CLI: remote servers go in
config.toml, becausecodex mcp addonly adds local servers. Then runcodex mcp login ferndesk.Other clients: any client that speaks Streamable HTTP and OAuth 2.1 with dynamic client registration and PKCE (S256). It must be a public client: one that needs a fixed client secret won't work.
What a connection can do
One connection acts as one member in one workspace. It can do what both your role and the permissions you approved allow, and your role is checked on every request, so a change of role applies at once.
Permission | What it allows |
|---|---|
| Read and search articles, drafts, revisions, review requests and Fern's tasks. |
| Create and edit drafts, move and delete articles, manage collections and order, stage changes in a review request, manage help center users. |
| Publish drafts and review requests, unpublish, restore revisions. Owners and admins only. |
| Read AI Assistant conversations from your help center. |
| Read Support conversations, customers, teammates, labels and saved replies. |
| Add internal notes. Owners and admins can also assign, label, close, reopen, snooze and prioritise. |
| Send replies to customers as you. Off by default: turn it on at consent. |
| Read Support and help center reports. |
| Read help center, widget, AI agent, playbook, inbox, label, saved reply and team settings. Secrets are never returned. |
| Change those settings, add email inboxes and turn on Support. Owners and admins only. |
| Invite teammates. Off by default, owners and admins only. |
Clients that don't ask for specific permissions get all of them except the two that are off by default. To add a permission later, connect again and approve it.
Changes go through review
In a help center that already has published articles, edits are staged in a review request. Nothing goes live until someone publishes it, in Ferndesk or from the client with your confirmation. Submitting a request emails your owners and admins. A review request that includes API reference changes is published in Ferndesk only.
Keep an article's URL
An article's URL is its slug and short ID, such as /connect-intercom-a1b2c. Without a custom slug, the slug follows the title each time the article is published, and the old URL redirects to the new one with a 301.
To choose the slug, pass slug to save_article when you stage the change in a review request. In direct mode, save the draft without it and pass slug to publish_article. The slug becomes the article's custom slug, so it stays when the article is retitled. To keep the current URL through a retitle, pass the current slug. get_article returns customSlug, which is true once a custom slug is set.
A slug has at least 2 characters: lowercase letters, numbers and single hyphens, with no hyphen at the start or end. An invalid slug is refused with a suggested fix.
The MCP doesn't require unique slugs, because every URL ends in the short ID.
You can't pass a slug for a translation (change it in Ferndesk), for a delete, or on a help center published through an external platform.
The MCP can't turn a custom slug off. To make the URL follow the title again, turn off Custom slug in Article settings > SEO.
The public API takes the same slug field on POST /v1/review_requests/:id/changes, POST /v1/articles and PATCH /v1/articles/:id, in the same format.
Link to collections and change their URLs
Text links can also point at a collection, a section or a published API reference in the same help center. Use internal://coll_..., internal://sect_... or internal://apiref_... with ids from get_helpdesk_overview (API reference ids come from get_order on the section).
To change a collection's URL, pass slug to save_collection with its collection_id. The short ID stays the same, so the old URL forwards to the new one with a 301.
Limits
It can't start a Fern task. It can list and discard Fern's tasks.
There is no image upload tool. Put images in the article's HTML or markdown: inline
data:images are uploaded when the article is saved, and images hosted elsewhere are copied to your help center when it is published.It can't create or delete sections, manage billing, API keys or webhooks.
An article body can be up to 500,000 characters.
Writes share the API budget: 1,000 a minute per connection and 3,000 a minute per workspace. Reads aren't counted.
Without an active subscription, changes are turned off.
Manage connections
Owners and admins see every connection on the AI clients page, one row per workspace, and can revoke any of them. A contributor who wants a connection removed asks an owner or admin. Access tokens last an hour and refresh for 7 days, so a client unused for a week asks you to sign in again.
Can one client use several workspaces?
Why was my save refused?
Most refusals say what to change: a missing permission (reconnect and approve it), a role that can only save drafts, an article with another writer's open draft, or an edit that would drop the title heading, images or blocks by accident.
Can a contributor publish?
No. A contributor's client saves drafts and submits review requests, and an owner or admin publishes them.