Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.mareaalcalina.com/llms.txt

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

​
Install Marea in your AI client in 60 seconds

The Marea MCP server runs at https://mcp.mareaalcalina.com/mcp and exposes the catalog API as 7 marea.* tools that AI clients can call directly. Install once with your developer key and the user’s AI client will route catalog calls through MCP instead of REST — gaining MCP elicitation prompts (explicit user confirmation on publish, ToS, and plan upgrades) for free.

​
Step 1 — Generate a developer key

Sign in at mareaalcalina.com/developers/keys and create an mk_dev_* key with at least the developer:bootstrap scope. Keep the key secret. The MCP client passes it to the Marea server on every call.

​
Step 2 — Add Marea to your client

Marea speaks streamable HTTP MCP at https://mcp.mareaalcalina.com/mcp. Most clients today still expect a stdio MCP server, so the install bridges the remote HTTP endpoint via mcp-remote — a small published npm shim that pipes stdio ↔ remote HTTP.
Open ~/Library/Application Support/Claude/claude_desktop_config.json on macOS (or %APPDATA%\Claude\claude_desktop_config.json on Windows) and add the marea entry:
{
  "mcpServers": {
    "marea": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.mareaalcalina.com/mcp",
        "--header",
        "Authorization: Bearer mk_dev_xxxxxxxxxxxxxxxx"
      ]
    }
  }
}
Restart Claude Desktop. The marea.* tools appear in the tool picker.
Need to share access without sharing the key? Pass Authorization: Bearer <user's mk_user_*> instead of mk_dev_* to limit the install to a single user’s storefronts — marea.bootstrap_user is rejected but every other tool works.

​
Step 3 — Confirm the install

Ask your AI client: “List the Marea tools you have.” You should see exactly seven:
ToolCallsScope required
marea.bootstrap_userPOST /v1/usersdeveloper:bootstrap (dev key)
marea.whoamiGET /v1/meany
marea.create_storefrontPOST /v1/storefrontscatalog:write (user key)
marea.update_storefrontPATCH /v1/storefronts/:storefrontIdcatalog:write
marea.create_productPOST /v1/storefronts/:storefrontId/productscatalog:write
marea.update_productPATCH /v1/storefronts/:storefrontId/products/:productIdcatalog:write
marea.publish_storefrontPOST /v1/storefronts/:storefrontId/publishstorefront:publish — fires an MCP elicitation prompt before sending the request
Verification is REST-only. POST /v1/users/:userId/verify and POST /v1/users/:userId/resendVerification are deliberately not exposed as MCP tools — the agent calls them directly with the restricted mk_user_* it received from marea.bootstrap_user. The 6-digit code flow needs the user in the loop; an MCP tool round-trip would add latency without changing the UX.

​
Discovery

Clients that support MCP discovery can also find the server via the well-known endpoint: 
https://mcp.mareaalcalina.com/.well-known/mcp.json
The well-known doc lists the same 7 tools, their JSON schemas, and the auth requirement (Bearer mk_dev_* or Bearer mk_user_*).

​
Troubleshooting

  • “Cannot find mcp-remote” — bump to npm ≥ 7 and Node ≥ 18; npx -y will fetch on first run.
  • “401 missing_authorization” — the --header argument was dropped during JSON-edit (common when editors strip backslashes). Re-paste from this page exactly.
  • “403 insufficient_scope” on marea.bootstrap_user — your dev key lacks developer:bootstrap. Re-issue at mareaalcalina.com/developers/keys.
  • Claude Desktop doesn’t see the tools — restart Claude Desktop fully (Cmd-Q on macOS); a tab reload isn’t enough.

​
Next steps

  • Bootstrap a user — same flow, narrated for the REST surface (verify is REST-only in MCP too).
  • Add and edit products — the calls behind marea.create_product and marea.update_product.
  • Publish a storefront — including the 402 / 422 / 451 gates that marea.publish_storefront surfaces via MCP elicitation.