Connecting
The MCP server runs at a single endpoint. Connect it once in your AI client, then talk to the assistant in natural language.
- Endpoint:
https://mcp.easy.tools - Transport: Streamable HTTP
- Authentication: sign in with your easytools account, or send an easycart API token
One connection covers both products. Whichever way you connect, the server obtains easymail access for you, so there is no second credential to create, paste, or rotate — see What your connection reaches.
Sign in with easytools
Clients that support OAuth for remote MCP servers connect by sending you to easycart to approve the connection. There is no token to copy or store.
Claude Desktop
- Open Settings → Connectors.
- Click Add at the top of the page, then Add custom connector.
- In Name, enter
Easytools— or any name you like. - In Remote MCP server URL, enter
https://mcp.easy.tools. - Click Add. Claude sends you to easycart to approve the connection. If you are already logged in, a confirmation screen appears — confirm it and you are returned to Claude. If you are not, log in first and the same confirmation screen follows.
The connector is ready as soon as you land back in Claude. Ask the assistant something about your store or your contacts to check it.
Other clients
Any MCP client that supports OAuth for remote servers uses the same flow: add
https://mcp.easy.tools as a remote MCP server and follow the approval screen
it opens. Claude Code supports it too — add the server without a header, then
run /mcp and pick Authenticate.
Managing the connection
Approved connections appear on the API keys list under API & Webhooks in easycart, at cart.easy.tools/creator/store-settings/developer. Disconnecting one there cuts off the client's access immediately; reconnect from the client to restore it.
Connect with an API token
Clients without OAuth support authenticate with an easycart API token sent in
the Authorization header. Generate one at
cart.easy.tools/creator/store-settings/developer
and store it securely — it is the same token used for the easycart REST API.
Claude Code
claude mcp add --transport http easytools https://mcp.easy.tools \
--header "Authorization: Bearer YOUR_EASYCART_TOKEN"
Other clients
| Setting | Value |
|---|---|
| URL | https://mcp.easy.tools |
| Transport | Streamable HTTP |
| Header | Authorization: Bearer YOUR_EASYCART_TOKEN |
A connection made this way reaches easymail as well. If you set yours up before the easymail tools existed, they are available now with no change to your configuration.
What your connection reaches
Your easycart authorization belongs to your user account, not to a single store. It reaches your own store, plus any store whose team granted you the Use the Easycart API permission — see Working across stores.
The same authorization also unlocks the easymail tools. The server obtains easymail access for the store it is acting on, which means your own account's email marketing and that of every store you can reach as a team member.
Reaching easymail for a store additionally requires the Manage Easymail API keys permission on that store. Without it, the easymail tools report that the store's owner has to grant it, and the easycart tools keep working as normal.
For more on tokens and access, see the easycart Authorization and easymail Authorization guides.
Working across stores
Ask the assistant which stores you can manage —
"Which stores can I manage?"
— and it will list them. By default it acts on your default store; name a specific store and it will switch to that one for the actions that follow, for both the easycart and the easymail tools.
This mirrors store selection in the REST API. For the underlying rules — how access is granted and what happens when it is revoked — see Store selection.
Rate limits
The assistant's requests count against each product's own API rate limit: 100 requests per 60 seconds — per store for easycart, per account for easymail. The assistant may make several requests to answer a single question. See the easycart Rate limiting and easymail Rate limiting guides for details.