Model Context Protocol (MCP)

Build websites with Claude AI

The Social AI MCP connects Claude, VS Code Copilot, Cursor and other AI tools to the website builder — create, edit, stock, and publish complete websites from chat.

Fastest setup — paste this into your AI

Copy the prompt below into any AI assistant that supports MCP — Claude, ChatGPT, Cursor, Windsurf, Copilot, Codex, Perplexity, or another client. The AI reads it, works out which kind of client it is, and walks through the correct setup itself.

Set up the Social AI website-builder MCP for me. Detect which MCP client you are running in and pick the right path:

1. If this client supports remote MCP connectors (Claude.ai, Claude Desktop, Cowork, ChatGPT developer mode, Perplexity): add the custom connector URL https://socialai.one/api/mcp, open the Social AI OAuth sign-in for me to complete, then enable the connector for this conversation. Do not use JSON files or npm for a remote connection.

2. If this client is a local CLI or IDE (Claude Code, Cursor, Windsurf, VS Code Copilot, OpenAI Codex): add the stdio server "@socialai/website-mcp" (run with npx) to my MCP configuration, preserving my existing servers, with the environment variable SOCIALAI_API_KEY. Use the placeholder sai_user_xxxxxxxx and tell me to create a real key at https://socialai.one/settings/api-keys and enter it locally myself — never ask me to paste the key into chat.

After setup, restart or reconnect the MCP, call get_started, then list my Social AI websites to verify a tool call works. Full instructions: https://socialai.one/mcp

Your AI never gets your password or API key: OAuth sign-in happens in a separate browser window, and local API keys are entered by you directly into the config file or secret store.

Step 1 — Choose OAuth or an API key

For Claude, Cowork, Claude Desktop, or another remote MCP client, use https://socialai.one/api/mcp and complete the Social AI sign-in in that client's OAuth window. No JSON, npm package, or API key is needed. For a local CLI or IDE, sign in to Social AI, go to Settings → API Keys, name a key, keep the scopes you need selected, and copy the one-time key that starts with sai_user_ directly into the local config or secret store.

Do not give an AI your Google or Social AI password. Browser sessions are isolated, so sign in in the OAuth window when prompted.

Generate API key

Step 2 — Connect your AI tool

ChatGPT developer-mode app

Use the supported ChatGPT setup page. Social AI copies the hosted MCP endpoint for you; ChatGPT still requires you to press +, paste it, and approve OAuth.

The setup button copies Social AI's reviewed OpenAI endpoint and opens ChatGPT Plugins. Existing SocialAI entitlements apply; purchases remain on SocialAI.one. Turn on Developer mode, press +, paste the URL, then complete Social AI OAuth. ChatGPT does not currently provide a supported link that can create an unpublished custom app automatically. Accounting records returned by the connector include direct Social AI verification links.

Connect another AI client

Cursor supports a true install deep link. Other clients copy the endpoint and open their supported setup surface. MCP 1.5.5 accounting results include direct Social AI verification links.

Customize → Connectors → + → Add custom connector

Remote MCP server URL:
https://socialai.one/api/mcp

Then authenticate with your Social AI account and enable Social AI for the conversation.

Use the remote server URL, then complete the Social AI sign-in when prompted.

Please add Social AI as a remote MCP connector using https://socialai.one/api/mcp. Open the OAuth sign-in for me, then enable Social AI for this conversation, call get_started, and list my Social AI websites to verify that a tool is callable. Do not use a JSON file or npm for this remote connection.

Step 3 — Say hi to your AI

Once connected, start a new chat and say:

"List my Social AI websites"

Your AI will call manage_websites and show you your websites. After creating or editing a site, ask it to call get_preview_url, open the draft link in your preferred external browser (or copy it there if the built-in browser is unreliable), and refresh after each change.