ChatGPT and Claude

Connect a supported hosted chat to Kitecraft through a custom remote MCP connection. This path uses OAuth in your browser, so you do not need a developer key, terminal command, local agent setup, or pasted API key. For local coding agents with Bearer developer keys, see MCP setup and Set up your agent.

Custom MCP connection availability varies. ChatGPT and Claude document custom remote MCP connections for supported plans, and your workspace may need admin approval. Interface labels change, so treat the names below as guides. If your Kitecraft deployment does not offer a chat connection, chat connections are not enabled there yet. Kitecraft does not promise an App Directory listing, and not every MCP client is supported.

What OAuth connects

The remote MCP URL is https://kitecraft.ai/mcp. Copy it with the button above. Add it as a custom connector, choose OAuth, sign in through Kitecraft browser consent, and approve project read and write plus research access.

Your connected chat can read projects, business context, plans, briefs and private article materials, edit your plan, and request research. Tell it which research you authorize before it starts. Research requests use your current plan allowance. Review each request and your chat provider privacy choice before you approve, because the chat can read private materials.

The connected chat writes in its conversation or tools you give it, and follows the independent editing workflow. Kitecraft can retain the exact article, review and delivery files. An optional article destination supports an approved package through a compatible custom API or self-hosted WordPress. Squarespace uses an authorized editor handoff. Destination configuration, credential entry and exact-package approval stay in the owner browser, alongside account setup, trial checkout, Google and PostHog consent, billing and account deletion.

ChatGPT

Use Copy server URL, then Open ChatGPT above. Paste the URL into the custom MCP server form. Pasting a prompt into an ordinary conversation does not install a connection; you still review and approve it in ChatGPT.

1. Open ChatGPT Plugins, select the plus button, then Add custom MCP server.
2. Name it Kitecraft and enter https://kitecraft.ai/mcp as the public HTTPS connection URL.
3. Choose OAuth. Review ChatGPT's connection warning, create the plugin, then sign in to Kitecraft and approve access when prompted.
4. Review the discovered tools and install the connection.
5. Start a new chat, select Kitecraft with @, and ask it to start with project_context.

Some accounts still use the older Settings > Apps > Create flow. Custom connections depend on your plan, workspace permissions and current ChatGPT availability. See OpenAI's current connection instructions.

Claude

Use Connect to Claude above to open the connector form with Kitecraft and its URL already filled in. Review the connection, sign in to Kitecraft and approve access. No directory listing is required for this shortcut. See Claude install links.

If the shortcut does not open the form, use the manual setup:

1. Open Claude Customize, then Connectors.
2. Choose Add, then Add custom connector.
3. Enter Kitecraft and its MCP URL, then continue through the detected authentication settings.
4. Choose Sign in now. If an OAuth client choice appears, choose Register automatically. Kitecraft supports dynamic client registration.
5. Add the connector, complete Kitecraft sign in and approve access.
6. In a chat, enable the Kitecraft connector, then ask it to start with project_context.

See the Claude custom connector guide.

If the option is missing

If your chat app has no custom connection or connector option, check your chat plan and workspace admin settings. Do not paste a developer key into a chat prompt to work around it. If Kitecraft shows no chat connection choice, your deployment has not enabled it yet.

First prompt

Ask for a read-only project_context check first. Then ask the chat to read your saved profile, plan, and brief before it suggests new work. Do not buy research to prove the connection. Start no new research and no publishing from this first check.

Example: "Use Kitecraft project_context to list my projects, then read my saved profile and plan. Do not request research yet."

Full packet output may be chunked in chat. Ask for the next section, or read specific brief sections, rather than expecting one complete export.

Refresh tools and resume saved work

A server version does not prove this chat refreshed its tools or schemas. Compare actual discovery with the workflow advertised by project_context, including destination_prepare when reusable mappings are available. Follow Refresh a stale connection for owner-managed and workspace connections. Reconnect through the host settings when needed, start a fresh chat and retrieve a saved article and review before resuming. Never paste a credential into the conversation to repair discovery.

Recurring writing

Ask for calendar_setup after confirming the project. It returns a bounded test prompt and recurring instructions, not a running writer or a schedule. Run one authorized draft-and-independent-edit pass first. If your host supports recurring agent work, separately authorize and configure that task there. A custom MCP connection alone does not establish that the host can run it unattended. See recurring work in your own agent. Publishing remains a separate approved action.

Limits and disconnect

Google and PostHog stay disconnected until you authorize them in your browser. Billing changes stay in Billing. Disconnect the chat in Connect your agent. Work you already submitted may continue after disconnect.

Developer Bearer key access for MCP, CLI, and API remains available for local agents. See MCP setup.