Connect a coding agent with MCP

An MCP connection lets a compatible coding agent work with your Supahelp Knowledge Base. The current Supahelp MCP 2.0 tools can read articles, edit existing drafts, preview publication, and publish the entire site when you grant that permission.

“MCP 2.0” is the Supahelp integration version. It is not a client protocol version you need to select.

Before you start

• You need the Owner, Admin, or Editor role.

• Install and run your coding agent, such as Codex, Claude Code, or Cursor.

• Choose the workspace whose Knowledge Base you want to connect.

This connects your external agent. It does not turn on customer Ask Supa or Supa for your team.

Create a connection

1. Open Settings → AI Configuration in your workspace.

2. Find Coding agent connections.

3. Choose Codex, Claude Code, or Cursor.

4. Optionally enter a name, such as “Codex on my laptop”.

5. Choose permissions.

6. Choose an expiry of 7, 30, or 90 days.

7. Select Create connection.

Start with Read, or Read and Edit drafts. Add publication permission only if you want this connection to publish.

Add the supplied configuration

After creation, Supahelp shows a Token and agent-specific Configuration. The token is shown only once.

1. Follow the setup instructions shown for your chosen agent.

2. Open the configuration file shown below.

3. Add the Supahelp entry while keeping your other settings and MCP servers.

4. Save the file and restart the agent.

For Codex, replace an existing Supahelp block instead of adding a second one. If you use the configuration supplied by the page, remove bearer_token_env_var from that block as instructed.

For Claude Code, run it once if its configuration file does not exist. For Claude Code and Cursor, add the Supahelp entry under mcpServers; do not replace the whole file if it already contains settings.

The supplied configuration contains your token. Keep it in your private local agent configuration. Never put it in a shared project file, repository, screenshot, or chat prompt.

Use the endpoint supplied by Supahelp. Your help center address, such as help.yourcompany.com, is not the MCP endpoint. Signing in to Supahelp in a browser does not authenticate the agent.

Check the connection

Ask your agent:

“Use Supahelp MCP to call get_context. Confirm the workspace and permissions, then list the draft articles. Do not edit or publish anything.”

Check that the workspace is correct before allowing edits. Available tools depend on the permissions you selected.

If the secret is lost, create a replacement connection and revoke the old one. Supahelp cannot show the original token again.

See Edit Knowledge Base drafts with an agent and Troubleshoot MCP connections.