The Replit MCP Server is in beta. Tools and behavior may change.
Server details
Requirements
For developers:- An MCP client or SDK that supports Streamable HTTP transport
- A Replit account (Free, Core, Pro, or Enterprise)
Authentication
The server uses OAuth 2.1 with PKCE. MCP clients like Claude Code handle the entire flow automatically. If you’re building with an MCP client SDK, it handles discovery, dynamic client registration, PKCE, and token exchange — you provide the UX (browser redirect, callback handler, token storage). See the MCP authorization spec for details.Connecting
Configure the server URL in your MCP client. Builders will complete the OAuth consent flow when they first connect. MCP SDK (TypeScript):TypeScript (MCP SDK)
Claude Code
Tools
The server exposes three public tools.create_app_from_prompt
Create a new Replit App from a natural language description. Replit Agent immediately starts building the app.
Response:
replUrl to track progress. Use replId and replUrl in subsequent tool calls.
update_app_using_prompt
Make changes to an existing Replit App. Use this to add features, fix bugs, or iterate on the app after it has been created.
ask_question
Ask Replit Agent about the current app. Runs in discussion mode — it won’t modify the app. Use this to check build status, ask about the tech stack, or relay builders’ questions.
Example workflows
These examples show the prompts an MCP client can translate into Replit tool calls. The exact phrasing is flexible.Create and iterate on an app
Start with a detailed product prompt:Create a mobile-friendly neighborhood seed-swap app. Include seed listings, pickup requests, profiles, and a warm, garden-inspired visual style. Name it Seed Circle.Your client calls
create_app_from_prompt, which returns a replId and replUrl. Replit Agent continues building asynchronously, so open the returned URL to follow progress.
After the first build, request a focused change:
Add filters for plant type and pickup distance. Keep the existing visual style and make the filters easy to use on mobile.Your client calls
update_app_using_prompt with the original replId. You can continue sending changes against the same app.
Ask about an app without changing it
Useask_question when you need context instead of an edit:
Which database tables does this app use, and where is the pickup request flow implemented?The tool runs Replit Agent in discussion mode. It can explain the app or report build progress without modifying files.
Hand off between clients
ThereplId identifies the app across MCP calls. Store it with the conversation, then provide it when another client continues the work.
For example:
- Create an app from Claude Code.
- Open the returned
replUrlto review the live build in Replit. - Continue iterating from another MCP client using the same
replId.