Install the Somewhere MCP server.

ChatGPT (web)

Access to ChatGPT custom plugins is required. Sign in to Somewhere to connect your existing projects.

Add Somewhere as a plugin

Open ChatGPT on the web → Plugins
Select + → Add custom MCP server
Name: Somewhere
Server URL: https://mcp.somewhere.cloud/mcp/chatgpt
Authentication: OAuth
Review the warning, then Create as a plugin
Install Somewhere, sign in and approve the connection

In a new conversation, type @ and select Somewhere before asking it to list your projects. Workspace permissions and security settings can restrict custom plugins.

If tools are missing or the list looks old

Open Somewhere’s app details in ChatGPT settings
Refresh the app to load its current tools and instructions
Check that the tools you need are enabled
Start a new conversation, type @ and select Somewhere

Use the ChatGPT-specific address above. The other clients on this page use the general MCP address.

Codex

OpenAI Codex CLI

Local bridge — recommended, auth rides your CLI login

npm i -g @somewhere-cloud/cli
somewhere login
codex mcp add somewhere -- somewhere mcp

Remote (streamable HTTP) — if your Codex setup manages auth itself

codex mcp add somewhere --url https://mcp.somewhere.cloud/mcp

Or let the CLI write the config for you

somewhere mcp install codex

Claude Code

Anthropic Claude Code CLI

Fastest — login configures Claude Code automatically

npm i -g @somewhere-cloud/cli
somewhere login

somewhere login writes the MCP entry for you. No extra step.

Or let the CLI write the config for you

somewhere mcp install claude-code

Cursor

Cursor editor

One command

npm i -g @somewhere-cloud/cli
somewhere login
somewhere mcp install cursor

Or manually — add to ~/.cursor/mcp.json

{ "mcpServers": { "somewhere": { "command": "somewhere", "args": ["mcp"] } } }

Claude.ai (web)

No terminal needed — the simplest install.

Connectors

Open Claude.ai → Customize → Connectors
Click + → Add custom connector
Paste https://mcp.somewhere.cloud/mcp, then Connect

Prefer the focused build-and-deploy connector (custom connector today, Connectors Directory once published)? It is documented at /connectors/claude.

Any other MCP host

Continue, Windsurf, your own agent — anything that speaks MCP.

Remote (streamable HTTP)

URL: https://mcp.somewhere.cloud/mcp
Auth: OAuth, or header Authorization: Bearer <your developer key>

Local stdio

npm i -g @somewhere-cloud/cli
somewhere login
Run as the server command: somewhere mcp

How do I know it worked?

In a new agent session, the tool list should include names like:

mcp__somewhere__project_create
mcp__somewhere__db_query
mcp__somewhere__project_deploy

Remote vs. local bridge

Remote (streamable HTTP)

Your host connects straight to https://mcp.somewhere.cloud/mcp and handles auth itself — OAuth on Claude.ai, or a bearer key on hosts that support custom headers.

Local bridge (stdio)

Your host runs `somewhere mcp`, which signs every request with your CLI login from ~/.somewhere/config.json. If `somewhere whoami` works, the bridge works — no token pasted into host config.

FAQ

What is MCP?

Model Context Protocol — Anthropic's open standard for connecting AI agents to external tools and data. The platform offers an MCP server, which means any MCP-compatible agent can use it to provision databases, auth, payments, email, file storage, and more — without writing boilerplate.

Which agents work with Somewhere?

Shell agents use the CLI; connected clients use MCP. Our recorded end-to-end runs: Claude in Cowork, ChatGPT in Work and Antigravity on September 14, 2026, each with the one-sentence prompt on the home page; and Codex from an empty folder on October 14, 2026. Other agents, including Claude Code, Cursor and Continue, and the Claude.ai and ChatGPT connectors, use the same CLI or MCP address, but we have no current end-to-end test of them on record. If your agent supports MCP, point it at https://mcp.somewhere.cloud.

I installed it but my agent doesn't see the tools — is it broken?

Almost certainly not. Most MCP hosts load tools only when a session starts, so a server that shows as configured can still be invisible to the session you already had open. Open a new session (or restart the host) after any config change. Run somewhere mcp doctor to check login, connectivity, and host config in one shot.

Do I need a Somewhere account?

To connect your existing Somewhere projects, sign in and approve access. To try a temporary app without signing up, use the account-free steps on the home page. The full core platform — database, auth, email, custom domains — is on the Free tier; paid tiers just raise the limits and add scale and support.

Can I use this with my existing Claude subscription?

Yes — that's the point. Your Claude Pro or Max subscription already covers the intelligence. Somewhere covers the infrastructure. You're not paying for Claude twice.

Can the agent write to my database and files?

Yes, but scoped to your project. The agent operates under your developer key — same scope as you. You can also set row-level scoping so end-user data is auto-isolated.

Can I see what the agent did?

Your dashboard shows activity and deployment history. Every plan rolls back to the previous working version; full deploy history and restoring any retained deploy are on paid plans, subject to database schema safety checks. In-place database restore is unavailable; export or download a copy before database changes.

What if I want to leave?

Full export. All your code, all your database, all your files. Download and run anywhere. No lock-in — we keep you because we are better, not because you are trapped.

Is there a surprise charge on AI?

No surprises. In-app AI, images, and TTS bill pay-as-you-go from a prepaid balance — you see each rate up front and can't be charged beyond what you've funded. Your connected agent runs on the subscription you already have.