# A customer support MCP server for Claude Code

> Connect a hosted customer support MCP server to Claude Code, Codex or Cursor, install the chat widget from your terminal, and keep human approval.

You connect Pommy to Claude Code with one command against its hosted MCP endpoint at https://api.pommy.ai/mcp, then sign in and choose which projects the agent may reach. With the access you grant, it can read project status, add knowledge base content and fetch the widget snippet. It cannot delete a project or change billing.

Published: 2026-11-09 · Last updated: 2026-11-09

## What are the two directions of MCP in support?

MCP is used in support in two opposite ways, and vendors often mean only one. In the first, your **support assistant is the client** and calls someone else's server to look up an order. In the second, your **coding agent is the client** and calls the support platform to configure it.

This article is about the second. The first is [external tools over MCP](/docs/ai-assistant/external-tools-mcp), and the Free plan includes no external MCP servers. Connecting your coding agent is a separate thing with its own page: [Connecting a coding agent](/docs/coding-agents/connect-your-agent).

## How do you connect from Claude Code, Codex, Cursor and VS Code?

The endpoint is streamable HTTP behind OAuth. Copy the address from the **Coding Agents** page in Pommy, because the development environment has a different one.

Claude Code

```
claude mcp add --transport http pommy https://api.pommy.ai/mcp
```

Codex

```
codex mcp add pommy --url https://api.pommy.ai/mcp
```

Cursor, ~/.cursor/mcp.json

```
{
  "mcpServers": {
    "pommy": { "url": "https://api.pommy.ai/mcp" }
  }
}
```

VS Code, .vscode/mcp.json

```
{
  "servers": {
    "pommy": { "type": "http", "url": "https://api.pommy.ai/mcp" }
  }
}
```

Then sign in. In Claude Code the sign-in starts with `/mcp`, in Codex with `codex mcp login pommy`, and Cursor and VS Code open the browser themselves. A consent screen asks which projects the agent may touch.

## What does a first session look like?

These are example prompts rather than a recording. Each maps to a real tool in the [published list](/docs/coding-agents/connect-your-agent), and the tool names are the ones your agent will show.

| You ask | The agent uses | What happens |
| --- | --- | --- |
| What is my project missing? | `pommy_project_status` | Lists assistant, knowledge base, widget and channel state, and the single next step |
| Add the chat widget to this site | `pommy_get_widget_embed_code` | Fetches the snippet, and the agent pastes it into the codebase it is already editing |
| Import our help centre | `pommy_import_urls` | Imports up to 20 pages or Markdown files. Safe to repeat with the same list |
| Why was this answer wrong? | `pommy_get_conversation` | Reads the conversation so you can fix the source content |

## What can the agent never do?

The tool list is fixed. There is no tool for deleting a project, changing billing, managing your team or publishing a journey. Tools that change anything are only offered when you grant write permission, and without it the agent does not even see them. It also cannot write into a conversation as you.

## How do consent and revocation work?

- The agent acts as you, with your permissions and nothing more, and only on the projects you ticked.
- Access is re-checked on every call. If you lose access to a project, the agent loses it at once.
- Changes go through the same validation, quota and audit trail as the dashboard.
- The **Connected** card on the Coding Agents page shows every authorized agent, and **Revoke** ends its access to every project.

## Can the agent draft a journey without publishing it?

Yes. `pommy_draft_journey` writes a draft, refuses to touch a live journey, and never publishes, because publishing stays a human decision. Journeys themselves are off by default and we switch them on per project once domain verification, a verified domain and your written agreement are in place. See [writing a journey](/docs/journeys/writing-a-journey).

## What can the agent change?

| Area | Tools that make changes |
| --- | --- |
| Assistant | `pommy_create_agent`, `pommy_update_agent`, `pommy_update_agent_instructions` |
| Knowledge base | `pommy_add_document`, `pommy_update_document`, `pommy_scrape_url`, `pommy_import_urls`, `pommy_upsert_faq` |
| Widget | `pommy_create_widget`, `pommy_update_widget`, `pommy_delete_widget` |
| Domains | `pommy_add_domain`, `pommy_verify_domain` |
| Showcase cards | `pommy_upsert_product`, `pommy_delete_product` |

A second call to `pommy_add_document` with the same page address updates that document instead of adding a copy, and `pommy_delete_widget` refuses the widget your site is showing. `pommy_usage` shows the plan and quota, so the agent can tell you what is left before a limit refuses its next write.

## How do you debug a wrong answer from a transcript?

Ask the agent to read the conversation with `pommy_get_conversation`, then ask what source the answer came from. The usual fix is content: a missing or outdated document, updated with `pommy_update_document` or `pommy_add_document`. Check `pommy_list_documents` afterwards, since new content takes a few minutes to become searchable. New instructions apply to conversations that start after the change.

## What if something does not work?

| What you see | What it means | What to do |
| --- | --- | --- |
| The agent asks which project to use | The connection covers more than one project | Ask it to list your projects first |
| It reads everything but cannot change anything | The connection was granted read-only permission | Reconnect and check the change line on the consent screen |
| Every call reports it can reach no project | The grant was revoked or you lost access | Start the connection again and pick the projects |
| A new document is not used yet | Indexing takes a few minutes | Check it with `pommy_list_documents` |

## What else should you know about the Pommy MCP server?

### Does this replace the dashboard?

No. Nothing in Pommy depends on it. It is for people who already work in a terminal. If that is not you, use [the integrations](/integrations) and the dashboard.

---

Read this page on the web: [A customer support MCP server for Claude Code](/blog/customer-support-mcp-server-claude-code)
