Agent setup

Or copy the sentence and paste it into your AI coding agent. The agent reads Marka's setup instructions at agent-setup/prompt.md, asks you for an API key once, checks the key, and connects itself to Marka's hosted MCP gateway. It then tells you what it set up and where it stored the key.

The icons open the guide for each agent, if you would rather read the steps first or run them yourself.

What your agent gets

Six operations on the hosted gateway at https://joinmarka.com/api/mcp: search the live catalogue, read a listing, list categories, look up a seller, and create or update a listing draft. No operation publishes a listing. Publishing stays your decision, taken in the Marka app. See Tools for the full list.

By default the gateway lists two tools, search_tools and execute_typescript, instead of one tool per operation. Your agent calls search_tools to see the operations, then runs a short program through execute_typescript that calls them, for example await external_search_listings({ query: "chair" }). If the gateway lists the six operations as tools instead, your agent calls them directly. Either way the operations and their checks are the same.

Before you start: an API key

Create a key at Settings → API keys while signed in. The full mk_… value is shown once, so copy it when it appears.

Put the key in the MARKA_API_KEY environment variable of the shell your agent starts from. Every guide below reads it from there, so the key itself never lands in a file you check in. When you use the pasted sentence, the agent asks you for the key if that variable is not set.

Pick your agent

Any other MCP client

A client that speaks Streamable HTTP can use the hosted gateway with a config block of this shape. Put it in the client's user-level config, never in a file that is checked in.

{
  "mcpServers": {
    "marka": {
      "type": "http",
      "url": "https://joinmarka.com/api/mcp",
      "headers": {
        "x-api-key": "${MARKA_API_KEY}"
      }
    }
  }
}

A client that can only start a local process over stdio runs the SDK's bridge instead. It needs Node.js 20.19 or newer and reads the key from MARKA_API_KEY. The bridge lists its own six tools directly, and they differ from the hosted gateway's operations. The MCP overview explains how the two servers differ.

npx -y -p @joinmarka/sdk marka-mcp-stdio

Check the key

This call works on every plan. A good key prints a JSON object with your user and plan. A missing, revoked or expired key prints {"error":"unauthorized"} and nothing else.

curl -sS https://joinmarka.com/api/v1/me -H "x-api-key: $MARKA_API_KEY"

For agents

The instructions an agent follows are published as plain Markdown at https://docs.joinmarka.com/agent-setup/prompt.md. They are built from the same data as these pages, so both always give the same commands.