Emergent for ChatGPT

Build Emergent apps inside ChatGPT.

Start a build, answer the agent, and preview the running app on an inline card — without leaving the chat.

Serverhttps://mcp.emergent.sh

Transportstreamable HTTP

AuthOAuth 2.1 · PKCE

Add to ChatGPT

1. In ChatGPT, open Settings → Connectors and create a custom connector (developer mode must be enabled).
2. Set the MCP Server URL to https://mcp.emergent.sh and authentication to OAuth.
3. Save, then Connect. You'll be redirected to sign in to Emergent and approve access.
4. Once connected, ask ChatGPT to build something on Emergent — the tools appear automatically.

Codex (CLI)

Add the server, then sign in via OAuth:

codex mcp add emergent --url https://mcp.emergent.sh
codex mcp login emergent

The Emergent tools are then available to the Codex agent. (Codex reaches the same MCP endpoint; the inline app card is a ChatGPT feature.)

Typical flow

Using it

For existing work, ChatGPT 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.”
• “Open my recipe-sharing app from Emergent.”

Tools

Tool	Type	Description
create_job	write	Start a brand-new Emergent app from a natural-language task; returns the new job_id and shows the inline app card.
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	Returns a live preview URL for the running app (the inline card calls this to refresh).
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 the model 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 — ChatGPT 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

How does sign-in work?

Through OAuth 2.1 — ChatGPT opens an Emergent sign-in page where you approve access; no password is shared with ChatGPT. You can disconnect anytime from the connector's settings.

I don't see the Emergent tools.

Make sure the connector finished connecting and is enabled for the conversation. Adding a custom connector requires developer mode to be turned on in ChatGPT settings.

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

Reconnect the connector from its settings. The server status is at https://mcp.emergent.sh/healthz; if it keeps failing, contact us below.

Support

Questions or issues: [email protected].