Layers
Partner APIMCP server

Overview

The Layers MCP server is a thin, 1:1 wrapper over the Partner API that lets an AI agent — Claude, ChatGPT, Cursor, any MCP client — call Layers as native tools, with no HTTP code to write.

View as Markdown

The Layers MCP server exposes the Partner API as Model Context Protocol tools. An MCP client (Claude, ChatGPT via the OpenAI Agents SDK, Cursor, or any other) spawns it, and the agent can then create projects, generate content, schedule posts, and read metrics by calling tools directly — without you writing a single fetch.

It is published to npm as @layers/mcp-server and runs locally over stdio. There is no hosted endpoint to point at and no service to operate.

It's a thin wrapper, by design. Every tool maps to exactly one documented /v1 endpoint. The MCP server adds no new capabilities — it's an ergonomic surface over the same API, so it tracks the API reference one-to-one. When you want the precise request/response shape for a tool, read its linked endpoint page.

Who it's for

  • Agent builders wiring Layers into an AI assistant or autonomous workflow, who want tool-calling instead of an HTTP client.
  • Anyone prototyping against the Partner API who'd rather say "list my Layers projects" in an MCP client than hand-roll requests.

If you're integrating Layers into a conventional backend, you don't need the MCP server — call the Partner API directly.

How it relates to the Partner API

The MCP server is a client of the Partner API. It authenticates with the same lp_... key, talks to the same https://api.layers.com/v1 host, and inherits the same auth, scopes, idempotency, rate limits, and sandbox behavior.

That means everything you already know about the API carries over:

  • Auth & scopes — the key you pass the server determines what it can do. See Authentication.
  • Sandbox — a lp_test_... key returns fixture-backed results, so an agent can be developed safely against it. See Sandbox.
  • Async jobs, pagination, idempotency, errors — identical semantics, surfaced through MCP conventions. See How it works.

Next steps

Package

On this page