# Vilkas MCP connector

Connect Vilkas to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot or any MCP client can look up carts, build orders, apply coupons and tidy categories, inside each person's own access, with every action logged.

Source: https://elaichi.ai/connectors/vilkas/

## Facts

| | |
| --- | --- |
| Application | Vilkas |
| Category | Ecommerce |
| AI tools | 94 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Vilkas is connected

- Show me open carts with more than three line items
- Add coupon SPRING10 to the cart for Anna Korhonen
- Move the Outdoor category above Footwear in the shop menu

## Connect Vilkas in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Vilkas.
2. Optionally set Share with, then press Connect.
3. Paste a Vilkas API key. One person generates a token in Vilkas and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Vilkas tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Vilkas MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Vilkas MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Vilkas MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Vilkas MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Vilkas MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Vilkas to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Vilkas tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Vilkas through Elaichi

### Turn a phone order into a Vilkas order

Sales. After a call, ask the agent to create a cart, add the line items and the customer's billing and shipping addresses, then turn the cart into an order.

### Fix a cart before it becomes an order

Support. Swap a wrong line item, correct a shipping address or change a quantity on a shopper's cart, then read the cart back to confirm it is right.

### Apply a campaign coupon to a cart

Marketing. Add a coupon to a cart during a promotion, or remove one that was applied by mistake, without opening the Vilkas admin.

### Reorder categories before a season launch

Merchandising. Rename categories, add a subcategory for a new range and change the order categories appear in the shop, all in one request.

### Update prices and shipping data in bulk

Operations. Correct line item prices, payment details or shipping data across many carts at once when a rate or carrier changes.

### See what is sitting in carts right now

Store management. Ask which carts are open, what is in each one, and which are ready to be turned into orders.

## Elaichi vs Zapier MCP vs Composio for Vilkas

All three can connect Vilkas to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Vilkas tools | Allow or restrict single Vilkas tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Vilkas call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Vilkas to Claude?

Connect Vilkas in Elaichi first: open the Vilkas connector, paste the API key from your Vilkas shop settings and save. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in to Elaichi when Claude asks and Vilkas is ready to use.

### Does Vilkas work with ChatGPT and Cursor as well as Claude?

Yes. Once Vilkas is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Vilkas once and every client picks it up.

### What can an AI agent actually do with my Vilkas shop?

With Vilkas connected, an agent can list your open carts, read the line items in one, add or change items, apply a coupon, set billing and shipping addresses and turn the cart into an order. It can also list your shop categories, rename one, add a subcategory or change the order they appear in. Short, specific asks such as "add coupon SPRING10 to cart 4120" work better than long paragraphs.

### Does connecting Vilkas give the AI my whole shop?

No. The Vilkas connection runs with the access of the Vilkas account whose API key was used, and each person signs in to Elaichi as themselves, so nothing runs outside what that access already allows. Elaichi can narrow that access further with roles and restrictions, but it can never widen what Vilkas itself permits.

### Can my team share one Vilkas connection?

Yes. One person connects Vilkas with the API key, shares the connection with a team in Elaichi, and nobody else ever sees or handles that key. Each teammate still signs in to Elaichi as themselves, so the audit log names who created an order or changed a category rather than a shared account.

### Can I stop an agent from deleting or changing things in Vilkas?

Yes. In Elaichi you restrict individual actions in Vilkas, such as deleting a category or removing a line item, for a role or for one person. A restricted action still shows up in Elaichi's tool search, flagged as restricted, but no client can run it in Vilkas whatever the prompt says.

### What happens to a Vilkas connection when someone leaves?

Offboard the person in Elaichi and their access to Vilkas through every client ends at once. A shared Vilkas connection keeps working for everyone else on the team. If you later want Vilkas gone entirely, disconnect it once in Elaichi and it disappears from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.

### Does the Vilkas MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Vilkas is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Vilkas?

Yes. Both let Claude, ChatGPT or Cursor use Vilkas. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Vilkas call.

### How is Elaichi different from Composio for Vilkas?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Vilkas: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 94 Vilkas tools

