eekaam.docs

Eekaam MCP

Eekaam MCP

Reference theme

Eekaam MCP is the official Model Context Protocol server for Eekaam stores. It lets a compatible AI assistant inspect and operate a merchant's store without sharing dashboard credentials.

What the connection can do

The server exposes tools for store setup, products, variants, collections, media, themes, orders, customers, discounts, content, SEO, metafields, tracking and analytics. Tool discovery is permission-aware: an assistant only sees tools covered by the scopes the merchant granted.

Start most sessions with get_store_snapshot. Use search_store when the merchant names a product, order, customer, page or post without providing an ID.

Server address

Use the canonical MCP endpoint:

https://api.eekaam.com/mcp

Authentication uses OAuth 2.0 with protected-resource metadata and dynamic client registration. A compatible client should open Eekaam's approval screen automatically; merchants select a store and approve permissions there.

Safety model

  • The access token is bound to one installation and one store.
  • Every repository query is tenant-scoped; store IDs are never accepted as tool arguments.
  • Discovery hides tools outside the granted scopes.
  • Read-only, destructive, idempotent and open-world hints are published through MCP annotations.
  • Consequential operations use a preview followed by a five-minute, single-use confirmation token bound to the exact action.
  • Calls are assigned request IDs and written to the store activity log.

Updated 26 October 2026