Somewhere connector for Claude

Ask Claude for an app. Get a live one.

Somewhere gives Claude a backend it can actually ship to: projects, hosting, a database, users, email, and a live URL. This connector is the platform surface for Claude — create, inspect, edit, deploy, verify, roll back, and run the app you asked for.

https://mcp.somewhere.tech/mcp/connector

Today: add this address in Claude as a custom connector. Once the connector is published in the Claude Connectors Directory, you will be able to add it from the directory as well. Sign in or create a Somewhere account when Claude asks.

What the connector can do

One workflow, with the platform behind it.

Each tool says exactly what it does. Read tools are marked read-only and write tools are marked for confirmation; how Claude applies those marks depends on your Claude settings. The exact tool list is what the connector advertises when you connect.

Projects and deploys
  • List your projects, read one in detail, create a new one
  • Deploy raw application source and publish it at the live URL — the platform compiles it
  • Update selected files in an existing project and deploy the change
  • Roll back to the previous release, code only by default
  • Read deploy history, including rejected and failed attempts, and snooze platform notices
Source and files
  • List files, read one file, search the source for text, or export the whole project
  • Read, write and upload project files, and get public or signed file links
  • Read the project’s generated documentation and its source index — routes, symbols, tables, dependencies
Database
  • Describe the schema: tables, columns, types, constraints, row counts
  • Apply the declared schema, run migrations, and run SQL that reads or writes rows
  • List or declare which tables are scoped to the signed-in user of your app
  • Export data, or introspect an existing table to generate its schema declaration
Users, email and domains
  • Create and sign in app users, read the current user, list users
  • Send email from an authorized project
  • Check whether a domain is available and what it costs, then add and verify a domain you own
Tasks
  • List, read, create and update tasks on the project board, with file attachments
Code, AI text and the platform API
  • Run a short script against the project’s live bindings and get its result and logs back
  • Generate a text response with a platform AI model, charged to the project
  • Read platform API endpoints in a batch of up to ten independent requests, and create, update or delete platform data in a separate batch — batches are not transactions; each request succeeds or fails on its own
Verify, security and help
  • Verify the live site in one browser flow across desktop and phone and get a structured verdict; run and read site checks
  • Run a security review of the deployed source and read its findings
  • Browse the tool catalog, read platform documentation by topic, and send yourself an account recovery link
What it deliberately leaves out

What it will not do.

A few operations are unavailable through this connector by policy, and they stay unavailable even when Claude runs code or calls the platform API through it. One more is a dashboard flow by design.

  • No AI media: no image generation, no speech synthesis, no background removal. Text responses and website generation stay available.
  • No money movement: no payment capture, release or refund. Reading refund records stays available.
  • Domain purchases are completed in the dashboard by design; availability and pricing checks stay available here.
  • No creating new credentials and no platform-internal operations through the generic API.
  • Code runs use short-lived project credentials that carry the same limits. From a terminal, the Somewhere CLI runs without these restrictions.

Building from a terminal? The Somewhere CLI is the primary surface there and needs no connector. See the MCP and CLI page

Connect

Three steps, no terminal.

  1. In Claude, open Connectors and add a custom connector with the address above. Once Somewhere is published in the Connectors Directory, you can choose it there instead.
  2. Sign in or create a Somewhere account. The free plan can start building and shipping, subject to its plan limits.
  3. Ask for what you want: “Create a project called meal-planner and deploy a page that lists this week’s dinners.”

Claude reads the project, writes the source, deploys it, checks the live URL and reports back. The same project is in your dashboard at any time.

A five-minute first test

  1. Ask Claude to create a project and deploy a single page that says hello. Expect a live address ending in somewhere.site.
  2. Open that address in your browser. Expect the page you asked for.
  3. Ask Claude what tables the project has. Expect an empty database on a fresh project, or the tables the app declared.
  4. Ask Claude to change one word on the page and deploy again. Expect the change live after the deploy completes, and a new entry in the deploy history.
  5. Ask Claude to roll back. Expect the previous page back, with your data untouched.

Claude asks for confirmation on the steps that write, as your Claude settings decide. If any step does not match, email support@somewhere.tech with the project name.

Data and permissions

You stay in control.

What Claude can reach

Only the projects your Somewhere account owns or is shared with. The connector has no direct access to your Claude chat history or memory; it receives the content you and Claude supply in each tool call — which can include file or source content you provide — plus connection and account metadata.

Confirmations

Read tools are marked read-only. Everything that creates, changes, deploys, sends or runs — deploying, editing files, SQL that writes, migrations, sending email, creating users, running code, platform API writes, task changes, rolling back — is marked for confirmation. Whether a marked tool prompts you is applied by Claude according to your Claude settings.

Rollback

Rolling back restores the previous code immediately and leaves your data untouched unless you explicitly ask to restore the previous schema, which runs through the same deployment checks.

Privacy and support

How we handle account and project data is in the privacy policy. Questions or problems: support@somewhere.tech.

Read the privacy policy

Give Claude somewhere to ship.

Add the connector, sign in or create an account, and ask for the app.

Open the dashboardRead the full server page