Build Emergent apps inside Claude.

Add Emergent as a custom connector, start a build, answer the agent, and see a preview of the running app.

Serverhttps://mcp.emergent.sh

Transportstreamable HTTP

AuthOAuth 2.1 · PKCE

Add to Claude

Emergent works on Claude Free (one connector), Pro, Max, Team, and Enterprise. Custom connectors are currently in beta.

Pro & Max

Open Customize → Connectors.
Click +, then Add custom connector.
Enter the remote MCP server URL https://mcp.emergent.sh. Leave Advanced settings empty — the connector registers OAuth clients automatically.
Click Add, then Connect and sign in to Emergent to authorize access.
In a chat, turn the connector on from the + → Connectors menu, then ask Claude to build something on Emergent.

Team & Enterprise

An Owner adds it once: Organization settings → Connectors → Add, hover Custom and choose Web, enter https://mcp.emergent.sh, and click Add. Members then open Customize → Connectors, find Emergent, and click Connect.

Claude Code (CLI)

Add the server, then authenticate from a session:

claude mcp add --transport http emergent https://mcp.emergent.sh

Open Claude Code, run /mcp, and complete the OAuth sign-in. The Emergent tools are then available to the agent.

◆

Each preview comes with a link to the live app, so you can open and interact with it in a new tab.

Typical flow

01create_jobDescribe the app you want.

02wait_for_jobThe agent asks its first question.

03send_messageAnswer it, or request a change.

04get_job_previewSee a preview of the running app.

Using it

For existing work, Claude calls list_jobs first to find the job, then get_job_status or send_message. Some example prompts:

“Build me a todo app on Emergent with categories and due dates.”
“What's the status of my Emergent app?”
“Show me a preview of the app I built on Emergent.”
“Tell my Emergent app to add a dark-mode toggle.”
“List my recent Emergent jobs.”

Tools

Tool	Type	Description
`create_job`	write	Start a brand-new Emergent app from a natural-language task; returns the new `job_id`.
`wait_for_job`	read-only	Long-poll a new job until the agent asks its first question or finishes.
`send_message`	write	Send a message to a job's agent — answer, feedback, or a change request.
`list_jobs`	read-only	List your jobs (newest first) to find a `job_id`.
`get_job_status`	read-only	A job's run state plus its recent messages.
`get_recent_trajectories`	read-only	Recent conversation history for a job.
`get_job_preview`	read-only	Live preview URL for the running app.
`pause_job`	write	Pause a running job; it can be resumed later.

Every tool declares a human-readable title plus readOnlyHint, destructiveHint, and openWorldHint, and an outputSchema so Claude understands each result.

Building and iterating on apps consumes Emergent credits from your account. The connector has no purchase, billing, or plan-management tools — it only builds and manages jobs.

Authentication & security

OAuth 2.1 with PKCE and Dynamic Client Registration — Claude registers itself; no manual client setup.
Discovery at /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server.
Every call is bearer-gated and scoped to gateway.mcp; the connector acts only as you — it can't see another user's jobs.
All traffic is HTTPS.

Privacy & data

The connector accesses only your authenticated Emergent account's jobs and forwards your prompts to the Emergent agent to build and manage them. It does not sell your data. Previews may be cached briefly on Emergent's CDN (Amazon CloudFront). See the connector Privacy Policy for collection, usage, storage, third-party sharing, retention, and contact details.

FAQ & troubleshooting

Which Claude plans are supported?

Free (one connector), Pro, Max, Team, and Enterprise. Custom connectors are currently in beta. On Team/Enterprise, an Owner adds the connector and members connect individually.

How does sign-in work?

Through OAuth 2.1 — Claude opens an Emergent sign-in page where you approve access; no password is ever shared with Claude. You can revoke access anytime from Customize → Connectors.

I don't see the Emergent tools in a chat.

Make sure the connector is turned on for that conversation from the + → Connectors menu, and that you finished Connect and authorized access.

It says it can't connect, or asks me to reconnect.

Re-run Connect from Customize → Connectors. If it keeps failing, the server status is at https://mcp.emergent.sh/healthz; otherwise contact us below.

Support

Questions or issues: [email protected].