Resources · Claude connector

Claude Replit connectorWhat Claude can do in your Replit account.

The Claude Replit connector exposes 5 tools. 2 look at your apps, 2 create or change one through Replit Agent, and 1 is described by no source. Here is what Claude passes on, what it asks you, and where the documentation runs out.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Claude Replit connector changes for you

You no longer have to open Replit to get an app idea started. You describe it to Claude, which hands the request to Replit Agent, Replit's coding assistant; the Agent builds it and sends back a link to the live app. Claude acts as the go-between here, and the Agent does the actual building.

Start a project in one sentence. create_app_from_prompt kicks off a new app from your description, anything from a React website to a mobile app or a spreadsheet.

Make changes without the editor. update_app_using_prompt passes the change you describe on to the Agent, once resolve_app_by_name has found the app by its exact title.

Understand an app before touching it. ask_question asks the Agent about an app without modifying it.

What Claude cannot do with this connector: it only works on apps you can edit, and the directory sheet lists no broad search and no publishing. Replit documents those tools for its own server, but they are not on the Claude connector's sheet. A fifth tool has no description anywhere. Nothing runs on its own either: no tool fires unless you ask. For hands-off sequences, you need an automation platform, a different kind of tool; the Integrations hub covers that side.

Vocabulary

The vocabulary in one minute

Five words worth knowing before you connect Replit.

Connector
The link you set up once between Claude and your Replit account, so Claude can work in it while answering you.
Tool
One named action the connector makes available to Claude, which decides on its own when to call it. The directory sheet lists them.
Authorization
Replit's sign-in screen, where you give Claude the access it will use. Granted once per person, and revocable the same way.
Approval
The confirmation Claude waits for before starting something that changes your account, shown in the chat at the right moment.
MCP
The common standard connectors are built on; it lets an assistant talk to an outside service.
Connect

Connect Replit to Claude in three steps

  1. 01

    Open the connector list

    In Claude's settings, go to Customize then Connectors and find Replit. On a Team or Enterprise plan, an Owner or Primary Owner has to enable it for the organization before you can connect.

  2. 02

    Sign in to Replit

    Click Connect on Replit's row, then sign in through the window Replit opens itself. If the connection drops, use Disconnect and reconnect from the same row.

  3. 03

    Read the authorization screen

    Go through Replit's authorization screen before you confirm: Replit, not Claude, decides how far the access reaches. You can also withdraw it later from your Replit account.

Tools

All 5 tools, grouped by effect

Replit gives Claude 5 tools: 2 that read your account, 2 that change something in it, and 1 no official source describes.

Three groups: what Claude looks at, what it starts on Replit, and what no source describes. Tool names stay as Claude shows them.

  • 2 read
  • 2 write
  • 1 not documented

What Claude looks at (2)

2 tools

Two tools that query your apps without changing them.

resolve_app_by_name

Looks up one of your Replit apps from its exact title and points Claude to it for what comes next. Replit says the match is on the full title, not a fragment.

When it helps
you name an app and Claude needs to locate it before doing anything else.
Watch out
when an app is not found, Replit's first advice is to check your rights on it (see the limits below).

Sourcedocs.replit.com · October 1, 2026 ↗

ask_question

Puts a question to Replit Agent, Replit's coding assistant, about one of your apps without altering anything in it. Claude brings the answer back into the chat.

When it helps
you want to understand how an app is built before deciding what to ask for next.
Watch out
it targets one specific app, so Claude first needs to know which one you mean.

Sourcedocs.replit.com · October 1, 2026 ↗

What Claude starts (2)

2 tools

Two tools that create or evolve an app through Replit Agent. No source gives them their own confirmation.

create_app_from_prompt

Approval: see the rule

Starts building a new Replit app from what you describe. Nine project types are available, from a React website to a spreadsheet, and the app can begin as a private copy of an existing one.

What Claude asks for
no source describes a confirmation specific to creating an app; the general approval rule further down applies.
When it helps
you have an app idea in mind and want Replit Agent to start building it from your description.

Sourcedocs.replit.com · October 1, 2026 ↗

update_app_using_prompt

Approval: see the rule

Hands Replit Agent a change to an app you already have, described in everyday language. Claude passes the request along and the Agent does the work.

