Skip to main content

How to connect AI tools to Stripo via MCP integration?

In this article, you will learn how to enable MCP integration in your Stripo workspace and connect Claude, Claude Code, Cursor, VS Code, or Codex to work directly with your email templates.

Written by Dmitry Kulaksyz

MCP (Model Context Protocol) is an open standard that lets AI tools — such as Claude, Claude Code, VS Code, Cursor, and OpenAI Codex — work directly with your Stripo workspace. Once connected, your AI assistant can find and read emails, templates, and modules, create and edit emails, export HTML and screenshots, and delete content. It always acts with your own Stripo permissions in the workspaces you belong to.

Requirements:

  • Stripo Plan: Medium, Pro, or Prime.

  • To enable the integration: Owner or Admin role in the workspace.

  • To connect an AI tool: any workspace member with the Client ID. Ask your Owner or Admin to share it.

  • A Stripo account you can sign in to with email and password, Google, or your company SSO.

1. Enable MCP integration in Workspace Settings:

(Owner or Admin)

  • Go to Workspace Settings (click your organization name in the top-right corner → Settings).

  • Scroll to the MCP integration section.

  • Turn on Connect AI tools.

  • Click the Copy icon next to the Client ID field. You will need this value in Step 2.

Note: If the toggle is disabled and you see the banner “Available on Medium, Pro and Prime”, your plan doesn’t include MCP integration. Upgrade your plan to unlock it.

Your Client ID is not a password, but treat it with care: keep it private, avoid sharing it with third parties, and never publish it in public repositories.

2. Connect your AI tool:

You need two values:

  • Client ID — copied from Workspace Settings in Step 1.

  • MCP Server URL — https://mcp.stripo.email/mcp (the same for everyone).

Find your AI tool below and replace YOUR_CLIENT_ID with your Client ID. Each section ends with how to sign in and how to check that the connection works.

When your AI tool opens the Stripo sign-in page, sign in with your Stripo email and password, with Sign in with Google, or with your company SSO. Your email address must be confirmed.


Claude (web, desktop, and mobile)

Claude connects through a custom connector — no config file, no Node.js needed. Add it once on claude.ai or in Claude Desktop, and it becomes available in claude.ai, Claude Desktop, Cowork, and the Claude mobile apps.

Free, Pro, and Max plans:

  1. In Claude, go to Customize → Connectors, click + and choose Add custom connector.

  2. Name: Stripo

  3. MCP server URL: https://mcp.stripo.email/mcp

  4. Enter your Client ID. The dialog looks different depending on your Claude version:

    • if you see Advanced settings, expand it and paste the Client ID into OAuth Client ID;

    • if the dialog asks how Claude should sign in, choose Sign in now. Under OAuth client, choose Use your own OAuth client and paste the Client ID.

    Leave OAuth Client Secret empty.

  5. Click Add, then Connect. A Stripo sign-in window opens — sign in.

Team and Enterprise plans:

  1. A Claude Owner goes to Organization settings → Connectors, clicks Add, then Custom (if Claude asks for the connector type, choose Web), and adds the connector with the same name, URL and Client ID as above. The secret stays empty.

  2. Each member goes to Customize → Connectors, finds Stripo, and clicks Connect to sign in with their own Stripo account.

Check the connection: Stripo shows as connected in Customize → Connectors. In a chat, click + → Connectors (or type /) and make sure Stripo is turned on.

Notes

  • The Free plan allows one custom connector at a time.

  • Adding connectors from the mobile apps is still in beta. Add the connector on the web or in Claude Desktop; the mobile apps then use it without signing in again.

  • You can rename a connector or change its URL, but you can’t change its Client ID. To change the Client ID, remove the connector and add it again.


Claude Code

Run this command in your terminal. It works in macOS/Linux shells, PowerShell, and Command Prompt:

claude mcp add --transport http --scope user --client-id YOUR_CLIENT_ID stripo-mcp https://mcp.stripo.email/mcp

--scope user makes Stripo available in every folder where you use Claude Code. Without it, Stripo is added only for the current folder.

