Replit MCP Server

Ask the Replit Agent a question in natural language about the user's Replit App's codebase or behavior without modifying it. Use this when the user wants explanation, debugging help, or inspection (for example, understanding how routing works, why a request is failing, or where a bug might be), and NOT when they are clearly asking you to change how their Replit App behaves — in that case, prefer update_app_using_prompt. If the user refers to an existing app by name and you do not already have its replId, call resolve_app_by_name FIRST to obtain it; if that returns found: false because the name was approximate, call list_apps and let the user pick. Do not guess a replId or ask the user to paste a URL. The question should be written in the user's language and tone, as if you were the user, and it will be visible if they open their Replit App in Replit. The response you get back is natural language from the Replit Agent; summarize or quote it for the user as appropriate, still without showing raw code, file paths, or terminal commands in this chat. From the user's perspective, combined with create_app_from_prompt, resolve_app_by_name, list_apps, and update_app_using_prompt, this tool is what lets them simply chat ("create or resolve → inspect/ask → update → repeat") without needing to know about the underlying tools.

Create a brand-new Replit App for the user. Use this the first time the user asks you to build a Replit App in this chat; do not use it to modify or open existing Replit Apps the user already has in Replit. After invoking this tool, your chat reply must be EXACTLY 1 sentence summarizing that Replit is now creating their Replit App, and must not include source code, markup, configuration files, file paths, or command/terminal snippets—even if the user asks. Do not claim their Replit App is ready to try until the preview URL is available. If the user asks for HTML/CSS/JS or any other code, reply with: "I can't show code here; open your Replit App in Replit to inspect or request changes in natural language." Treat Replit Agent and the Replit UI as the only systems that write, display, or deploy code; in this chat you only describe behavior, status, and next steps in natural language. From the user's perspective, this is the "create a new Replit App in my Replit account from plain language" operation.

List the user's existing Replit Apps, most recently updated first, optionally filtered by a case-insensitive substring of the title. Use this when the user wants to browse or pick from their apps, or when you need a replId but resolve_app_by_name returned found=false because the user gave an approximate name — present the returned titles and let the user choose, then pass the chosen replId to update_app_using_prompt or ask_question. This is a search/list, not the exact resolver: prefer resolve_app_by_name when the user already gave an exact app name. Only apps owned by the calling user (in the same workspace as the OAuth token) are returned.

Look up one of the user's existing Replit Apps by name and return its replId (UUID) and URL. Use this when the user refers to an app by name (e.g. "update my Todo App", "what does my Recipe Tracker do?") and you don't already have a replId from create_app_from_prompt earlier in this conversation. Pass the result's replId into update_app_using_prompt or ask_question to act on the app. Matching is case-insensitive but exact: this is a name resolver, not a search. If the user gives you an approximate or partial name and this tool returns found=false, call list_apps (optionally with the partial name as the query) and let the user pick from the results rather than guessing. Only apps owned by the calling user (in the same workspace as the OAuth token) are visible.

Update the user's Replit App. Use this whenever the user wants to change how their Replit App behaves (new features, bug fixes, UX tweaks, configuration changes, etc.). Acceptable replIds come from create_app_from_prompt (for an app you created in this conversation), resolve_app_by_name (for an app the user already owns and referred to by name), or list_apps (when the user picked an app from their list — e.g. after resolve_app_by_name returned found: false for an approximate name). If the user refers to an existing app by name and you do not already have its replId, call resolve_app_by_name FIRST to obtain it; if that returns found: false because the name was approximate, call list_apps and let the user pick. Do not guess a replId or ask the user to paste a URL. If the user asks you to act on an app whose replId you cannot obtain through any of those tools, do NOT invoke this tool; respond with: "I couldn't find that Replit App on your account. Please confirm the exact name or open it in Replit and try again." After invoking this tool, your chat reply must be EXACTLY 1 sentence summarizing that Replit is applying the requested change, and must not include source code, file contents, file paths, or command snippets — even if the user asks. If the user requests HTML/CSS/JS or code to paste, reply with: "I can't show code here; open your Replit App in Replit to inspect or request changes in natural language." Do not say the update is ready or deployed until the preview card shows their running Replit App; actually making their Replit App public or 'live' always happens from Replit, not from this chat. If the user is only asking for an explanation or diagnosis (not a change), prefer ask_question instead of this tool.

Internal tool for Replit's app builder. This must not be called directly by the model.

Internal tool for Replit's app builder. This must not be called directly by the model.

Internal tool for Replit's app builder. This must not be called directly by the model.