Skip to main content
Use Marble’s Model Context Protocol server to let AI agents read and manage content in your workspace through the Marble API.
You need a Marble API key. Write tools such as create, update, and delete require a private API key.

Installation

The quickest way to add Marble to supported MCP clients is with the open-source add-mcp CLI. It detects supported agents and writes each client’s native MCP configuration.
add-mcp is maintained separately from Marble and writes configuration files on your machine. By default it writes project-level configuration; -g writes user-level configuration. Review the agents and scope it selects before confirming.
Leave the placeholder in single quotes so your shell does not expand it before add-mcp runs. Because the command is interactive, the CLI prompts for the key and the selected agents. Use -a <agent> to target specific clients, or omit -g to install at project scope.

Install in Cursor

Open Cursor with the Marble MCP server pre-filled.
1

Open the installer

Click Install in Cursor and allow your browser to open Cursor.
2

Add your API key

Cursor installs the server with this header:
Set MCP_MARBLE_API_KEY in your environment before starting Cursor.
3

Verify the connection

Open Cursor’s MCP settings and confirm that the marble server is enabled. The server URL should end with /mcp.
You can also add the server manually in Cursor:

Available Tools

Tool badges describe how clients may present or approve tool calls:
  • READ-ONLY: reads data without changing your workspace
  • DESTRUCTIVE: may update or delete existing content

Scheduling Posts

Scheduling uses create_post and update_post, so there’s no separate tool. Ask your agent in plain words:
  • “Schedule this post for Friday at 9am.”
  • “Move the launch post to next Monday.”
  • “Publish the scheduled launch post now.”
  • “Unschedule the launch post.”
Times use your workspace timezone unless you name a zone, such as “9am New York time”. Your agent reads scheduled posts through a private API key. The agent repeats the go-live time back to you in UTC. Check that it matches what you asked for. The agent can’t see your workspace timezone, and older workspaces may still be on the default Europe/London. If the time looks wrong, change the timezone in Settings and reschedule the post.

Authentication

The MCP server accepts your Marble API key through the standard API header:
The Bearer prefix is also accepted, but is not required by Marble. For clients that need a custom header, these compatibility aliases are also accepted:
Keep private API keys out of client-side code and public repositories.

Troubleshooting

If your client cannot connect, verify that:
  • The URL ends with /mcp
  • The API key header is present
  • Your key has the permissions needed for the tool you are calling
  • Write operations use a private Marble API key