Every tool below is callable through https://api.elaichi.ai/mcp once Vilkas is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Vilkas cart billing addresses bulk update** (Update). Modifies the billing address for a cart. Required: cart_id.
- **Vilkas cart billing addresses bulk delete** (Delete). Deletes the billing address from a cart. Required: cart_id.
- **Create a Vilkas cart coupon** (Create). Applies a coupon code on a cart which results in creating a couponLineItem and a link to remove the coupon. Required: cart_id, code. Documented for ePages 6 shops only; may not be available on Vilkas Now.
- **Delete a Vilkas cart coupon by ID** (Delete). Deletes a coupon line item from a specific cart and recalculates cart. The link to add a coupon appears in the links section. Required: id, cart_id. Documented for ePages 6 shops only; may not be available on Vilkas Now.
- **Vilkas cart line item prices bulk update** (Update). Modifies the price of a specific product line item in a cart. Required: cart_id, line_item_id.
- **Create a Vilkas cart line item** (Create). Creates a product line item in a cart. Required: cart_id.
- **Update a Vilkas cart line item by ID** (Update). Modifies a specific product line item in a cart. Required: id, cart_id.
- **Delete a Vilkas cart line item by ID** (Delete). Deletes a specific product line item from a cart. Required: id, cart_id.
- **Vilkas cart line items bulk create** (Create). Creates multiple product line items in a cart. Required: cart_id.
- **Create a Vilkas cart order** (Create). Creates an order that is valid at the time of cart creation. It won't be validated again while processing the actual request. Billing address has to be available in the cart before creating an order. The request body for this REST call remains empty. Required: cart_id.
- **Vilkas cart payment data bulk update** (Update). Modifies the payment data for a cart.&lt;br&gt;&lt;br&gt;Please note that by providing the attribute name in the request body, the attributes paymentMethod and transactionId included in paymentData will be set to null. The provided name will not be included in the response. Required: cart_id.
- **Vilkas cart shipping addresses bulk update** (Update). Modifies the shipping address for a cart. Required: cart_id.
- **Vilkas cart shipping addresses bulk delete** (Delete). Deletes the shipping address from a cart. Required: cart_id.
- **Vilkas cart shipping data bulk update** (Update). Modifies the shipping data for a cart. Required: cart_id.
- **List all Vilkas carts** (List). Returns a list of carts. The connector pages through all results (up to 100 per page).
- **Create a Vilkas cart** (Create). Creates a cart for a shop.
- **Get single Vilkas cart by ID** (Get). Returns a specific cart from a shop identified by the provided cart Id. Required: id.
- **List all Vilkas categories** (List). Returns the product categories of the shop. This usually is the default root category "Categories", but can also include additional root categories, if supported by the shop.
- **Get single Vilkas category by ID** (Get). Returns the category identified by the provided category ID. Required: id.
- **Update a Vilkas category by ID** (Update). Modifies a category identified by the provided category ID. Required: id.
- **Delete a Vilkas category by ID** (Delete). Deletes a category identified by the provided category ID. Required: id. Documented for ePages 6 shops only; may not be available on Vilkas Now.
- **List all Vilkas category sequences** (List). Returns the order of subcategories for the provided category ID as an array. If the category has no subcategories, an empty array will be returned. Required: category_id.
- **Vilkas category sequences bulk update** (Update). Updates the order of subcategories for the provided category ID. Note that it is only possible to change the order but not to delete a subcategory. Required: category_id.
- **Create a Vilkas category subcategory** (Create). Creates a subcategory to an existing category. Providing attributes in the request is optional. Required: category_id.
- **List all Vilkas countries** (List). Returns all supported countries of the shop, i.e. all countries that can be selected as delivery countries for orders placed in the shop.
- **Vilkas coupon campaign coupons bulk update** (Update). Creates a coupon code in a coupon campaign. Required: coupon_campaign_id, code.
- **Create a Vilkas coupon campaign** (Create). Creates a coupon campaign for a shop. Coupon campaign types can be FIX (absolute value), PERCENT (percentage value), and SHIPPING (waive delivery costs). Required: locale.
- **Get single Vilkas coupon campaign by ID** (Get). Returns a specific coupon campaign from a shop identified by the provided coupon campaign Id. Required: id.
- **List all Vilkas currencies** (List). Returns the currency information of a shop.
- **List all Vilkas customers** (List). Returns a list of all customers. The connector pages through all results (up to 100 per page).
- **Create a Vilkas customer** (Create). Creates a customer. If *customerNumber* is not provided in the request, it will be generated automatically.
- **Get single Vilkas customer by ID** (Get). Returns a specified customer of a shop. Required: id.
- **Update a Vilkas customer by ID** (Update). Updates information for a single customer with partial data according to RFC 6902. You can either add or remove certain attributes. &lt;br&gt;&lt;br&gt; *Supported JSON-PATCH operations*&lt;br&gt; - add (sets or replaces an attribute)&lt;br&gt; - remove (unsets an attribute)&lt;br&gt;&lt;br&gt; *Attribute paths that allow updates via PATCH* ( ¹ supports *add* only)&lt;br&gt; - /customerNumber¹&lt;br&gt; - /billingAddress&lt;br&gt; - /internalNote&lt;br&gt;. Required: id. Send a JSON Patch array (RFC 6902) as the body.
- **List all Vilkas legal** (List). Returns hyperlinks of legal information for a shop.
- **List all Vilkas legal contact information** (List). Returns the contact information of a shop.
- **Vilkas legal contact information bulk update** (Update). Modifies the contact information of a shop. This endpoint expects a complete object representation, all fields included. If any field is not set, it will be deleted from the transferred object. Required: locale.
- **List all Vilkas legal cookie policy** (List). Returns the cookie policy of a shop.
- **Vilkas legal cookie policy bulk update** (Update). Modifies the cookie policy of a shop. This endpoint expects a complete object representation, all fields included. If any field is not set, it will be deleted from the transferred object. Required: locale.
- **List all Vilkas legal privacy policy** (List). Returns the privacy policy of a shop.
- **Vilkas legal privacy policy bulk update** (Update). Modifies the privacy policy of a shop. This endpoint expects a complete object representation, all fields included. If any field is not set, it will be deleted from the transferred object. Required: locale.
- **List all Vilkas legal rights of withdrawal** (List). Returns the customer rights of withdrawal of a shop.
- **Vilkas legal rights of withdrawal bulk update** (Update). Modifies the customer rights of withdrawal of a shop. This endpoint expects a complete object representation, all fields included. If any field is not set, it will be deleted from the transferred object. Required: locale.
- **List all Vilkas legal shipping information** (List). Returns detailed information on possible shipping types and the costs incurred. Also displays the costs for shipment abroad.
- **Vilkas legal shipping information bulk update** (Update). Modifies the shipping information of a shop. This endpoint expects a complete object representation, all fields included. If any field is not set, it will be deleted from the transferred object. Required: locale.
- **List all Vilkas legal terms and conditions** (List). Returns the terms and conditions of a shop.
- **Vilkas legal terms and conditions bulk update** (Update). Modifies the terms and conditions of a shop. This endpoint expects a complete object representation, all fields included. If any field is not set, it will be deleted from the transferred object. Required: locale.
- **List all Vilkas locales** (List). Returns the shop's locale information, i.e. the language identifier and the region identifier.
- **List all Vilkas newsletter campaign subscribers** (List). Returns all subscribers of a newsletter campaign from a shop. Required: campaign_id. Documented for ePages 6 shops only; may not be available on Vilkas Now. The connector pages through all results (up to 100 per page).
- **List all Vilkas newsletter campaigns** (List). Returns all newsletter campaigns of a shop. Documented for ePages 6 shops only; may not be available on Vilkas Now. The connector pages through all results (up to 100 per page).
- **List all Vilkas order documents** (List). Returns finalized invoice and credit note order documents by orderId. Required: order_id. The connector pages through all results (up to 100 per page).
- ...and 44 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
