Use ProjectHQ from ChatGPT, Claude or Cursor
Connect ChatGPT, Claude, Claude Code or Cursor to all your ProjectHQ sites at once, ask about rankings, traffic and content, and let it write drafts.
Connect ProjectHQ to the AI assistant you already use — ChatGPT, Claude, Claude Code, Cursor or any other app that supports MCP (Model Context Protocol). Then ask it about your sites in plain words: "Which pages lost traffic this week?", "What did visitors ask in the chat today?", "Draft an article on the keyword we're closest to page one for." One connection can cover all your sites, so you connect once and ask about any of them.
What your assistant can do
Every connection can read the sites it covers:
- Analytics — visitors, traffic over time, top pages and sources, live visitors, notable spikes and drops, events and goals.
- Search — your keyword rankings, Google Search Console clicks and queries, indexing status, and Bing data.
- Content — your articles, publications, content plan and documentation.
- SEO — site audit issues, insights and your webpages.
- Leads — contacts, chat conversations and your Knowledge Base.
- Notifications — what happened on your sites lately.
When you approve the connection, you can also let it do more:
- Allow editing content — create and edit draft articles and documentation pages, and upload images. Drafts wait for you in Publications; editing a published page doesn't change the live version until the edit is published.
- Allow publishing (only together with editing) — publish articles and documentation pages, putting them live on your site or connected blog, and take them down again.
- Allow changes to your project — track new keywords in the Rank Tracker (this uses your plan's keyword allowance), pause and resume automations, move contacts between lead board stages, tag contacts and add web pages to your Knowledge Base.
A connected assistant can never delete anything, send email or change your settings.
Note: A connected assistant can read your contacts and conversations. Connect only assistants and accounts you trust with that data.
Connect your assistant
- In ProjectHQ, click Settings at the bottom of the menu.
- Open AI tools (MCP).
- Under Server URL, copy the address with the copy button. It is the same for everyone and for every site:
https://api.projecthq.pro/v1/mcp - Pick your assistant's tab and follow the steps (also below).
- When your assistant opens the ProjectHQ sign-in, sign in and approve the connection (next section).
ChatGPT
- Open Settings → Apps & Connectors → Advanced settings and turn on Developer mode.
- Go back to Connectors and click Create (or Add custom connector).
- Paste the server URL and choose OAuth authentication.
- Click Connect, sign in to ProjectHQ and choose the sites to connect.
Claude (web and desktop)
- Open Settings → Connectors → Add custom connector.
- Paste the server URL and confirm.
- Click Connect — a ProjectHQ window opens where you sign in and choose the sites.
Claude Code
Run this in your terminal:
claude mcp add --transport http projecthq https://api.projecthq.pro/v1/mcp
Then run /mcp inside Claude Code, choose projecthq and Authenticate.
Cursor
Add this to .cursor/mcp.json in your project (or the global one in ~/.cursor):
{
"mcpServers": {
"projecthq": {
"url": "https://api.projecthq.pro/v1/mcp"
}
}
}
Then click Connect next to the server in Cursor Settings → MCP.
The menus in ChatGPT, Claude and Cursor change from time to time. If a step doesn't match, look for "connectors", "custom connector" or "MCP servers" in your assistant's settings.
Approve the connection
When your assistant sends you to ProjectHQ, you see Connect … to ProjectHQ:
- Check what it will be able to read.
- Tick Allow editing content, Allow publishing or Allow changes to your project if you want it to do more than read. Leave them unticked for read-only access.
- Under Sites, choose what the connection covers:
- All my sites is ticked to start with. It covers every site you own or were added to — including sites you add later, with no need to connect again.
- To connect only some of them, click a site to untick it. The connection then covers the sites left ticked.
- Click Authorize.
You're sent back to your assistant, and it's ready. The approval link works once and expires after 15 minutes — if you see This request is no longer valid, start the connection again from your assistant.
To change what a connection may do (for example, to allow editing), disconnect it and connect again with the boxes ticked or unticked.
Ask about more than one site
When a connection covers more than one site, tell your assistant which site you mean — by its name or domain: "How did kettleandcrema.com do last week?" The assistant can list the sites the connection covers, and if you don't say which site, it asks you or answers for each one.
Add or remove a site later
- All my sites: nothing to do. A site you add to ProjectHQ, or one someone shares with you, is covered on the assistant's next request.
- Chosen sites: open the site you want to add, then Settings → AI tools (MCP). Under Your other connections, click Add this site next to the assistant. It can use the site on its next request — you don't sign in again.
To take a site out of a connection, open that site's AI tools (MCP) settings and click Remove this site next to the assistant. Its other sites stay connected.
See and disconnect assistants
Settings → AI tools (MCP) → Connected assistants lists every assistant connected to the site you're in: who connected it, when, and when it was last used. Each shows what it may do — Read only, Can edit drafts, Can edit and publish or Can change the project — and, for your own connections, whether it covers All your sites or how many.
- Remove this site appears on your connections that also cover other sites. It takes only this site out.
- Disconnect cuts the assistant off from this site. A connection left with no site stops working.
Both take effect immediately.
Use an API key instead (advanced)
For scripts and tools that can't sign in, use an API key. In AI tools (MCP), open API key, click Generate API key and copy it straight away: it's shown only once. Send it as a bearer token in the Authorization header to the same server URL.
An API key gives read access to one site only — the site whose settings you generated it in. Editing always needs a signed-in connection. Treat the key like a password. Regenerate replaces it with a new one; Revoke turns it off. Assistants connected by signing in aren't affected by either.