Setting Up the Yespo Plugin for Claude Code and Claude Cowork

Read this article in Ukrainian ⮕

The Yespo plugin works with both Claude Code and Claude Cowork. It combines an eSputnik MCP connection with reusable skills for email template editing, email deliverability audits, and messaging analytics.

Once installed, you can describe an eSputnik task in plain language, let Claude retrieve the required data, and review any proposed changes without switching repeatedly between Claude and the eSputnik interface.

📘
About the Plugin Name
eSputnik and Yespo run on the same underlying platform, so a single plugin — published as Yespo — supports both. The plugin card, skill names, and folder names all say "Yespo," including when you're working with an eSputnik account. During setup, you connect the eSputnik connector specifically; the plugin name itself doesn't change what account it works with.

For the available skills, example tasks, and integration limitations, see Integrating eSputnik with AI Agents.

The same plugin also supports OpenAI Codex.

📘
Note
In this article, Claude refers to both Claude Code and Claude Cowork. The same Yespo plugin repository supports both environments, although some interface labels may differ.

The steps below show the installation flow in Claude Desktop. Cowork requires additional network settings, while the Code tab is used to install the plugin for Claude Code.

🚧
Research Preview
This integration is available as a research preview. Expect iteration and evolving capabilities.

Requirements

Before you start, make sure you have:

An active eSputnik account.
A Claude plan that supports Claude Code or Claude Cowork.
Claude Desktop for macOS or Windows if you use Claude Cowork.
Permission to install personal or organization plugins.

Configure Network Access for Claude Cowork

Before installing the plugin, allow Claude to connect to the required eSputnik services.

Open Claude Desktop.
Click your profile icon in the bottom-left corner, then go to Settings → Capabilities. Find Cloud code execution and file creation and allow network egress.

In Additional allowed domains, enter *.esputnik.com, then click Add.

📘
Connecting Both Accounts
If you also plan to connect a Yespo account with the same plugin, add *.yespo.io as well.

Installation

Step 1. Add the Yespo Plugin Marketplace

In Cowork, go to Customize → Plugins → Add → Add marketplace.

Select Add from a repository and enter the Yespo plugin repository URL:

https://github.com/Yespo-CDP/ai-plugin

Click Sync.

Claude adds the marketplace and displays the Yespo plugin.

Step 2. Install the Plugin and Connect Your eSputnik Account

Installing the plugin adds the Yespo skills, but Claude cannot access your eSputnik data until you connect the bundled eSputnik connector. After you sign in and authorize access, Claude can use the eSputnik MCP tools available to your account.

In the Code tab, find the Yespo plugin and click +.

Click the Yespo plugin card to open its Skills and Connectors settings.
Open the Connectors tab. It lists separate rows for Yespo and eSputnik.
Next to the platform you want to use, click Install (if shown), then click Connect:
- Yespo — to connect a Yespo account.
- eSputnik — to connect an eSputnik account.

After authorization, click Open desktop app to return to Claude Desktop. You can also close the browser tab and return manually.

📘
Note
Yespo and eSputnik are authorized separately. You can connect either one or both. If both are connected and the required account for a task is unclear, Claude may ask which platform to use.

Tool Permissions

After connecting, you'll see the available eSputnik MCP tools. By default, Claude may ask for confirmation before using a tool.

You can set frequently used read-only tools to Always allow. Keep confirmation enabled for tools that create or update messages, contacts, workflows, or other account data unless broader access is approved by your organization.

Verify the Connection

Start a new Claude chat and ask:

Are any MCP servers connected?

Claude should list the eSputnik MCP server.

Next, test access to your eSputnik account:

Use the eSputnik MCP tools to show me my last 5 email templates.

If Claude returns templates from your account, the connector is ready.

To check that the plugin skills are available, ask:

Which Yespo skills are installed?

Claude should list:

yespo-email-editor
email-deliverability
yespo-analytics

What to Do Next

Once the plugin is connected, describe the result you need rather than listing individual API calls.

Templates and content:

Translate email template ID 3935987 into German.
Clone template ID 3935987 and update the subject line for a spring sale campaign.
Duplicate template IDs 3935987, 3935988, and 3935989. Add the suffix "— Copy Q2" to each template name.
Replace all instances of the old unsubscribe link with the new one across all emails in workflow ID 434661.
Extract the subject, preheader, body copy, CTA, and footer from template ID 3935987.

Template QA:

Audit all emails in workflow ID 434661 for unsubscribe links. Flag any that are missing or broken.
Check the subject line, preheader, and hero image for templates in the "Spring Sale" series. Flag anything incomplete or inconsistent.
Template ID 3935987 has mobile rendering issues on iOS. Diagnose and fix the HTML/CSS.

Analytics and performance:

Show me the Open and Click metrics for all workflows last month.
Which workflows had the highest conversion rate in March?
Compare broadcast and triggered workflow performance for Q1.
How many PurchaseCompleted events were recorded last week, broken down by day?
What is the share of email conversions from total PurchaseCompleted events in March?
My open rate is high but CTR is low — what could explain this?
Run a deliverability and spam metric audit for campaign IDs 1234, 1235, and 1236.

Contacts and segments:

Create a static segment called "Abandoned Cart — April" and add the following contact IDs: 10023, 10045, 10089.
Show me the recent message history for contact ID 58821.
What communications did contact ID 58821 receive in the last 30 days and why?
Contact ID 58821 should be in segment ID 1234 but isn't. Why, and how do I fix it?

Workflows:

What is workflow ID 434661 about? Describe its structure and steps.
Review all emails in workflow ID 434661 and suggest improvements.
Are there any contacts entering two workflows at the same time?
Help me set up an A/B experiment in workflow ID 434661.

For more examples and skill descriptions, see Integrating eSputnik with AI Agents.

Troubleshooting

The Personal Tab Is Missing

Install an Anthropic plugin from Browse plugins, then reopen the plugin marketplace.

If your organization restricts personal plugins, contact your Claude administrator.

The eSputnik Connector Does Not Appear

Open the Yespo plugin card and check the Connectors tab for eSputnik.

If the connector is still unavailable:

Confirm that the Yespo plugin is installed.
Restart Claude Desktop.
Reopen the plugin settings.
Check whether your organization restricts third-party connectors.

Authorization Is Complete, but Claude Cannot Use eSputnik Tools

Restart Claude Desktop and start a new chat. Tools added during installation may not be available in an already open session.

Also confirm that:

The eSputnik connector shows as connected.
*.esputnik.com is included in the allowed domains.
Network egress is enabled.
You authorized the correct eSputnik account.

Claude Can Read Data but Cannot Make a Change

Check the permission requested by Claude and the access rights of the connected eSputnik user. The plugin cannot perform actions that are unavailable to that user.

I Connected Yespo Instead of eSputnik by Mistake

Yespo and eSputnik are separate connectors with independent authorization. Open Connectors in the plugin settings, connect eSputnik, and tell Claude which platform to use if you have both connected.