ChatGPT
Add Sprout in Claude
Open Claude Web and add the connector once. It then follows your Claude account to web, desktop, and mobile.
Open Claude connector settingsSprout
https://mcp.sprout.is
Only these two fields are required. Leave Advanced settings closed, then choose Add.
I can’t find the connector form
Custom connectors are added on claude.ai in a browser, not in the mobile or desktop app. Refresh the browser settings page and try again.
Connect your Sprout account
Connect the new MCP connector to the Sprout account you want Claude to use. No account yet? The same page creates one.
- 1
Find Sprout in the connectors list and choose Connect.
- 2
On the Sprout page, choose Allow access.
- 3
Return to Claude with Sprout shown as connected.
Sprout signs you in on its own page and requests only openid, profile, and mcp:tools. Never paste a password, email link, code, cookie, or token into Claude.
I don’t have a Sprout account
Enter your email on the Sprout page; the same flow creates an account. A brand-new account must confirm its email before authorizing the connector, then you can choose Connect again.
Allow both Sprout tool groups
Open the connector and confirm Claude shows both groups published by Sprout:
- Read-only tools
- Write/delete tools
- 1
On Read-only tools, open the permission menu on the right and choose Always allow.
- 2
Do the same on Write/delete tools.
- 3
If either group is missing, refresh Claude and reopen the connected Sprout connector before continuing.
Always allow prevents a prompt for every call and includes write and delete tools. Select it only for the Sprout connector you just added.
I don’t see Always allow
Leave each group on Needs approval and approve Sprout calls as they happen; the connection still works.
Test Sprout in Claude
Start a fresh chat and send the same build prompt shown on the Sprout homepage. This version checks the connector first.
Before acting on the build request below, use Sprout's get_sprout_session tool to confirm the connector is working and connected is true. If the tool is unavailable or connected is not true, stop and explain the smallest reconnection step; do not create or change anything. Build and deploy the app I describe next using Sprout. Before acting, read and follow the current Sprout builder instructions at https://sprout.is/SKILL.md. Treat them as authoritative. Use the verified Sprout CLI when you have a terminal; use the hosted Sprout connector only when no terminal is available. Never invent or bypass APIs, credentials, IDs, URLs, or verification results. If I have not described the app yet, ask me what I want to build. Then: - Clarify only decisions that would materially change the product; make sensible defaults for everything else. - Reuse an existing app only when it clearly belongs to this project. Otherwise create a new private app unless I explicitly request a public one. - Build a complete, polished, mobile-friendly product with every requested capability. - Never ask me to paste passwords, cookies, tokens, email links, credentials, or secret values. Use Sprout’s browser approval and protected secret-entry flows. - Validate each coherent revision, test it in isolated development with synthetic data, fix failures, obtain an exact-revision verification receipt, promote that receipt, wait for deployment, and run production verification. - Do not stop after generating code, validating, or creating a preview. I authorize production deployment only for the exact revision that passes Sprout’s isolated verification for this request. This does not authorize deleting, restoring, rolling back, exposing private data, or changing unrelated apps or platform resources. Finish by giving me the canonical live URL, a concise summary of what was built, and the final validation, deployment, and production-verification results. If blocked, explain the exact blocker and the smallest action I need to take.
The prompt continues with the homepage build flow only after Sprout confirms the connector is working.
Claude doesn’t use Sprout
Refresh Claude and retry in a fresh chat. If the Sprout tool is still absent, reopen the connector and confirm both tool groups are visible.
Turn on developer mode
Developer mode lives in ChatGPT’s Security and login settings.
Open Security and login- 1
Scroll to Developer mode.
- 2
Turn it on.
ChatGPT marks this elevated risk because it permits unverified connectors. Add only connectors you trust — here, just Sprout.
There’s no Developer mode row
Open the settings page on chatgpt.com in a browser and make sure you’re signed in to the account you want to connect.
Create the Sprout plugin
Open the New Plugin form and enter these values. Icon and Description are optional.
Open ChatGPT connector settingsSprout
https://mcp.sprout.is
- 1
Keep Connection on Server URL, not Tunnel.
- 2
Keep Authentication on OAuth.
- 3
Tick I understand and want to continue, then choose Create.
OAuth sends you to Sprout’s own sign-in page in the next step. Do not enter an API key or client secret.
There’s no New Plugin form
Custom plugins appear only after developer mode is enabled. Confirm the toggle is still on and reload settings.
Sign in with Sprout
Connect the Sprout account you want ChatGPT to use. No account yet? The same page creates one.
- 1
Choose Connect on the new Sprout plugin.
- 2
In Add Sprout to ChatGPT, choose Sign in with Sprout.
- 3
On the Sprout page, choose Allow access.
Sprout sign-in happens on its own browser page. Never paste a password, email link, code, cookie, token, or client secret into ChatGPT.
I don’t have a Sprout account
Enter your email on the Sprout page; the same flow creates an account. A brand-new account must confirm its email before authorizing the plugin, then you can start Connect again.
Allow Sprout actions
If you closed the bar shown after connecting, reopen connector settings, select Sprout, and open Permissions.
Open ChatGPT connector settingsAllow all actions prevents repeated prompts and includes write and delete actions. Use it only for the Sprout plugin you just created.
Allow all actions is unavailable
Leave the available permission selected and approve write actions individually; the connection still works.
Test Sprout in ChatGPT
Start a fresh chat, choose Sprout from Tools or type @Sprout, then send the same build prompt shown on the Sprout homepage. This version checks the connector first.
Before acting on the build request below, use Sprout's get_sprout_session tool to confirm the connector is working and connected is true. If the tool is unavailable or connected is not true, stop and explain the smallest reconnection step; do not create or change anything. Build and deploy the app I describe next using Sprout. Before acting, read and follow the current Sprout builder instructions at https://sprout.is/SKILL.md. Treat them as authoritative. Use the verified Sprout CLI when you have a terminal; use the hosted Sprout connector only when no terminal is available. Never invent or bypass APIs, credentials, IDs, URLs, or verification results. If I have not described the app yet, ask me what I want to build. Then: - Clarify only decisions that would materially change the product; make sensible defaults for everything else. - Reuse an existing app only when it clearly belongs to this project. Otherwise create a new private app unless I explicitly request a public one. - Build a complete, polished, mobile-friendly product with every requested capability. - Never ask me to paste passwords, cookies, tokens, email links, credentials, or secret values. Use Sprout’s browser approval and protected secret-entry flows. - Validate each coherent revision, test it in isolated development with synthetic data, fix failures, obtain an exact-revision verification receipt, promote that receipt, wait for deployment, and run production verification. - Do not stop after generating code, validating, or creating a preview. I authorize production deployment only for the exact revision that passes Sprout’s isolated verification for this request. This does not authorize deleting, restoring, rolling back, exposing private data, or changing unrelated apps or platform resources. Finish by giving me the canonical live URL, a concise summary of what was built, and the final validation, deployment, and production-verification results. If blocked, explain the exact blocker and the smallest action I need to take.
The prompt continues with the homepage build flow only after Sprout confirms the connector is working.
@Sprout doesn’t resolve
Plugin availability is fixed when a chat opens. Start a fresh chat, select Sprout from Tools, and retry. If it is absent, reopen the plugin connection first.