> For the complete documentation index, see [llms.txt](https://ce-docs.keywordrush.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ce-docs.keywordrush.com/ai-agents/connect-other.md).

# Connect any other assistant

ChatGPT and Claude are the easiest to set up, but Agent Access is a standard interface — **any** assistant or tool that can call a web API can drive Content Egg. There are two ways to connect, and your tool will support one or both.

**Before you start,** finish [**Turning on Agent Access**](/ai-agents/turning-on-agent-access.md) so you have your application password and your site's links.

{% hint style="success" %}
**The no-setup path.** Assistants that can act on your behalf — agent and coding tools like Claude Code, Cursor, or ChatGPT's agent mode — usually don't need any of the configuration below. Paste your **agent guide link** into the chat, give it your WordPress username and application password, and ask. It reads the guide and starts working. The two paths below are for making a permanent, reusable connection.
{% endhint %}

### Path 1 — Web API tools (OpenAPI)

If your tool can import an **OpenAPI** document and use **Basic authentication** — this covers Custom-GPT-style actions, many no-code automation tools, and code you write yourself — give it:

* Your **OpenAPI link** (`…/wp-json/content-egg/v1/openapi`)
* **Basic auth**: your WordPress **username** + **application password**

The tool reads the OpenAPI link to learn everything it can do; the application password lets it log in.

### Path 2 — MCP tools

If your tool speaks **MCP** — this covers Claude Desktop, Claude Code, Cursor, and other MCP clients — give it:

* Your **MCP endpoint** (`…/wp-json/content-egg/mcp`)
* Your WordPress **username** + **application password**

The MCP endpoint requires the free **WordPress MCP Adapter** plugin (see [**Connect Claude**](/ai-agents/connect-claude.md) for how to install it).

{% hint style="info" %}
**The one tip that helps every assistant:** hand it your **agent guide link** (`…/wp-json/content-egg/v1/agent-guide`). It's a short, plain-language playbook that tells the assistant what your site can do and which kind of block to use when. Most tools have an "instructions" or "system prompt" box — paste the link (or its contents) there.
{% endhint %}

### A few common tools

* **Claude** — no MCP needed. Allow your site's domain in Claude's settings, then give it your **agent guide link** plus your WordPress **username** and **application password**; it calls the REST API directly. **Claude Code** works the same way with nothing to allow. See [**Connect Claude**](/ai-agents/connect-claude.md). (The MCP endpoint remains an option if you'd rather store credentials in a local config file.)
* **Cursor** — as an agent tool it works the same no-setup way (guide link + credentials, direct REST). Or, for a permanent connection, point its MCP client at your **MCP endpoint** (requires the MCP Adapter).
* **Your own scripts** — call the REST API directly with the application password. The [**For advanced users**](/ai-agents/advanced.md) page has the technical details.

Whatever you connect, the rules are the same: it acts as the WordPress user you gave it, everything is logged, and your secrets stay hidden. See [**What your assistant can and can't do**](/ai-agents/safety-and-permissions.md).