Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.launchmystore.io/llms.txt

Use this file to discover all available pages before exploring further.

​
Model Context Protocol (MCP) Integration

LaunchMyStore ships a built-in MCP server so AI assistants — Claude Desktop, Claude Code, Cursor, and any other MCP-compatible client — can drive your store through natural language.
Nova AI & MCP share the same tools. Both interfaces use the same tool definitions, so any capability available in Nova AI is also available through MCP. This document covers MCP setup — for tool details, see Nova AI Tools.

​
What is MCP?

The Model Context Protocol is an open standard that lets AI assistants call external tools and read external resources. With MCP wired up to your store, you can:
  • Ask the AI to update product prices or inventory
  • Create and manage discount codes through conversation
  • Pull sales analytics and dashboards
  • Manage orders and fulfillments
  • Update store settings, content, and themes

​
Quick Start

​
1. Generate an MCP token

  1. Open your LaunchMyStore admin.
  2. Navigate to Settings → AI Connector (MCP).
  3. Click Generate token.
  4. Copy the token shown — it’s a long opaque string valid for 1 year.
Treat the MCP token like a password. Anyone with it can call the MCP server as you. Never paste it into a public repo, screenshot, or chat.
To revoke a token, change your account password — every MCP token issued before the password change stops working immediately. We don’t yet expose per-token revocation; this is on the roadmap.

​
2. Add the server to your MCP client

Every supported client uses the same SSE transport configuration: 
{
  "mcpServers": {
    "launchmystore": {
      "type": "sse",
      "url": "https://api.launchmystore.io/mcp/sse",
      "headers": {
        "Authorization": "Bearer YOUR_MCP_TOKEN"
      }
    }
  }
}
The admin page also generates this snippet pre-baked with your token — click the Copy button on each client tab.

​
Claude Desktop

Edit claude_desktop_config.json:
  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
Paste the snippet, save, and restart Claude Desktop.

​
Claude Code

Create a .mcp.json at the root of your project (or add to ~/.claude.json for user scope), paste the snippet, and run /mcp inside Claude Code to confirm the connection.

​
Cursor

Open Cursor settings (Cmd+, / Ctrl+,), search for MCP, and paste the snippet into your MCP servers config.

​
3. Try a few commands

  • “Show me my top selling products this month”
  • “Create a 20% discount code for new customers”
  • “Update the price of ‘Classic T-Shirt’ to $29.99”
  • “What orders need fulfillment today?”

​
Available Tools

The MCP server exposes the same tools as Nova AI, organized by category:

Products

List, create, update, and delete products and variants

Orders

View orders, create manual orders, update status, refunds

Categories

Organize products with categories

Customers

View and manage customer data

Analytics

Sales reports, traffic data, product analytics

Coupons

Create and manage discount codes

Blogs & Pages

Content management for blogs and custom pages

Themes

Theme settings, sections, and blocks

Menus

Navigation menu management

Store Settings

Shipping, checkout, and store configuration
For a complete list of tools with parameters, see the Tools Reference.

​
Endpoints

MethodPathPurpose
GET/mcp/infoPublic discovery. Returns server info, capabilities, and the endpoint map.
POST/mcp/tokenMints a 1-year MCP token for the authenticated merchant.
GET/mcp/configReturns a paste-ready config snippet (?client=claude|claudeCode|cursor). If no token query is supplied, mints a fresh one.
GET/mcp/sseOpens the MCP SSE transport. First event delivered is endpoint, whose data is the messages URL the client must POST to.
POST/mcp/sse/message?sessionId=…Send a JSON-RPC request bound to an open SSE session. Returns 202 Accepted; the response is pushed back through the SSE stream as an event: message.
POST/mcpPlain JSON-RPC over HTTP without a long-lived SSE channel. Useful for debugging or for clients that don’t speak SSE. Supports batch requests.
GET/mcp/toolsLists every tool the AI can call.
GET/mcp/resourcesLists read-only resources.
GET/mcp/docsReturns the full tool catalogue as markdown.

​
Verifying the server

curl https://api.launchmystore.io/mcp/info
Response: 
{
  "name": "launchmystore-mcp",
  "version": "1.0.0",
  "protocolVersion": "2024-11-05",
  "serverUrl": "https://api.launchmystore.io",
  "capabilities": {
    "tools": { "listChanged": false },
    "resources": { "subscribe": false, "listChanged": false },
    "prompts": { "listChanged": false },
    "logging": {}
  },
  "endpoints": {
    "jsonrpc": "/mcp",
    "sse": "/mcp/sse",
    "token": "/mcp/token",
    "config": "/mcp/config"
  },
  "documentation": "https://docs.launchmystore.io/mcp/overview"
}

​
Transport details

The SSE transport follows the MCP 2024-11-05 spec:
  1. The client opens GET /mcp/sse with Authorization: Bearer ….
  2. The server immediately emits event: endpoint\ndata: /mcp/sse/message?sessionId=<id>\n\n.
  3. The client POSTs every JSON-RPC request to that messages URL with the same Bearer header. Each POST returns 202 Accepted with no body.
  4. The server pushes the matching JSON-RPC response back over the original SSE stream as event: message\ndata: <json>\n\n.
  5. Heartbeats (: heartbeat <ts>) keep proxies from idling the connection out.
If you need plain request/response without a long-lived stream, use POST /mcp — it accepts a single JSON-RPC envelope or a batch array. 
curl -X POST https://api.launchmystore.io/mcp \
  -H "Authorization: Bearer YOUR_MCP_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": "1",
    "method": "tools/list",
    "params": {}
  }'

​
Security

  • Tokens are scoped to a single merchant account and inherit that account’s role and permissions.
  • Tool calls respect the same authorization model as the underlying REST APIs — if a role cannot delete products in the admin, the AI cannot delete them either.
  • Changing the account password invalidates every issued MCP token in one step.
  • All MCP tool calls land in your audit log with source: "mcp".

​
Troubleshooting

​
Client shows “Connecting…” forever

Make sure your snippet includes "type": "sse" and points to /mcp/sse (not /mcp). The plain /mcp endpoint is a JSON-RPC endpoint, not an SSE one — clients that try to open an event stream against it will hang.

​
”Unauthorized” / 401

Your token is invalid or expired. Generate a new one from Settings → AI Connector (MCP).

​
Tools don’t appear

  1. Confirm the connection is open in your client (Claude Code: /mcp).
  2. Try curl https://api.launchmystore.io/mcp/info to verify the server is reachable.
  3. Make sure your role has access to the tools you expect.

​
Permission denied on a specific tool

The role tied to your MCP token doesn’t have permission for that operation. Use an admin account or grant the relevant permission.