webtomcp
← blog

2026-05-17 · KY · ~5 min read

How to Connect Your Website to ChatGPT Using MCP (Every Tier, Including Free)

ChatGPT's custom MCP connectors went live across every tier — Free, Plus, Pro, Business, Enterprise — in May 2026. You no longer need to pay OpenAI to give ChatGPT live access to your website. This post walks through the five-minute setup that turns any public site into a queryable knowledge base ChatGPT can cite, on whatever account you have.

What you'll have at the end

ChatGPT with a new custom connector that answers questions about your website using real, cited passages from the indexed pages. Out-of-the-box ChatGPT either guesses about your site from training data or fetches one URL per question. After this setup, it queries every page through an MCP server and returns citations.

Total time: about five minutes. No coding, no Plus subscription, no credit card.

What you need before starting

Heads up — read-only. ChatGPT's custom MCP connectors are read-only on every tier as of May 2026. They can answer questions about your indexed site, but cannot trigger writes back to your systems. (Write actions through ChatGPT are a separate workflow that requires Business or Enterprise.)

Step 1 — Index your website

Sign in to webtomcp.net with Google, click New knowledge base, paste your website URL. WebToMCP crawls the site (respecting robots.txt and the path prefix you submit), chunks each page, and embeds the chunks into a hybrid vector + keyword search index on Cloudflare's edge.

Most sites under 500 pages finish in 1–10 minutes. JavaScript-rendered sites are supported and metered per plan — Free covers 5 JS pages/month, Hobby ($9/mo) covers 100.

Tip — start narrow. If your site is huge, submit just a path-prefix at first — e.g. https://docs.example.com/getting-started indexes only that section. You can always add more knowledge bases later.

Step 2 — Copy the MCP endpoint URL

When the knowledge base flips to Ready, click into it. The detail page shows your MCP endpoint URL: 

https://mcp.webtomcp.net/batches/<your-batch-id>/mcp?key=wmcp_<your-key>

Click Copy. The URL embeds an access token (?key=) — treat it like a personal access token. Anyone with the full URL can query your endpoint.

Step 3 — Add it as a custom connector in ChatGPT

Two paths. The CLI is faster; the manual click-through is the same outcome.

Path A — CLI (one command)

npm i -g webtomcp-cli
wmcp connect chatgpt

The CLI prints copy-paste instructions for ChatGPT's settings page, with your URL already substituted in.

Path B — In ChatGPT directly

  1. Open chatgpt.com in your browser, sign in.
  2. Click your profile picture (bottom-left) → Settings.
  3. Open the Connectors tab.
  4. Click Add custom connector.
  5. Paste your MCP endpoint URL into the MCP server endpoint field.
  6. Give the connector a short name (e.g. my-docs). This is what you'll @-mention in chat.
  7. Click Add. ChatGPT verifies the endpoint and saves the connector.

Step 4 — Verify it works

Open a new chat. Type @ — your custom connector should appear in the suggested list. Pick it. Ask a question only the indexed site would know:

"What's the refund policy on this docs site? Cite the page."

ChatGPT should respond with an answer that quotes the indexed content and links the source URLs from your site. If it does, you're connected.

What ChatGPT can do once connected

ChatGPT can answer anything a human reading every page of your site would know:

Every response cites real source URLs from your indexed pages. ChatGPT no longer hallucinates pricing tier names, invents endpoints, or quotes outdated policy.

Why this matters more than a Claude connection

ChatGPT has ~150× the daily active users of Claude. When you set up a Claude MCP connection, you're enabling power users. When you set up a ChatGPT MCP connection — and ChatGPT supports it on every tier including Free — you're enabling everyone who already has a ChatGPT tab open.

For a docs site, an e-commerce store, or a knowledge base, that is a much larger audience asking your AI-integrated content the same questions they'd have asked your support team.

Troubleshooting

"Add custom connector" doesn't show up. Custom connectors rolled out across tiers in May 2026; if you don't see the option, check that your ChatGPT app/web client is on the latest version. Force a refresh (Cmd-Shift-R) or update the desktop app.

"Endpoint validation failed". Double-check the URL has both the batch id and the ?key=... query string. Re-copy from the WebToMCP dashboard. The endpoint must return MCP-compatible responses — pasting a wrong URL fails fast at this step.

ChatGPT doesn't @-mention the connector. Open the connector's settings inside ChatGPT and confirm it's enabled. Some accounts require a one-time admin approval for new connectors (Business/Enterprise tenancies).

Answers feel stale. WebToMCP re-crawls weekly by default. Click Re-crawl in the dashboard for an instant refresh.

Questions? developer@webtomcp.net. Or sign in with Google to index your own site (free).