Connect your AI app

Connect ChatGPT, Claude or any MCP client to your WordPress site. You need a flitagent.com account and a site with FlitAgent installed and a public HTTPS address.

Connect your site first

In wp-admin open FlitAgent → Connect and click Connect to flitagent.com. Log in to your flitagent.com account, or create one and verify your email address. On the page that asks to connect your site to FlitAgent, keep Read and propose changes or pick Read only under Access, click Approve and wait for Connected. You do this once per site. Every change an AI tool proposes still waits for you in FlitAgent → Approvals, unless you turned on auto-approve for that tool. You can change the access later in the site's wp-admin, under FlitAgent → Settings.

Connect ChatGPT

ChatGPT Plus and above, on the web.

App menus change often; if a step does not match, tell us through the contact page.

Open Plugins in ChatGPT. Open ChatGPT Plugins at chatgpt.com/plugins, click + and choose Add custom MCP server. Set up for ChatGPT in FlitAgent → Connect links there too.
Describe the server. Name it FlitAgent and, under Connection, paste https://mcp.flitagent.com/. Under Authentication, choose OAuth.
Create and install. Confirm the warning, click Create as a plugin, then install FlitAgent from your plugins. ChatGPT opens flitagent.com. Then go on with Allow.

Connect Claude

Claude Pro, Max, Team and Enterprise.

App menus change often; if a step does not match, tell us through the contact page.

Open Connectors in Claude. In Claude, open Settings, then Connectors, and click Add custom connector. Set up for Claude in FlitAgent → Connect opens this form with the name and address already filled in.
Describe the connector. Name it FlitAgent, paste https://mcp.flitagent.com/ and click Add.
Connect. Claude lists FlitAgent as a connector; click Connect to start the login. Claude opens flitagent.com. Then go on with Allow.

Manual configuration

Claude Code, Codex and every other MCP client use the same address. Each opens flitagent.com to log in: then go on with Allow. More detail in the docs: Claude Code and MCP clients.

Claude Code

Run this in a terminal, then in Claude Code type /mcp, choose flitagent and Authenticate.

claude mcp add --transport http flitagent https://mcp.flitagent.com/

Codex

Run these in a terminal; the second command opens flitagent.com to log in.

codex mcp add flitagent --url https://mcp.flitagent.com/
codex mcp login flitagent

Other MCP clients

Add a remote (HTTP) MCP server with the address https://mcp.flitagent.com/ and OAuth authentication. The client opens flitagent.com to log in.

Allow the app on flitagent.com

Log in to your flitagent.com account. flitagent.com asks whether to connect the app to your account and lists each of your sites under Access type for this site, with its access: Read and propose changes or Read only. Click Allow. The app gets what each site allows and follows a change straight away, and FlitAgent → Connect on each site shows it as Connected right away.

Ask something

Start a chat, choose FlitAgent and ask, for example, "Check my site's health." With several sites on your account, name the site.

If it does not connect

Check the site first: FlitAgent → Connect shows Connected and when flitagent.com last reached the site. Site not reachable
Run Test connection under FlitAgent → Settings. It checks HTTPS, permalinks, the endpoint and whether the headers flitagent.com sends reach PHP, each with a one-line fix. Test connection
ChatGPT connected but lists no tools: the server was created without OAuth. Edit the server and set Authentication to OAuth.
Claude shows "No sign-in" or asks for a header: the connector was added without OAuth. Remove it and add it again with https://mcp.flitagent.com/ only; Claude detects OAuth from the address.
The app lists no write tools: the site allows Read only. To allow changes, choose Read and propose changes under FlitAgent → Settings in its wp-admin; connected apps follow it straight away, with no need to reconnect.
Another WordPress plugin answers instead of FlitAgent: select FlitAgent explicitly in the chat.
Still stuck: write to us with the plugin version, what Test connection reports and what flitagent.com's check page says. Contact