marble work ships its own MCP server. MCP (Model Context Protocol) is the open standard that lets AI assistants such as Claude, Claude Code or Cursor use external tools. Once connected, your AI assistant can work directly inside marble work: create clients, projects and tasks, build task chains, manage agents and knowledge, and read back results.

<aside> 🚀 The REST API and MCP server require the “Rocket” plan.

</aside>

An example: you tell Claude Code "Create a task in marble work: blog post on topic X, research by Wilma, then approval by me", and the assistant does it through the tools of this server.

<aside> 🔀

The MCP server and the REST API expose the same operations with the same permissions and limits. MCP is the right route for AI assistants, the REST API is the right one for your own scripts and integrations. See the page marble work » REST-API 🇺🇸

</aside>

Endpoint and protocol

<https://mcp.marblework.app>

Authentication

The server uses marble work API keys. An organization admin creates one in the app under Settings → Organization → API access, choosing the scopes (which tool groups the key may use). The key is shown only once.

Send the key as a header, in either of these two forms:

Authorization: Bearer mw_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
x-api-key: mw_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

The metadata methods (initialize, ping, tools/list, resources/list, resources/templates/list) work without a key so clients can establish the connection. Only tools/call and resources/read require it; without a valid key the server responds with HTTP 401 and the JSON-RPC error code -32001.

Note: the tool list always shows all tools, regardless of your key's scopes. Whether a call is allowed is decided at tools/call time (error code missing_scope).

Setup

Replace the placeholder in all examples with your real key.

Claude Code