Docs · Kite

Kite hosts and shares what your AI tools make. Connect a tool once and it can publish pages to your Kite, read comments people leave, and see who opened what.

In every case the address to paste is https://kite.new/api/mcp. Your tool sends you to Kite to sign in and click Allow; nothing to copy. Signed in, the same steps are on Settings → Connect, one click from the tool you use.

Claude

About a minute. Works on claude.ai and in the Claude desktop and mobile apps, on Pro, Max, Team and Enterprise plans.

1In Claude, open Settings → Connectors. On the web that's your name, then Settings, then Connectors.
2Choose Add custom connector, name it Kite and paste the address below. Leave the advanced fields empty.
3Click Add, then Connect. Kite opens and asks you to sign in and allow Claude — click Allow.
4Back in a chat, check Kite is on under the tools menu and say: “Publish this to Kite and give me the link.”

Team and Enterprise admins can add Kite once for everyone under Admin settings → Connectors.

ChatGPT

About two minutes. Needs a Plus, Pro, Team or Enterprise plan and developer mode, which is a one-time switch.

1In ChatGPT, open Settings → Apps & Connectors → Advanced settings and turn on Developer mode.
2Back on Connectors, click Create. Name it Kite, paste the address below as the server URL and set authentication to OAuth. Leave the client fields empty.
3Click Create, then Connect, and allow ChatGPT when Kite asks.
4In a new chat, click +, pick Kite under connectors and say: “Publish this page to Kite.” ChatGPT asks you to confirm the first time.

Claude Code

Any tool that speaks MCP can use Kite. Tools that can open a browser sign in with your account; the rest use a key from below.

1Claude Code: run claude mcp add --transport http kite https://kite.new/api/mcp, then type /mcp and choose Kite to sign in.
2Cursor: in .cursor/mcp.json add {"mcpServers":{"kite":{"url":"https://kite.new/api/mcp"}}}. Cursor opens a sign-in window the first time it is used.
3Scripts and headless agents: create a key below and send it as Authorization: Bearer kite_… to the same address.
4Any agent that reads skills can install /skill.md; machine-readable context is at /llms.txt.

How it works

Kite exposes a small set of actions over the Model Context Protocol (MCP) with OAuth 2.1 sign-in. Tools that can't open a browser can use a key from Settings instead. Each connection and key can be revoked on its own.

Actions

publish_page: publish HTML or Markdown, get a link.
update_page: replace a page's content, same link.
list_pages, get_page, duplicate_page: what you've sent, with open counts; make a copy.
set_audience: anyone with the link, anyone with a code you set, verified email, or a list of people.
get_comments, reply_comment: read what viewers said and answer.
get_views, get_responses: who opened it, and form submissions.
search_pages and delete_page: find a page by what is in it, or put one in Trash.
request_upload_url: everything that is not one blob of text — a page with its images and stylesheets, a built site or folder, or a single PDF, image, spreadsheet, document or deck. Give each file a source_url and Kite fetches the bytes and publishes in that one call; give a size instead and you get a signed URL to PUT to, then call finalize_upload; or, with no URL and no way to PUT, send the bytes base64 in pieces with upload_chunk.

For agents