Sign in

  1. Start Claude Code. If a session was already open, restart it.

  2. Run /mcp, select stripo-mcp, and choose Authenticate.

  3. A browser window opens — sign in to Stripo.

On a remote or SSH machine, run claude mcp login stripo-mcp --no-browser instead and follow the prompts.

Check the connection: claude mcp list shows stripo-mcp as ✔ Connected, and the Stripo tools appear in /mcp.

If sign-in fails, update Claude Code with claude update and try again. To sign out, run claude mcp logout stripo-mcp, or choose Clear authentication for stripo-mcp in /mcp.

Claude Code is available on the Pro, Max, Team, and Enterprise subscription plans, and through an Anthropic Console account billed per token (pay-as-you-go). The Free plan does not include Claude Code. Connecting Stripo works with either sign-in method, because Stripo authenticates through its own sign-in, not through your Claude Code plan.

If you have an ANTHROPIC_API_KEY set in your environment, Claude Code uses that key and bills your API account per token instead of your subscription. This does not affect Stripo access.


VS Code (GitHub Copilot)

Before you start

  • You need VS Code 1.123 or later and a signed-in GitHub Copilot account.

  • On Copilot Business or Enterprise, your GitHub admin must enable the MCP servers in Copilot policy.

Steps

  1. Open the Command Palette (Ctrl+Shift+P / Cmd+Shift+P) and run MCP: Open User Configuration.

    To use Stripo in a single project only, create .vscode/mcp.json in that project instead. Don’t commit it to a public repository.

  2. Add the stripo-mcp entry inside "servers". Keep any servers that are already listed:

   {      "servers": {        "stripo-mcp": {          "type": "http",          "url": "https://mcp.stripo.email/mcp",          "oauth": { "clientId": "YOUR_CLIENT_ID" }        }      }    }
  1. Save the file and click Start above the stripo-mcp entry. You can also run MCP: List Servers → stripo-mcp → Start Server. Confirm that you trust the server.

  2. When VS Code says that the MCP server definition stripo-mcp wants to authenticate, click Allow. Sign in to Stripo in the browser window.

Check the connection: open Chat, pick Agent in the agent picker, and click Configure Tools in the chat input — the Stripo tools are listed. (If your chat runs on the Copilot harness, the tools are listed under Agent Customizations → Tools instead.)

Note: Ignore the Set Client Secret action above the entry. Stripo uses a public OAuth client, so no secret is needed.


Cursor

Start by opening the MCP settings in Cursor. Open Cursor, click Customize in the left sidebar, select the MCPs tab, and under Connect External Tools with MCP click + New. Cursor opens a configuration file named mcp.json, where MCP servers are defined.

Next, add the Stripo configuration. Paste the following into mcp.json. If the file already contains other MCP servers, add only the stripo-mcp block inside the existing mcpServers object.

{   "mcpServers": {     "stripo-mcp": {       "url": "https://mcp.stripo.email/mcp",       "auth": { "CLIENT_ID": "YOUR_CLIENT_ID" }     }   } }

Replace YOUR_CLIENT_ID with your own Client ID from your Stripo account, keeping the quotation marks around it. This value identifies your account, so the server must have it before you authenticate.

Save the file (Ctrl+S on Windows, Cmd+S on macOS). Stripo MCP now appears in the MCP list under Needs Attention with the status Needs authentication.

Now authenticate with Stripo. Next to stripo-mcp, click Authenticate. A browser tab opens on the Stripo sign-in page. Sign in with Google, or with your Stripo email and password, and if prompted, review the access request and click Continue. When you see Authorization complete, click Return to Cursor and close the browser tab.

Finally, confirm the connection. Back in Cursor, stripo-mcp moves to the Connected section with a green indicator and shows the number of tools and resources now enabled. The connection is ready to use.


OpenAI Codex

You need Codex 0.134.0 or later (check with codex --version). The Codex CLI, the IDE extension, and Codex in the ChatGPT desktop app share one configuration, so you only set it up once.

Option A — command line

Run this as a single line:

codex mcp add stripo-mcp --url https://mcp.stripo.email/mcp --oauth-client-id YOUR_CLIENT_ID

