The Stripo MCP server exposes Stripo as Model Context Protocol (MCP) tools, so AI agents can find, read, create and edit your emails, generate and edit images, export HTML and maintain Business Profiles — without you opening the editor.
The Stripo plugin adds skills: ready-made workflows that guide the agent through creating an email from a brief or reference, editing an existing email or template, and building a Business Profile. The plugin is free and works in Claude (chat and Cowork), Claude Code, OpenAI Codex and Cursor.
Set up both the connection and the plugin. To create and edit emails, the agent needs the Stripo plugin as well as the MCP connection. A connection without the plugin gives the agent the tools only. The skills build the email as a native, editable Stripo email, validate it against the Stripo editor and check the saved desktop and mobile previews.
The plugin doesn't include the connection: you set up the MCP connection with your workspace's Client ID and install the plugin separately.
The server endpoint is:
https://mcp.stripo.email/mcp
Choose your setup
First get your Client ID, then follow the guide for your AI tool. Each guide sets up the connection and the plugin, so the agent gets the Stripo tools and skills. Another AI tool gets the tools only.
You use | Setup |
Claude: chat on the web, desktop or mobile, and Cowork | Custom connector + Stripo plugin |
Claude Code, in a terminal or in the Code tab of Claude Desktop | MCP server + Stripo plugin |
MCP server + Stripo plugin | |
MCP server + Stripo plugin | |
MCP server + Stripo plugin | |
MCP server only |
How the connection works
Model Context Protocol (MCP) is an open standard that lets AI agents communicate with external services and take actions on your behalf. The Stripo MCP server is hosted by Stripo; your AI tool connects to it over the internet.
Authentication
The connection uses OAuth 2.0. When you connect an AI tool, you sign in to Stripo in the browser with your own account — email and password, Google or your company SSO — and the tool receives an access token. You don't put a password or API key into the configuration.
Stripo doesn't support automatic client registration. Instead, each workspace has a Client ID that you enter in your AI tool once. The Client ID identifies the workspace's connection, not you, and there is no client secret. It isn't a password, but keep it out of public repositories and publicly shared prompts.
The agent acts with the permissions of the Stripo user who signed in, in every workspace and project that user can access. It can't do anything that is unavailable to that user. To work as another user, sign out of the connection and sign in with that account.
Your AI tool refreshes access automatically. You may need to sign in again after a long period without use, after signing out, or after the workspace's Client ID changes.
Before you start
Requirement | What you need |
Stripo plan | Medium, Pro or Prime. |
Stripo role | An Owner or Admin turns on the integration and copies the Client ID. Any workspace member can then connect with it. |
Stripo account | A confirmed email address and sign-in with email and password, Google or your company SSO. |
AI tool | Claude chat or Cowork; Claude Code; the Codex app or Codex CLI; Cursor; or another AI tool that supports remote MCP servers with OAuth. |
For the plugin skills | Claude chat and Cowork run the skills in Claude's code execution environment. Claude Code, Codex and Cursor run them on your computer and need Node.js 20.18.1 or later. Adding the plugin marketplace in Codex needs Git. Saving a Business Profile with the business-profile skill also needs Python 3.11 or later with the plugin's runtime packages and Node.js 20.19, 22.12 or later; the plugin's README lists the install commands. |
In Claude Code, Codex or Cursor, you can check what is missing on your computer. After installing the plugin, ask the agent: Run the Stripo plugin's scripts/doctor.mjs and tell me what is missing. Its Python checks (python311, brandkitRuntime, resvgPy) matter only for saving a Business Profile.
Get your Client ID
In Stripo, click your organization name in the top-right corner and open Settings.
Go to Workspace → Workspace Configuration.
Find MCP integration and turn on Connect AI tools.
Click Copy Client ID.
If the toggle is disabled and you see “Available on Medium, Pro and Prime”, your workspace needs an eligible plan. If you aren't an Owner or Admin, ask one of them for the Client ID.
In the commands and settings below, replace YOUR_CLIENT_ID with this ID. Keep the surrounding quotes exactly as shown; in a form field, paste the ID without quotes.
Set up Claude (chat and Cowork)
These steps cover Claude chat on the web, in the desktop app and on mobile, and Cowork in Claude Desktop. You add Stripo as a custom connector, add the Stripo plugin from its GitHub marketplace and allow the plugin's skills to reach Stripo. You need your workspace's Client ID.
The connector and the plugin are saved to your Claude account, so you set them up once for both chat and Cowork.
Step 1. Add the Stripo connector
In Claude Desktop, click your name in the bottom-left corner, open Settings and select Connectors under Customize. On the web, open Customize → Connectors.
Click + Add → Add custom connector.
Enter the name
stripo-mcpand the server URLhttps://mcp.stripo.email/mcp, then click Continue.Under OAuth client, select Use your own OAuth client. If Register automatically is preselected and marked Detected, change it.
Paste your Client ID into OAuth client ID. Leave OAuth client secret empty; no request headers are needed. Click Add.
On the connector's page, click Connect and sign in to Stripo in the browser. Then return to Claude.
On Claude Team or Enterprise, a Claude Owner adds the connector for everyone in Organization settings → Connectors → Add → Custom → Web, with the same URL, Use your own OAuth client and the Client ID. Each member then opens Customize → Connectors, finds stripo-mcp and clicks Connect to sign in with their own Stripo account.
Step 2. Add the Stripo plugin marketplace
On claude.ai or in Claude Desktop, open Customize → Plugins and click Add → Add marketplace. In Claude Desktop, you can do this in the Chat tab or in Cowork.
Select Add from a repository and enter the Stripo plugin repository URL:
https://github.com/stripoinc/agent-pluginClick Sync.
Claude adds the marketplace and displays the Stripo plugin.
Step 3. Install the plugin
In the plugin list, find the Stripo plugin and click +.
Open the Stripo plugin. The Skills tab lists the Stripo skills.
The plugin has no connector of its own: its skills use the Stripo connector from step 1. In a chat or a Cowork task, type / or click + to see the Stripo skills.
Step 4. Allow network access for the skills
The connector talks to the Stripo MCP server and needs nothing configured here. The skills do more than call tools: they download the email's model and previews from temporary Stripo links, upload the edited model back and read images from Stripo's image hosting. These commands run in Claude's code execution environment, in chat and in Cowork, which needs outbound access to these Stripo domains.
In Claude Desktop or on claude.ai, click your name in the bottom-left corner and open Settings → Capabilities.
Under Code execution and file creation, turn on Run code in the cloud and Allow network egress.
Keep Domain allowlist set to Package managers only.
In Additional allowed domains, enter
*.stripocdn.emailand click Add.Enter
stripo-mcp-content-live.s3.eu-west-1.amazonaws.comand click Add.Start a new chat or Cowork session.
If a skill has to reach another site, for example a website you give as a reference, add that domain too. On Claude Team or Enterprise, an Owner sets these options for the organization in Organization settings → Capabilities.
Tool permissions
By default, Claude may ask for confirmation before using a Stripo tool. You can set frequently used tools that read data or check a job's status, such as whoami, find_projects, find_content, get_screenshot, get_content, get_document_state, get_image_job and get_business_profile, to Always allow.
Keep confirmation on for tools that change your workspace: create_email, create_folder, set_document_state, delete_content, patch_business_profile and replace_business_profile. Also keep it on for generate_image and edit_image: each call spends your project's AI image quota.
Update the plugin
Open Customize → Plugins.
Click Add → Add marketplace, enter the Stripo repository URL again and click Sync. Claude re-reads the repository, even when it reports that the marketplace is already added.
Open the Stripo plugin and click Update.
If the plugin page still shows the previous version, quit Claude Desktop completely and open it again: closing the window leaves the app running. If that doesn't help, remove the Stripo plugin and the marketplace, then add them again. The Stripo connector and your sign-in stay unchanged.
Set up Claude Code
These steps work in Claude Code in a terminal and in the Code tab of Claude Desktop. You need your workspace's Client ID.
Step 1. Connect the Stripo MCP server
In your terminal, run:
claude mcp add --transport http --scope user --client-id "YOUR_CLIENT_ID" stripo-mcp https://mcp.stripo.email/mcp
--scope user makes the connection available in all your projects. Stripo doesn't require a client secret.
Step 2. Install the Stripo plugin
Start Claude Code in your working folder with claude. In the session, add the marketplace and install the plugin:
/plugin marketplace add stripoinc/agent-plugin
/plugin install stripo@stripo
If the install summary asks you to run /reload-plugins, run that command.
To install the plugin from the terminal or a script instead, run:
claude plugin marketplace add stripoinc/agent-plugin
claude plugin install stripo@stripo
Step 3. Sign in to Stripo
Run /mcp, select stripo-mcp and choose Authenticate. Sign in to Stripo in the browser and return to Claude Code.
You can also sign in from the shell with claude mcp login stripo-mcp (Claude Code 2.1.186 or later).
Step 4. Verify the connection
Check that the server is connected:
claude mcp list
Then start a new session and run the verification prompts. You can call a Stripo skill as /stripo:<skill-name>, for example /stripo:email-from-reference. Claude also uses the skills when your request matches.
Update the plugin
To turn on automatic updates, run /plugin, open Marketplaces → stripo and choose Enable auto-update. To update manually, run:
claude plugin marketplace update stripo
claude plugin update stripo@stripo
Then run /reload-plugins or start a new session. /plugin install doesn't update a plugin that is already installed.
Set up the Codex app
These steps cover the Codex desktop app. The Codex app, Codex CLI and the Codex IDE extension share one configuration, so you set Stripo up once, in the app or in the CLI. You need your workspace's Client ID.
Step 1. Add the Stripo MCP server
The app's Connect to a custom MCP form has no field for an OAuth Client ID, so you add Stripo to the Codex configuration file instead.
In the Codex app, open Settings → Configuration.
Click Open config.toml in the top-right corner.
Add the Stripo server at the end of the file. If the file already contains a
[mcp_servers.stripo-mcp]section, replace that section instead of adding a second one:
[mcp_servers.stripo-mcp]
url = "https://mcp.stripo.email/mcp"
scopes = ["mcp:tools", "offline_access"]
[mcp_servers.stripo-mcp.oauth]
client_id = "YOUR_CLIENT_ID"
Save the file.
Step 2. Install the Stripo plugin
Open Settings → Plugins, click Add and select Add a marketplace.
In Source, enter
https://github.com/stripoinc/agent-plugin. Leave Git ref set tomainand Sparse paths empty.Click Add marketplace.
In Settings → Plugins, search for
stripoand click + next to Stripo.
The installed plugin appears on the Plugins tab. Codex uses Git to add the marketplace. If it shows a program not found error, install Git and restart Codex.
Step 3. Sign in to Stripo
In Settings → Plugins, select the MCPs tab. If Codex shows Restart, click it so that the app reads the new configuration.
Click Authenticate next to stripo-mcp.
Sign in to Stripo in the browser. When the Authorization complete page appears, close the tab and return to Codex.
Step 4. Verify the connection
Start a new chat and type /mcp in the composer: stripo-mcp should be listed as connected. Then run the verification prompts. You can call a Stripo skill as $stripo:<skill-name>, for example $stripo:email-from-reference.
Codex approval settings still apply: depending on your settings, Codex may ask for confirmation before using a tool that reads or changes data in Stripo. The skills also need network access to download and upload the email's files; approve the command when Codex asks, or turn on Allow network access in Settings → Configuration.
Update the plugin
Open Settings → Plugins, select the Marketplace tab and click Upgrade next to the Stripo marketplace. Then start a new chat.
Set up Codex CLI
These steps cover Codex in a terminal. If you already set up the Codex app, Stripo is available in the CLI too. Otherwise, you need your workspace's Client ID.
Step 1. Connect the Stripo MCP server
In your terminal, run (Codex 0.134.0 or later):
codex mcp add stripo-mcp --url https://mcp.stripo.email/mcp --oauth-client-id "YOUR_CLIENT_ID"
Codex starts the sign-in. Sign in to Stripo in the browser; when the Authorization complete page appears, close the tab and return to the terminal.
If the browser doesn't open, or you need to sign in again later, run:
codex mcp login stripo-mcp --scopes mcp:tools,offline_access
Step 2. Install the Stripo plugin
Add the marketplace and install the plugin:
codex plugin marketplace add stripoinc/agent-plugin
codex plugin add stripo@stripo
Codex uses Git to add the marketplace. If it shows a program not found error, install Git and try again.
Step 3. Verify the connection
Check that the server is connected:
codex mcp list
Then start a new session and run the verification prompts. You can call a Stripo skill as $stripo:<skill-name>, for example $stripo:email-from-reference.
Codex approval settings still apply: depending on your settings, Codex may ask for confirmation before using a tool that reads or changes data in Stripo, and before running a skill's command with network access.
Update the plugin
Codex refreshes configured marketplaces when it starts. To update manually, run codex plugin marketplace upgrade stripo, then start a new session.
Set up Cursor
These steps cover the Cursor editor. Cursor CLI reads the same mcp.json, so the Stripo connection works there too. You need your workspace's Client ID.
Step 1. Add the Stripo MCP server
In Cursor, open Customize from the sidebar and select MCPs.
Click New MCP Server and choose User to use Stripo in all projects. To use it in one project only, choose that workspace instead. Cursor opens
mcp.json.Add the Stripo server. If the file already contains other servers, add the
stripo-mcpentry inside the existingmcpServersobject:
{
"mcpServers": {
"stripo-mcp": {
"url": "https://mcp.stripo.email/mcp",
"auth": {
"CLIENT_ID": "YOUR_CLIENT_ID",
"scopes": ["mcp:tools", "offline_access"]
}
}
}
}Save the file.
Keep the scopes line: without it, Cursor requests permissions that Stripo doesn't grant, and sign-in fails with invalid_scope.
Step 2. Sign in to Stripo
In Customize → MCPs, stripo-mcp appears under Needs Attention. Click Authenticate.
Sign in to Stripo in the browser and return to Cursor.
When the sign-in succeeds, stripo-mcp moves to Connected and shows the number of enabled tools. Click stripo-mcp to sign out, reload the server or turn individual tools on or off.
In Cursor CLI, sign in with agent mcp login stripo-mcp. If the server isn't approved yet, run agent mcp enable stripo-mcp. In older installations, the command is cursor-agent.
Step 3. Install the Stripo plugin
In Customize, select Plugins, click + Add and choose From GitHub Repository.
In Import Marketplace, enter
https://github.com/stripoinc/agent-pluginin Repository, keep Scope set to User and click Import.Search for
stripoand click Add next to stripo in the Marketplace section.
Open the installed plugin to see its skills.
When a skill runs, Cursor may ask you to run a command outside its sandbox. Approve it: downloading and uploading the email's files needs network access.
Step 4. Verify the connection
Start a new Agent chat and run the verification prompts. The first time the agent runs a Stripo tool, Cursor asks you to approve the call.
In Cursor CLI, check the server and its tools:
agent mcp list
agent mcp list-tools stripo-mcp
Update the plugin
To get a new version, import the repository again as in step 3, then start a new Agent chat: a running chat keeps the plugin version it started with.
Connect another AI tool
Any AI tool that supports remote MCP servers with OAuth can connect, if it lets you enter your workspace's Client ID. Clients that register themselves automatically fail with a 403 error: Stripo doesn't support Dynamic Client Registration.
Setting | Value |
Server name |
|
Transport | Streamable HTTP |
Server URL |
|
Authentication | OAuth 2.0, Authorization Code with PKCE (S256) |
OAuth Client ID | Your workspace's Client ID |
Client secret | None |
Scopes |
|
Authorization URL |
|
Token URL |
|
Stripo accepts sign-in callbacks from Claude, Cursor, VS Code and local addresses (localhost, 127.0.0.1). If your tool uses another callback URL, sign-in fails with Invalid parameter: redirect_uri. Send the exact URL, your AI tool and your workspace's Client ID to support@stripo.email, and sign in after Stripo support confirms the change.
For example, in VS Code 1.123 or later with GitHub Copilot, add this to your mcp.json, then start the server and sign in:
{
"servers": {
"stripo-mcp": {
"type": "http",
"url": "https://mcp.stripo.email/mcp",
"oauth": { "clientId": "YOUR_CLIENT_ID" }
}
}
}To use the Stripo skills in another agent that supports SKILL.md skills, copy skills/, packages/ and scripts/ from the plugin repository into one folder, keeping them side by side: the skills find the SDK and the file-transfer helper next to their folder. Copying only skills/ leaves out the SDK the skills need.
Verify the connection
Start a new chat or session and ask:
Use the Stripo MCP tools to call whoami and list the Stripo projects I can access. Don't change anything.
If the agent returns your Stripo account and projects, the connection is ready. Check that it is the account you expect.
To check that the plugin skills are available, ask:
Which Stripo skills are installed?
The agent should list the Stripo skills, such as email-from-reference. A connection without the plugin has no skills.
Available tools
The tools are grouped by area below. Each tool name is the exact identifier an agent uses to call it.
Account and access
whoami— Get your Stripo profile, the workspaces you can access with your role, and their content counts.find_projects— Find the projects you can access, with their workspace, group and recent activity.list_members— List the members of a workspace with their roles and access.get_server_time— Get the server's current time, used for date filters.
Search and read
find_content— Search or count emails, templates and modules by name, content or metadata.find_folders— List and search folders with their item counts.find_activity— Find create, update, delete, move and restore events for emails, templates, modules and folders.get_content— Get the details of one email, template or module; its HTML comes as a temporary download link.get_screenshot— Get desktop and mobile PNG previews of an email or template, including unsaved changes.show_content_preview— Get the preview and editor links of an email or template. Supported AI tools display the preview in the chat.export_to_html— Export an email or template as ready-to-send HTML, optionally replacing merge tags. Each call uses one export from the workspace quota.
Create and organize
create_email— Create an email: blank, from a template or as a copy of an existing email.create_folder— Create a folder for emails or templates.delete_content— Delete emails, templates or modules. It shows what will be deleted first and requires confirmation; deleted items can be restored from the trash.
Email content
get_document_state_schema— Get the JSON Schema of the email model.get_document_state— Download the editable model of an email or template.prepare_document_state_upload— Get a temporary link for uploading an edited model.set_document_state— Save the uploaded model to the email or template.
Images
generate_image— Start generating an image for an email or template from a text prompt, optionally guided by reference images.edit_image— Start editing an existing image by instruction. The original stays unchanged; the result is a new image.get_image_job— Get the status and result of an image job.prepare_image_upload— Get a temporary link for uploading an image you supplied.upload_image— Host the uploaded image in the email's or template's image gallery.
Generated and edited images are saved in the email's or template's image gallery and marked as AI-generated. Each job spends the project's AI image quota.
Business Profile
get_business_profile— Get a project's Business Profile.patch_business_profile— Update selected fields of the Business Profile.prepare_business_profile_upload— Get an upload link for a full Business Profile file.replace_business_profile— Replace the whole Business Profile with the uploaded file.
Capabilities and limitations
Nothing is sent. The agent creates and edits content, but it doesn't send emails or schedule campaigns.
Quotas. HTML export uses the workspace's export quota; generating and editing images uses the project's AI image quota.
Access. The agent works only in the workspaces and projects available to the signed-in user, with that user's role.
Example prompts
With the connection and the plugin set up, describe the result you need rather than individual tool calls. Name the project and the email by name, link or ID: “my latest email” can point to an email the agent has just created.
Create an email from a brief
Use the email-from-reference skill.
Create a new email in the "Spring campaign" project: a 20% spring sale for returning customers, with a hero image, three product cards and a "Shop now" button linking to https://example.com/spring. Use the project's Business Profile for colors, fonts and tone of voice. Check the saved desktop and mobile previews before you finish.
Rebuild an email from a reference
Use the email-from-reference skill.
Recreate the attached screenshot as a native, editable Stripo email in the "Newsletters" project. Keep the layout and structure, use our logo and colors from the Business Profile, and host the attached product photos in the email's image gallery.
Edit an existing email
Use the email-model-editor skill.
In email ID 1234567, change the headline to "Last chance: 20% off", update the button link to https://example.com/sale and generate a new hero image in the same style. Keep the rest of the layout. Show me the planned changes before saving.
Audit a Business Profile
Use the business-profile skill.
Audit the Business Profile of the "Acme" project against emails 1111111, 2222222 and 3333333. Don't change it; list what is missing or inconsistent.
Troubleshooting
Sign-in fails or the wrong account appears
Message or symptom | What to do |
You don't see MCP integration in Stripo settings | Only Owners and Admins see it. Ask them to turn on the integration and share the Client ID. |
The toggle is disabled or a plan banner appears | The workspace needs Medium, Pro or Prime. |
“Client not found” | The Client ID is wrong, contains spaces or was regenerated. Copy the current ID and update your connection. |
| Use only |
403 error or “Dynamic Client Registration not supported” | Your AI tool tried to register itself automatically. Enter the Client ID as shown in your tool's guide. |
| Update your AI tool and follow its guide. For a tool not covered here, see Connect another AI tool. |
“Account is disabled, contact your administrator” | Confirm your Stripo email address using the confirmation email, or request a new one from your profile. If it is already confirmed, contact support. |
| Sign out of the Stripo connection in your AI tool and sign in with the intended account. Don't regenerate the Client ID to switch users. |
The Stripo plugin marketplace can't be added
Check that you entered the repository exactly as shown: https://github.com/stripoinc/agent-plugin in Claude chat, Cowork, Cursor and the Codex app, stripoinc/agent-plugin in Claude Code and Codex CLI. Then:
Update your AI tool to the latest version and try again.
Check that your network can access GitHub.
Check that your organization allows third-party plugin marketplaces.
The tools or skills aren't available
Start a new chat or session: tools and skills added during installation may not load in a session that was already open. In Claude Desktop and Codex, restart the app.
Also check that the Stripo connection shows as connected and enabled: Customize → Connectors in Claude, /mcp in Claude Code, the MCPs tab in Settings → Plugins in the Codex app, codex mcp list in Codex CLI, Customize → MCPs in Cursor. In a Claude chat, open + → Connectors and make sure Stripo is turned on.
The server shows “Needs authentication”
Sign in again: run claude mcp login stripo-mcp, codex mcp login stripo-mcp --scopes mcp:tools,offline_access or agent mcp login stripo-mcp. In Claude Code, you can also open /mcp and select Authenticate. In the Codex app, click Authenticate next to stripo-mcp on the MCPs tab in Settings → Plugins.
Sign-in in the Codex app fails with a registration error
The Codex app tried to register itself automatically because stripo-mcp has no Client ID. This happens when you add the server through the Connect to a custom MCP form. Add the [mcp_servers.stripo-mcp.oauth] section with your Client ID to config.toml, as shown in the Codex app guide, and click Authenticate again.
Codex reports an error in config.toml
A typo in config.toml can stop Codex from loading its settings; the Codex app shows the file and the line with the error. Check that [mcp_servers.stripo-mcp] appears only once, that the Client ID is in quotes, and that the lines match the example exactly.
The terminal keeps waiting after you sign in
The browser confirms the sign-in, but the session doesn't continue. Copy the full URL from the browser's address bar and paste it into the URL prompt in the terminal. If that doesn't help, update the CLI, sign out and sign in again.
On a remote machine or over SSH, run claude mcp login stripo-mcp --no-browser in an interactive terminal, open the printed URL on your local computer and paste the redirect URL back.
A skill can't download or upload a file
The connection can work while the skill's commands can't reach Stripo. In Claude chat and Cowork, check that network egress is on and that both Stripo domains are in Additional allowed domains, then start a new chat or Cowork session. In Codex, approve the command when Codex asks, or turn on Allow network access in Settings → Configuration in the Codex app. In Cursor, approve running the command outside the sandbox.
A skill can't find its SDK
The skills need the packages folder next to them. If you copied the skills into another agent, copy skills, packages and scripts together again, as described in Connect another AI tool. Check that Node.js 20.18.1 or later is installed.
The agent can read data but can't make a change
Check the role of the signed-in Stripo user in that project, and the permission your AI tool asked for. The agent can't do anything that is unavailable to that user.
Manage the connection
Claude chat and Cowork
Disconnect or remove the connection: open the Stripo connector in Customize → Connectors.
Remove the plugin: Customize → Plugins.
Claude Code
Show the configuration:
claude mcp get stripo-mcpSign in again:
claude mcp login stripo-mcpSign out:
claude mcp logout stripo-mcpRemove the server:
claude mcp remove stripo-mcp --scope userRemove the plugin:
claude plugin uninstall stripo@stripo
Codex CLI
Show the configuration:
codex mcp get stripo-mcpSign in again:
codex mcp login stripo-mcp --scopes mcp:tools,offline_accessSign out:
codex mcp logout stripo-mcpRemove the server:
codex mcp remove stripo-mcpRemove the plugin:
codex plugin remove stripo@stripo
Cursor
Show the configuration in Cursor CLI:
agent mcp listSign in again in Cursor CLI:
agent mcp login stripo-mcpTurn off without removing in Cursor CLI:
agent mcp disable stripo-mcpRemove the server: delete the
stripo-mcpentry frommcp.json.Remove the plugin: click Uninstall on the plugin's page in Cursor.
Regenerate the Client ID
If the Client ID was exposed, an Owner or Admin can click Generate a new Client ID in Workspace Configuration → MCP integration. This affects every AI connection in the workspace: new sign-ins with the old ID stop immediately, and existing connections lose access within minutes. Share the new ID with your team. Each person updates their connection:
AI tool | What to do |
Claude chat and Cowork | Remove the Stripo connector, add it again with the new ID and click Connect. On Team or Enterprise, the Owner re-adds it and each member connects again. |
Claude Code | Run |
Codex app | Replace |
Codex CLI | Run |
Cursor | Replace |
The plugin and copied skills stay installed.
Turn off the integration
To turn off access for the whole workspace, an Owner or Admin turns off Connect AI tools in Stripo. All connected AI tools lose access within a few minutes. Turning it back on lets you use the same Client ID again. A downgrade to a plan without MCP integration turns it off automatically.
Need help?
Email support@stripo.email with your AI tool and its version, your operating system, the step that failed and the exact error text. Remove tokens and unrelated configuration from anything you share.