Connect Kwazi to Claude, Codex, Cursor or another AI assistant

Kwazi can be used by an AI assistant through MCP (Model Context Protocol). You ask in plain language ("Which contacts from Ghent haven’t booked in six months?", "Add a note to Nina: she wants a quote", "Book Nina for an intro call on Tuesday morning"), and the assistant uses Kwazi for you.

Your own assistant and subscription. Kwazi sends nothing to an AI service itself; the assistant you connect asks your site.
Your own rights. The assistant always works as the WordPress user it connects with, and sees and does only what that user may. "Only their own" contacts, app settings and every other check apply in the same way as in the app.
Never through an assistant: deleting, merging, and changes to rights, security, webhooks or what is shared with Kwazi. Those stay in the app.

Tested with MCP Adapter 0.7.0 (MCP protocol 2025-11-25 and 2026-07-28). The adapter is still before 1.0; we test every new release.

1. Install the MCP Adapter

In WordPress, go to Plugins → Add New, search for MCP Adapter (by WordPress.org Contributors) and activate it. It needs WordPress 6.9 or later. Kwazi → Integrations → AI assistants shows whether it is active.

2. Generate the prompt

In Kwazi → Integrations → AI assistants, under Connect your assistant:

Choose your program: Claude Code, Claude Desktop, Codex, Cursor or Other.
Tick that you understand an application password is made for your account.
Choose Generate prompt, then Copy.

Kwazi asks WordPress to make an application password for you, named after the program (for example "Claude Code (Kwazi)"), and puts it in the text together with the server address. The text is shown only once. Kwazi doesn’t store the password; WordPress keeps only a hashed copy.

An assistant signs in with an application password, not with your normal password. Application passwords skip two-factor login, so Kwazi only accepts them from roles you allow in Integrations → API & keys (by default only Administrator). If your role isn’t allowed, the screen says so instead of showing the button.
The assistant gets your rights. Connect with a user that has only the rights the assistant needs. The audit log shows every change an assistant makes, with the name of the application password.
The text holds a password: whoever has it can act as you on the whole website through the WordPress API, not only in Kwazi. Paste it only into your own assistant, and connect with an account that has only the rights the assistant needs.

3. Paste it into your assistant

Claude Code, Codex, Cursor: paste the text as a message. It asks the assistant to add the Kwazi server to its own configuration (Claude Code with claude mcp add, Codex in ~/.codex/config.toml, Cursor in ~/.cursor/mcp.json). Restart the program if it asks you to.
Claude Desktop: follow the text. Open Settings → Developer → Edit Config, add the configuration to claude_desktop_config.json and restart Claude Desktop. It uses the proxy package @automattic/mcp-wordpress-remote, so Node.js must be installed on your computer.
Other: the text lists the server address, your user name, the application password and the Authorization header, for any program that connects to a remote MCP server.

Prefer to set it up yourself? Choose Prefer manual configuration? on the same screen: make an application password under API & keys and use the server address shown there, for example:

https://yourdomain.com/wp-json/mcp/mcp-adapter-default-server

The web versions of Claude (claude.ai) and ChatGPT connect to remote servers with their own sign-in (OAuth), not with an application password, so this prompt doesn’t work there.

The adapter offers three tools: one to discover what Kwazi can do, one to read the details of an action, and one to run it. Your assistant uses them by itself.

4. Try it

"Find Nina Peeters and show her last appointments."
"Add a note to Nina: called back, she wants a quote for March."
"Which times are free tomorrow for an intro call? Book the first one for Nina."

Good to know

Turning an app off (Settings → Apps) also takes its actions away from assistants.
Revoking access: delete the application password in API & keys (it carries the name of the program). The assistant can no longer reach your site.
Who sees what: the adapter lists the names of the available actions to any signed-in user; whether an action may run is checked against that user’s rights every time.