Codex detects that Stripo uses OAuth and opens a browser window right away — sign in to Stripo.

If the browser didn’t open, you closed it before finishing, or Codex printed that the server “may or may not require login”, run:

codex mcp login stripo-mcp --scopes mcp:tools,offline_access

Check the connection: codex mcp list shows stripo-mcp with OAuth in the Auth column, and /mcp inside Codex lists the Stripo tools.

Important note:

If Codex reports an unknown option --oauth-client-id, update Codex to 0.134.0 or later and run the command again.

On Windows, if PowerShell shows "running scripts is disabled on this system", see Troubleshooting → OpenAI Codex.


3. Staying signed in:

Your AI tool refreshes access automatically, so you normally don’t need to sign in again. You will be asked to sign in again if:

  • you haven’t used the connection for a long time;

  • an Owner or Admin regenerates the Client ID or turns off Connect AI tools;

  • the workspace plan is downgraded;

  • you sign out of Stripo in your AI tool.

4. Regenerate your Client ID or turn off the integration:

Regenerate the Client ID

Regenerate the Client ID only if it has leaked. Regenerating disconnects every AI tool in the workspace.

  1. Go to Workspace Settings → MCP integration.

  2. Click the regenerate icon next to the Client ID field.

  3. Confirm in the dialog. The old Client ID stops accepting new sign-ins right away. AI tools that are already connected lose access within a few minutes.

  4. Share the new Client ID with your team, and update each AI tool:

AI tool

What to do after regenerating

Claude (custom connector)

Remove the Stripo connector, add it again with the new Client ID, and click Connect. On Team and Enterprise plans, the Owner re-adds it and members click Connect again.

Claude Desktop (manual setup)

Replace YOUR_CLIENT_ID and quit Claude Desktop. Delete the saved sign-in (macOS/Linux: rm -rf ~/.mcp-auth; Windows PowerShell: Remove-Item -Recurse -Force "$env:USERPROFILE.mcp-auth"), then start Claude Desktop again.

Claude Code

Run claude mcp remove stripo-mcp --scope user, run the claude mcp add command again with the new Client ID, then authenticate in /mcp.

VS Code

Replace clientId in mcp.json and run Developer: Reload Window. If you still see “Client not found”, run Authentication: Remove Dynamic Authentication Providers, remove the sso.stripo.email entry, and start the server again.

Cursor

Replace CLIENT_ID in mcp.json, then click Authenticate next to stripo-mcp.

OpenAI Codex

Replace client_id in config.toml, or run codex mcp add again with the new ID. Then run codex mcp logout stripo-mcp and codex mcp login stripo-mcp

Turn off the integration

When you turn off Connect AI tools, every connected AI tool loses access within a few minutes. When you turn it back on, the same Client ID works again.

If the workspace plan is downgraded to a plan without MCP integration, the integration is turned off automatically. After upgrading, turn it on again.

Troubleshooting

Access and plan

  • The MCP integration section is not visible. Only Owners and Admins can see it. Ask your workspace Owner for the Client ID, or for the required role.

  • The toggle is disabled, or you see a paywall banner. Upgrade the workspace to Medium, Pro, or Prime.

Errors on the sign-in page

  • “Client not found.” The Client ID is wrong, contains extra spaces, or was regenerated. Copy the current Client ID from Workspace Settings and update your AI tool (see Step 4).

  • “Invalid parameter: redirect_uri”. Your AI tool, or its version, isn’t supported yet. Update the tool. If the error persists, contact support.

  • An error mentioning invalid_scope or “Invalid scopes”. Your configuration requests permissions that Stripo doesn’t allow. Use exactly mcp:tools and offline_access, as shown in the snippets above. Your AI tool shows this error, not the Stripo sign-in page.

  • An error about client registration, or a prompt to enter a client ID. The Client ID is missing from your configuration, or your tool ignored it. Add it as shown above. In VS Code, paste the Client ID into the prompt, or update to version 1.123 or later and add oauth.clientId to mcp.json.

  • “Account is disabled, contact your administrator.” Your email address isn’t confirmed yet. Open the confirmation email from Stripo, or request a new one in your Stripo profile.

  • You can’t sign in. Use your Stripo email and password, Sign in with Google, or your company SSO. Sign in with Google works with any Stripo account that uses the same email address. If you registered with Facebook, Microsoft, or Apple and don’t use Google, set a password in your Stripo profile first.

