Connect an AI agent to your knowledge base (MCP & API)

AcornReply lets you manage your knowledge base from an AI assistant over MCP, or from your own code over a REST API. Use it to stand up a help center from existing docs, keep entries in sync with your product, or let an assistant draft and organize articles for you. Setup instructions live under Settings → MCP & API (admins also see the API key and REST snippets there).

Connect Claude by signing in

No API key needed. Any workspace member can connect, not only admins.

• Claude (claude.ai or Claude Desktop): add https://mcp.acornreply.com as a custom connector and click Connect. Sign in with your AcornReply account, pick a workspace if you have more than one, and click Allow.
• Claude Code: run claude mcp add --transport http acornreply https://mcp.acornreply.com, then run /mcp, choose acornreply, and select Authenticate. Your browser opens to sign in.
• Other MCP clients that support MCP OAuth sign-in connect the same way, with just the URL.

The connection acts as you, in the workspace you picked. To use a different workspace, ask your assistant to switch; the switch applies to every conversation using that connection. To disconnect, remove the connector in your client, or go to Settings → MCP & API → Connected apps and choose Disconnect.

What a connected assistant can do

• Search and list your FAQs and articles, and read any one in full.
• Create FAQs and articles (written in markdown, converted and sanitized automatically), with a dry run to preview first.
• Update, publish or unpublish, and delete entries. Deleting an entry asks for confirmation first.
• Manage categories and upload images for your articles.
• Check view stats for your published articles to find content nobody reads.

It reaches only your knowledge base. It can't see your inbox, conversations, customers, billing, or team members. Entries AcornReply learns automatically from resolved conversations are not available to it either.

Other MCP clients: use an API key

For clients without OAuth sign-in, and for the Claude API, connect with a workspace API key instead. Admins create keys under Settings → API keys: enter a name (like "Cursor"), click Generate key, and copy the key. It starts with ak_. Send it in an Authorization: Bearer ak_YOUR_KEY header, never in the URL. Treat a key like a password; you can revoke it any time. A key connection always stays in the key's workspace.

Or use the REST API

Prefer to call it from your own code? The knowledge-base operations are also available over REST at https://acornreply.com/api/v1/… with the same ak_ key, for example GET /api/v1/kb/entries to list entries. Full documentation lives at acornreply.com/developers, with an OpenAPI spec at /api/v1/openapi.json.

What it's good for

• Bulk-authoring a help center from your existing product docs.
• Keeping the knowledge base current by syncing entries from your source of truth.
• Letting an assistant help draft, tidy, and categorize entries. You stay in control: create entries unpublished and publish them once you've reviewed them.