> For the complete documentation index, see [llms.txt](https://kb.craftformswp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.craftformswp.com/documentation/for-developers/connect-ai-apps.md).

# Connect Claude, ChatGPT and other AI apps

*CraftForms PRO 2.4 and later.*

Your site can be a connector in AI apps such as Claude and ChatGPT. Once connected, you can ask in plain words: "Who arrives this weekend?", "Show me last week's enquiries about kitchens", "Mark booking 1042 as paid", "Add a note to Anna's order". The app works only through CraftForms' own tools, with the access you chose, and you can disconnect it at any time.

### What you can ask

* "How was last month?" or "How busy are we in December?": submissions, orders, revenue, arrivals and departures, and how full your rooms were.
* "Which enquiries are still waiting? Give the kitchen ones to Marta." It can move enquiries in the inbox (replied, won, lost, read) and assign them.
* "Write a reply to Anna's enquiry using our price list reply." It leaves a **draft reply** on the enquiry; you open it in **Enquiries**, click **Use this draft**, check it and send.
* "Send Tom the same answer." With **Draft and send** it emails him from your business address, after showing you the text.
* "Did the Petrovs get our confirmation email?" It reads which emails went out for a booking or enquiry (not their text).
* "The guest in room 4 didn't show up." "Mark Ivan's booking as paid, he paid cash." "Move booking 1042 to the 14th–16th." "Close the boat on Sunday." The same as the buttons on your work pages, with the same rules: a no-show only from the arrival day, dates that are taken or closed are refused, dates with bookings can't be closed until those are moved or cancelled.

Nothing can be deleted through an AI app, payments are never taken, and refunds stay in WordPress.

### Your site's address for AI apps

```
https://example.com/wp-json/craftforms/mcp
```

Replace `example.com` with your site's address. This is the address of your site's **MCP server** (MCP is the standard AI apps use to connect to other software).

### Connect

1. In your AI app, add a **custom connector** (some apps call it an MCP server) and paste the address above.
2. Click **Connect**. A window opens on your own site: sign in to WordPress if you aren't already.
3. Choose what the app may do, and which forms and catalog items it sees, then click **Allow**.

You're back in the app, connected. Nothing else to copy or paste: the app gets its own sign-in, which it renews by itself.

**In Claude Code** (the terminal app):

```bash
claude mcp add --transport http craftforms https://example.com/wp-json/craftforms/mcp
```

Then type `/mcp` in Claude Code and choose **craftforms** to sign in.

### What the app may do

You choose on your site, when you click Allow. Start from a ready-made choice:

| Choice                          | The app can                                                                                                                                                         |
| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Read only** (chosen at first) | Read forms, submissions, orders and bookings, catalog items and people                                                                                              |
| **Bookings**                    | Read and change orders and bookings (status, no-show, paid, reschedule) and catalog items (prices, stock, closed dates), read people and forms, add notes and tasks |
| **Enquiries**                   | Read, add and update submissions (inbox status, assign), read people and forms, add notes and tasks, and draft replies for you to send                              |
| **Everything**                  | Read and change all of the above, and email customers                                                                                                               |

To fine-tune it, open **Customize**: each area (Forms, Submissions, Orders and bookings, Catalog items, People, Notes, tasks and own fields) can be **None**, **Read** or **Read and change**. Changing a row switches the choice to **Custom**.

**Email customers** has its own levels:

* **None**: the app can't write to your customers.
* **Draft**: the app writes replies and leaves them on the enquiry as drafts. Nothing reaches the customer until you send it from **Enquiries**.
* **Draft and send**: the app can also email the reply itself, from your business address, the way **Enquiries** sends it. It is asked to show you the text first unless you told it to send. Sending needs **Enquiries → Setup → Send replies from this site** on, goes only to the address on the enquiry, and stops at 20 replies an hour.

Under **Which forms**, choose **Only these** to let the app see just some forms. Everything made by other forms (their submissions, orders and bookings) stays hidden from it.

Under **Which catalog items**, choose **Only these** to let the app see just some rooms, tours or products. It then sees those items, their orders and bookings, the submissions made for them, and the people behind those, and nothing else; forms show only the ones those items belong to. This part is shown only when your site has catalog items. With both limits, a record must pass both.

Only people who can manage CraftForms settings can let an app change things or email customers. Other team members with CraftForms access see **Read only** and the **Read** column, and can connect apps that read only.

Payments are never taken through an AI app, and refunds stay in WordPress.

Apps connected before this version keep exactly what they had: to let one draft or send replies, use **Change access** (below).

### See and disconnect connected apps

Every connected app is listed in **CraftForms → Settings → API Keys**, named after the app, for example **Claude (signed in)**, with what it may do, its forms and items, and when it was last used.

* **Change access** narrows or widens what the app may do, and which forms and catalog items it sees. The app keeps its connection; the change counts from its next request.
* **Revoke** and the app is out at once: it would have to ask you again.

Connecting the same app again replaces its earlier connection.

### Good to know

* Your site needs **https** and **pretty permalinks** (Settings → Permalinks, anything but Plain). AI apps look for your site's sign-in details at `https://example.com/.well-known/oauth-authorization-server`.
* The sign-in follows the MCP standard (OAuth 2.1 with PKCE). Apps register themselves, so there's nothing to set up beforehand.
* An app's sign-in lasts an hour and renews itself for up to 60 days of not being used.
* Tools that send a header instead of signing in (Cursor, scripts) can use an [API key](https://kb.craftformswp.com/documentation/for-developers/data-api.md#api-keys) as the bearer token: `Authorization: Bearer cfk_…`.