What Claude asks for
no check is documented before the update starts; you fall back on the default approval behaviour.
When it helps
an existing app needs a new feature and you would rather describe it than open the editor.
Watch out
only apps you can edit are in scope, including the ones shared with you.

Sourcedocs.replit.com · October 1, 2026 ↗

Undocumented (1)

1 tool

The directory publishes this name and nothing else. No official text says what it does, and we will not guess from the name.

import-claude-design-from-url

This name appears in the directory sheet's tool list, and that is all. None of the Replit pages reviewed describes it, and no Anthropic page does either, so this page will not say more.

Watch out
whatever it actually does, the general approval rule covers it.
Approvals

What Claude asks before it acts

By default, Claude stops and asks for your go-ahead before each action it takes on an account for you. The request appears in the chat.

On Team and Enterprise, owners decide whether members can let some actions through without being asked each time. They can also cap what a connector does for the whole organization, keeping reads and blocking writes for instance, and nobody can override that from their own account. On the Replit side, Claude only reaches apps you can edit, including ones shared with you, and the Agent does the building once a request goes through.

Plans

Which plans include the connector

None of the 819 sheets in the official directory shows availability by plan. Connector by connector, that information is not published anywhere.

The general rule is on record: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables the connector for the organization before members connect. For the current state, check Replit's sheet in the directory. Only Replit documents this connector; Anthropic has no page about it.

Limits

Where the Replit connector stops

A connector is not an automation: Claude calls these tools while it answers you, and nothing starts by itself.

The directory sheet and Replit's documentation do not list the same tools. Replit documents an app search, an app list, publishing and publish status for its server, none of which are on the sheet, and the sheet includes one tool Replit does not describe. The sheet is what tells you what Claude actually has. The directory badge is not a security audit, and Anthropic does not vouch for how a publisher's tools behave.

Need help

Need help connecting Replit to Claude?

A person reads every message.

FAQ

Claude Replit connector: common questions

01What can Claude do with the Replit connector?
Claude acts as a go-between for you and Replit Agent, Replit's coding assistant. It can start a new app from your description, change an existing app, find an app by its exact title and ask the Agent a question about an app without modifying it. According to Replit, the Agent does the work and sends back a link to the live app. A fifth tool sits on the directory sheet with no published description at all.
02Can Claude create or change my Replit apps?
Yes, two tools write. create_app_from_prompt starts a new app, from a blank project or a private copy of an existing one, across nine project types. update_app_using_prompt hands the Agent a change described in plain language. Both only touch apps you can edit, including ones shared with you. The connector's sheet lists no deletion or publishing tool, and the documentation says nothing more on that front for Claude. If you need either, the Replit interface is still where that happens.
03Does Claude ask before it builds something?
By default, yes: Claude asks for confirmation before each action it takes on an account for you. No source describes a confirmation specific to create_app_from_prompt or update_app_using_prompt, so that general rule is what applies. On Team or Enterprise, owners decide whether members can let some actions through without a prompt, and they can block every write from the connector organization-wide. The undocumented tool falls under the same rule, whatever it turns out to do.
04Which plans is it available on?
No official source publishes plan availability connector by connector, and none of the 819 directory sheets shows it. The general rule is that remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, with an Owner or Primary Owner enabling them first on Team and Enterprise. Replit's sheet in the directory is the only up-to-date place to check for your own account, rather than a third-party article.
05Does Claude see every app in my Replit account?
No, only the ones you can edit. Replit's documentation says the connector works with apps you have the right to modify, including those shared with you; an app outside that scope cannot be found. To point at one, Claude uses its exact title. On Team or Enterprise, an owner can further restrict what the connector may do for the whole organization, and members cannot undo that from their own settings.
06Why doesn't Claude publish my Replit app?
Because the connector's sheet in the directory lists no publishing tool. Replit's documentation does describe a publish tool and a publish-status check for its server, but neither appears among the five tools exposed to Claude. The directory sheet is the reference for what Claude actually has. To take the app live, you go through Replit directly for now, and check the sheet again later in case the tool list grows.
07Claude or an automation tool for Replit?
They do different jobs, so it depends on the use. Claude with this connector acts when you talk to it: starting an app, requesting a change, asking the Agent about a project. An automation platform runs in the background and reacts to events with nobody involved. If you want something to fire on a schedule or whenever a form comes in, that second kind of tool is the fit, not a connector.