Claude

  • The connector fails right after Add, without opening the Stripo sign-in. Claude tried to register its own OAuth client or use its published identity. Remove the connector and add it again: choose Use your own OAuth client and paste your Client ID.

  • The connector can’t connect after you regenerated the Client ID. Claude doesn’t allow editing the Client ID. Remove the connector and add it again.

  • The connection error shows a reference ID that starts with ofid_. Include it when you contact support.

Claude Desktop manual setup

  • 'C:\Program' is not recognized as an internal or external command (Windows). The "command" is npx instead of npx.cmd. Change it to npx.cmd, save, and fully quit and reopen Claude Desktop.

  • “npx not found” or “spawn npx ENOENT”. Install Node.js 18 or newer, then fully quit and reopen Claude Desktop.

    • If npx works in your terminal but not in Claude Desktop (common with nvm, Homebrew, or Volta), put the full path to npx in "command". Get it with which npx on macOS or where npx.cmd on Windows.

  • “Callback port 3334 is already in use”. Replace 3334 with another free port, such as 3335, and restart Claude Desktop.

  • You are asked to sign in over and over. Quit Claude Desktop, delete the saved sign-in (see the Step 4 table), and start it again.

  • You edited the file, but stripo-mcp doesn’t appear in Connectors. Check that "mcpServers" is a top-level key, next to "preferences", not inside it, and that there is a comma between it and the previous setting (and no comma after the last one). Also make sure you edited the file that Settings → Developer → Edit Config opens, not a copy in another folder.

  • Where to find logs:

    • macOS: ~/Library/Logs/Claude/mcp-server-stripo-mcp.log (and mcp.log)

    • Windows: the logs folder next to claude_desktop_config.json (open it with Edit Config)

VS Code

  • A dialog says “Dynamic Client Registration not supported”. VS Code didn’t find oauth.clientId in mcp.json (missing, misspelled, or VS Code older than 1.123). Click Copy URIs & Proceed and paste your Client ID into the prompt, or fix mcp.json and start the server again.

Cursor

  • The browser sign-in doesn’t return to Cursor. Another app is using port 8787. Close it and click Authenticate again.

OpenAI Codex

  • "npm.ps1 cannot be loaded because running scripts is disabled on this system" (Windows). PowerShell blocks scripts by default, so it can't run npm or codex commands. The error may also mention codex.ps1 instead of npm.ps1. To allow scripts for your Windows account, open PowerShell and run:

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser

Type Y to confirm, then run the codex mcp add command again. You don't need administrator rights for this. Learn more about execution policies in Microsoft's guide.


Rule in one line: in a form field or on the command line the Client ID is pasted without quotes; inside a config file (JSON, TOML) it is a string value, so it goes in double quotes. The only escaping exception is the manual Claude Desktop setup (mcp-remote).

Tool / place

How the Client ID looks when pasted

Quotes

Claude web/desktop, OAuth Client ID field

mcp_org_363699_01M0ZF...

no, raw

Claude web/desktop, URL field

https://mcp.stripo.email/mcp

no, raw

Claude Code, --client-id flag

--client-id mcp_org_363699_01M0ZF...

no (argument)

VS Code, mcp.json → "clientId"

"clientId": "mcp_org_363699_01M0ZF..."

yes, JSON

Cursor, mcp.json → "CLIENT_ID"

"CLIENT_ID": "mcp_org_363699_01M0ZF..."

yes, JSON

Codex, config.toml → client_id

client_id = "mcp_org_363699_01M0ZF..."

yes, TOML

Claude Desktop manual (mcp-remote)

"{\"client_id\":\"mcp_org_363699_...\"}"

yes + \ escaped


Thank you for taking the time to read our articles. We hope you will find this information helpful.


​If you have any additional questions, please email us at support@stripo.email.

We would be glad to talk with you.


Did this answer your question?