MCP Server

The Model Context Protocol (MCP) server provides a standardized interface that allows any compatible AI model or agent to access your Decks workspace in a simple and secure way.

Connect to the MCP server natively in Claude, Cursor, and other clients or use the mcp-remote module for backwards compatibility with clients that do not support remote MCP.

Decks's MCP server follows the authenticated remote MCP spec, so the server is centrally hosted and managed. The MCP server has tools available for reading and modifying slide decks, slides, and layers — with more functionality on the way.

Setup Instructions

General

The MCP server supports Streamable HTTP transport with OAuth 2.1 and dynamic client registration for authentication at the following address:

https://withdecks.com/api/mcp

For instructions for specific clients, read on.

Claude Code

claude mcp add --transport http decks https://withdecks.com/api/mcp

Then run /mcponce you've opened a Claude Code session to go through the authentication flow.

Codex

Configuration via CLI:

codex mcp add decks --url https://withdecks.com/api/mcp

Then authenticate with your Decks account:

codex mcp login decks

Cursor

Search for Decks from Cursor's MCP tools page, or add manually:

{
  "mcpServers": {
    "decks": {
      "type": "http",
      "url": "https://withdecks.com/api/mcp"
    }
  }
}

Visual Studio Code

{
  "mcpServers": {
    "ablo": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://withdecks.com/api/mcp"]
    }
  }
}

Ctrl/Cmd + P and search for MCP: Add Server
Select Command (stdio)
Enter: npx mcp-remote https://withdecks.com/api/mcp
Name it Decks and start the server

Windsurf

Ctrl/Cmd + , to open settings
Scroll to Cascade → MCP servers
Select Add Server → Add custom server

{
  "mcpServers": {
    "ablo": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://withdecks.com/api/mcp"]
    }
  }
}

Zed

Cmd + , to open settings and add:

{
  "context_servers": {
    "ablo": {
      "source": "custom",
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://withdecks.com/api/mcp"],
      "env": {}
    }
  }
}

Others

Hundreds of tools now support MCP servers. Configure them with:

Command: npx
Arguments: -y mcp-remote https://withdecks.com/api/mcp
Environment: None

Available Tools

The MCP server exposes the following tools for interacting with your Decks workspace. All mutations sync in real-time to connected clients.

Tool	Description
`execute_code`	Read and edit decks through the validated Decks sandbox. Writes commit through the live sync engine.
`get_slide_screenshot`	Render a slide as a PNG for visual review.
`get_guide`	Load focused instructions for deck, slide, chart, and layout work.
`memory`	Read and maintain persistent workspace memory.

FAQ

Does the MCP support Streamable HTTP?

Yes, at the https://withdecks.com/api/mcp endpoint.

Does MCP use the API keys from Settings?

No. MCP uses Decks sign-in through OAuth so the agent receives your user and organization permissions. Secret API keys are for server-side API automation and are not MCP login tokens.

Why am I seeing an internal server error when trying to connect?

Remove the saved Decks connection in your MCP client, add it again, and complete Decks sign-in in the browser. Codex users can rerun codex mcp login decks.

What data can AI agents access?

Agents can read and modify slide decks, slides, and layers within your organization. All operations are scoped to the authenticated user's permissions.

Do changes sync in real-time?

Yes. All mutations go through the Decks sync path, so changes made via MCP appear instantly for any connected clients (browser, Electron, other MCP sessions).