Laya MCP server

Give Claude, Cursor or any other AI assistant Laya's fast, calibrated decisions as built-in tools. One address, your existing API key, no code.

What is MCP, in plain words?

MCP (the Model Context Protocol) is an open standard for plugging tools into AI assistants, a bit like USB for AI apps. You give your assistant the address of an MCP server; it reads the list of tools the server offers and calls them when they help with what you asked.

Laya's MCP server offers decision tools. Ask Claude "which of these 200 tickets are refund requests, and how sure are you?" and it can call Laya's classify tool on each one, getting a label with a probability back in about a tenth of a second instead of writing out its reasoning. Laya never generates text, so it cannot invent a label that is not on your list.

• Product and ops teams: triage, tag and score text straight from a chat with Claude.
• Developers: let your coding agent label data, check outputs or route requests while it works.
• Everyone: the same key, billing, limits and data residency as the REST API.

Connect your assistant

You need an API key from the dashboard (new workspaces get 5 free runs). Pick your client, paste your key if you like, and copy the snippet.

claude mcp add --transport http laya https://api.laya.studio/mcp --header "Authorization: Bearer lsk_live_…"

Claude Code in one line

claude mcp add --transport http laya https://api.laya.studio/mcp --header "Authorization: Bearer lsk_live_…"

To keep every call in Switzerland, add a second header: --header "x-laya-residency: ch" (JSON configs: add "x-laya-residency": "ch" to headers). See data residency.

The six tools

Pick a tool to see what it does, its parameters and an example call. The four decision tools can run live on the free demo, right here.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "decide",
    "arguments": {
      "state": "I was charged twice for order #4411 and I need the money back today.",
      "questions": {
        "intent": {
          "type": "choice",
          "instructions": "What does the customer want?",
          "criteria": {
            "refund": "money back or a duplicate charge reversed",
            "tracking": "where is my parcel",
            "other": "anything else"
          }
        },
        "urgent": {
          "type": "noul",
          "instructions": "Does the message communicate time pressure?"
        }
      }
    }
  }
}

{
  "id": "dec_3f9c0a…",
  "model": "laya-rl-agent",
  "answers": {
    "intent": {
      "type": "choice",
      "choice": "refund",
      "probabilities": {
        "refund": 0.9466,
        "tracking": 0.0456,
        "other": 0.0078
      },
      "confidence": 0.7899
    },
    "urgent": {
      "type": "noul",
      "noul": 0.912,
      "confidence": 0.824
    }
  },
  "usage": {
    "input_tokens": 109,
    "output_tokens": 0
  },
  "routing": {
    "model": "english",
    "reason": "English Latin text"
  },
  "credits_charged": 109
}

decide takes the full question format from choice, score and noul questions; classify, yes_no and score are shortcuts for a single question.

Billing, limits and errors

MCP tool calls use the same pipeline as POST /v1/systemone: the same key, rate limit, credit balance and usage records (logged with the endpoint name mcp). Each successful tool call is one run: the first 5 free runs of a workspace cost nothing, then you pay the input tokens the model reads (1 credit = 1 input token, $0.0294 per 1M input tokens). Failed calls are free. See pricing.

Unknown methods return JSON-RPC error -32601; an unknown tool name returns -32602. Batches (a JSON array of messages) are supported and run in order. More in errors, limits & retries.

Protocol details (for client builders)

Streamable HTTP transport, JSON responses only. Protocol version 2025-06-18; clients asking for 2025-03-26 or 2024-11-05 get that version back. Supported methods: initialize, notifications/initialized, ping, tools/list and tools/call. A session id is returned on initialize but never required.

POST https://api.laya.studio/mcp
Authorization: Bearer lsk_live_…
Content-Type: application/json
Accept: application/json, text/event-stream

{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"my-app","version":"1.0"}}}

→ 200, Mcp-Session-Id: mcp_…
{"jsonrpc":"2.0","id":1,"result":{"protocolVersion":"2025-06-18","capabilities":{"tools":{}},"serverInfo":{"name":"laya-studio","title":"Laya Studio","version":"1.0.0"},"instructions":"…"}}

Questions