Skip to main content

Connect an AI assistant to EasyChannel with MCP

Give Claude, Cursor, or any MCP client direct access to your EasyChannel account. Three setup routes, what the assistant can reach, and where to take care.

Written by Karolina Santiago

The idea in one line

Instead of describing your catalog to an AI assistant, you let it look for itself.

MCP (Model Context Protocol) is an open standard for plugging assistants into real systems. Once EasyChannel is connected, questions like "which Walmart listings ran out of stock this week?" get answered from your actual data, and instructions like "tag those orders as priority" get carried out.

No code involved. Setup takes a couple of minutes.


Pick your setup route

If you use

Route

Token needed

claude.ai, Cowork, Claude Desktop

1

No, you sign in

Cursor, VS Code, most other clients

2

Yes

Claude Code in a terminal

3

Yes

Routes 2 and 3 need the token first, so grab it below. Route 1 users can skip straight past it.


Getting the token

Sign in at easychannel.com/login, open Settings > Integrations, and stay on All Integrations. Scroll down to the MCP EasyChannel tile, marked NEW, and click it.

The dialog hands you three things:

  • The raw token, with a Copy button

  • A Copy command button, giving you the Claude Code line from Route 3 with the token already in it

  • A Copy settings button, giving you the JSON from Route 2, likewise filled in

So in most cases you never touch the raw token at all. Copy whichever of the two ready-made blocks matches your tool.

Handle it like a password. This token reads and writes your EasyChannel data. Keep it out of repositories and shared channels. If it ever gets loose, generate a fresh one from the same dialog, which retires the old one on the spot.


Route 1: sign in (claude.ai, Cowork, Claude Desktop)

  1. In Claude, go to Settings (or Customize) > Connectors

  2. Press +, then Add custom connector

  3. Paste https://api.easychannel.com/mcp and confirm

  4. Sign in to EasyChannel when the login prompt appears, and approve access

  5. Inside any chat or Project, turn the connector on from + > Connectors

On Team and Enterprise workspaces the connector is added once by an owner under Organization settings > Connectors. Everyone else then switches it on for themselves under Settings > Connectors.

Worth knowing: this is also how you wire EasyChannel into a shared Claude Project, so a whole team can query the same store.


Route 2: config file (Cursor, VS Code, other clients)

Open your client's MCP settings and add:

{   "mcpServers": {     "easychannel": {       "type": "http",       "url": "https://api.easychannel.com/mcp",       "headers": {         "Authorization": "Bearer YOUR_TOKEN_HERE"       }     }   } }

Or skip the typing and use Copy settings in the MCP EasyChannel dialog. Save the file, restart the tool, and EasyChannel shows up in its list of servers.

Where the file lives:

  • Cursor, every project: ~/.cursor/mcp.json

  • Cursor, one project: .cursor/mcp.json at the project root. There is also Cursor Settings > Tools & MCP if you prefer a UI

  • Claude Desktop on macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

  • Claude Desktop on Windows: %APPDATA%\Claude\claude_desktop_config.json

Anything that speaks MCP over HTTP will take the same URL and header, VS Code through GitHub Copilot included. Only the location of the setting differs between tools. If yours is not listed, check its own MCP documentation for where the config lives.


Route 3: Claude Code

One line in the terminal:

claude mcp add --transport http easychannel https://api.easychannel.com/mcp --header "Authorization: Bearer YOUR_TOKEN_HERE"

The Copy command button in the MCP EasyChannel dialog gives you this with your token already inserted. Run it once and the tools load automatically in every session afterwards.

First time with Claude Code? docs.anthropic.com/en/docs/claude-code/mcp


First things to ask it

Once connected, put it to work straight away:

  • Which of my products have zero stock right now?

  • Show me Etsy orders from the past three days

  • Is SKU ABC-123 already in my catalog?

  • Which listings on seller 123 are still in Library rather than Active?

  • What are the shipping policies on my eBay account?

  • Did any CSV import fail this week, and which rows?

  • Tag everything in my Clearance segment as end-of-line

  • Set product 456 to quantity 20 and leave everything else alone

  • Publish products 101 and 102 to Walmart

If you would rather see the full menu, ask it what EasyChannel tools it has. It reads its own tool list and explains each one.


What it can reach

Area

What it reads

What it can change

Products

Filter by SKU or segment, variants included

Create, replace, patch single fields, tag

Listings

Filter by channel, account, SKU, status, segment, and trace back to the catalog product

Publish to a marketplace, tag

Orders

Filter by status, channel, SKU, marketplace order ID

Tag

Categories

List your categories

Create

Mapping templates

See how fields map onto each channel, and what a channel category accepts

Apply mappings in bulk, dry run first

SKU templates

List them

Create, delete

Seller accounts

List accounts, read payment, shipping, and return policies

Nothing

Segments

Read your saved filter sets

Nothing

CSV imports

Status and row-level errors, searchable by SKU or item ID

Nothing

Bulk actions

Track progress

Queue operations from the built-in catalog

Deleting is off the table entirely. The assistant cannot remove products, orders, or listings, whatever it is asked.


Working with more than one account

One connection covers your whole EasyChannel company, no matter how many marketplace accounts sit under it.

When a request only concerns one of them, name the seller ID. Ask the assistant to list your sellers and it will show each account with its ID, which you can then reuse. Leave the ID out and it works across the company.


Where to slow down

Most of what the assistant does stays inside EasyChannel and is easy to undo. Two things are not:

Publishing. This creates or revises live listings on the marketplace. Buyers see the result.

Bulk actions. These touch many records at once, and a vague instruction covers more ground than you meant.

Neither is riskier than the equivalent button in the app. Just give those instructions the same read-it-twice treatment. Asking the assistant to show you what it is about to touch, before it acts, costs nothing.


If it will not connect

Run down this list:

  1. Is the URL exactly https://api.easychannel.com/mcp, with no trailing slash and no typo?

  2. If you pasted a token, did the whole thing come across, with one space after Bearer and nothing clipped off either end?

  3. Has the token been regenerated since you copied it? The previous one stopped working the moment it was.

  4. Did you restart the tool, or toggle the connector off and back on, after saving?

Still nothing? Use the Need more MCP tools? button in the integration dialog, or your normal support channel.


Questions we get

Does the assistant see my whole account, or only what I ask about?

It can request anything in the table above, but it only receives what the specific tool it calls returns. It is not handed a copy of your database.

Can I let it read but not write?

Not through a setting. Reading and writing come with the same connection. If that matters, the practical control is how you phrase instructions, plus asking it to confirm before it acts on anything that reaches a marketplace.

Does this cost extra?

Access follows your EasyChannel plan, the same as the API.

Can two people connect at once?

Yes. Each person sets it up in their own AI tool. On claude.ai, a shared Project is the neater option since the connector is configured once.

What if I regenerate the token?

Every tool using the old one loses access straight away. Update them with the new token from the same dialog.

Do I need this if I already use the API?

No, they overlap. The API suits scheduled and production work, and it is the only one with webhooks. MCP suits the ad hoc questions that are not worth writing a script for. Plenty of people run both, on the same token.

Where is the full endpoint documentation?


Something missing?

The MCP server keeps growing, and requests from sellers decide what gets added. If there is a corner of EasyChannel you wish the assistant could reach, open Settings > Integrations > MCP EasyChannel and click Need more MCP tools?. It goes straight to the team.


Related

Did this answer your question?