> ## Documentation Index
> Fetch the complete documentation index at: https://docs.replyful.com/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP server

> Let Claude, ChatGPT or any MCP client write help-center articles for you

Replyful exposes a remote [Model Context Protocol](https://modelcontextprotocol.io) server. Connect it to an AI assistant and ask it to write, translate and publish help-center articles.

```
https://api.replyful.com/mcp
```

Transport: Streamable HTTP (protocol revision 2026-07-28, older 2025 clients are served too).

## Signing in

Two credentials work:

* **OAuth (recommended, per user).** Add the URL in your client and sign in with your Replyful account. Tokens are scoped to the organization you sign in to and require the *org:manage* permission. Claude and ChatGPT both discover the sign-in flow automatically.
* **API key (per organization).** Send `Authorization: Bearer rfl_live_…` on every request. Create keys under **Settings → Developers → API keys**. Use this for CLI tools and Claude Code.

### Claude.ai / Claude Desktop

**Customize → Connectors → Add custom connector**, paste the URL and choose **Sign in now**. Team and Enterprise admins add it under **Organization settings → Connectors**. To use an API key instead, choose **No sign-in** and add a request header `authorization` with the value `Bearer rfl_live_…` (request headers are in beta).

### Claude Code

```bash theme={null}
claude mcp add --transport http replyful https://api.replyful.com/mcp
# or with an API key
claude mcp add --transport http replyful https://api.replyful.com/mcp \
  --header "Authorization: Bearer rfl_live_…"
```

### ChatGPT

Enable **Developer mode** in ChatGPT settings, add a connector with the URL and complete the sign-in. Writing tools require a plan that allows write actions.

## Tools

| Tool                 | What it does                                                                                   |
| -------------------- | ---------------------------------------------------------------------------------------------- |
| `list_help_centers`  | Help centers with enabled languages and audience. Start here.                                  |
| `get_help_center`    | Category tree and all articles with per-language status and version.                           |
| `get_article`        | One translation's draft title, markdown content, slug and version.                             |
| `create_category`    | New category (optionally nested) named in one language.                                        |
| `create_article`     | New empty article (version 0) in a help center.                                                |
| `save_article_draft` | Save title, markdown content and slug for one language. Compare-and-swap on `expectedVersion`. |
| `publish_article`    | Publish the saved draft of one translation.                                                    |

Every write goes through the same rules as the admin editor: the language must be enabled on the help center, `expectedVersion` must match the current version, and nothing is public until published. Deleting, settings, languages and custom domains stay in the admin app.

A typical prompt: *"Write a Swedish version of every English article in our Docs help center and publish them."* The assistant lists the center, reads each English article, creates the Swedish translation with `save_article_draft` (expectedVersion null) and publishes it.

## Rate limits

The MCP endpoint shares the [API rate limit](/api-reference/rate-limits): 100 requests per minute per user or API key.