Developers

MCP Server

Generate game assets from a conversation with your AI assistant.

Included with the Pro and Studio plans. See what a generation costs

Using a coding agent? Give it the Ludo CLI instead. It's the recommended way to connect agents to Ludo. It uses far fewer tokens, because the agent loads only the commands it needs, not the schema of every tool. And it handles files for you: local files go in by path and results are saved to disk, so the agent never has to push base64 through its context.

Set up in 3 steps

Subscribe to Pro or Studio

API and MCP access is included on the Pro and Studio plans.

Get Your API Key

Log in at app.ludo.ai, open API Keys from the sidebar or the user menu, name your key and click Create key. Copy it right away: it is shown only once.

Connect your client

Add the Ludo MCP server to your assistant with one of the setups below.

MCP (Model Context Protocol)

Connect Ludo.ai to AI assistants like Claude using the Model Context Protocol. Generate game assets, animate sprites, and create visuals directly through natural language conversations.

MCP Server URL

https://mcp.ludo.ai/mcp

Use this URL to connect any MCP-compatible client.

Authorization Header

Authorization: ApiKey YOUR_API_KEY

Setup with Claude Code

Run this in your terminal (add -s user to use it in every project):
claude mcp add --transport http ludo https://mcp.ludo.ai/mcp --header "Authorization: ApiKey YOUR_API_KEY"
Start Claude Code. The Ludo tools are listed under /mcp.

Setup with Codex

Add this to ~/.codex/config.toml:
~/.codex/config.toml
```
[mcp_servers.ludo-ai]
url = "https://mcp.ludo.ai/mcp"

[mcp_servers.ludo-ai.http_headers]
Authorization = "ApiKey YOUR_API_KEY"
```
Restart Codex. The CLI, the IDE extension and the desktop app share this file.

Setup with Cursor

Add to CursorThen replace YOUR_API_KEY with your key in Cursor's MCP settings.

Or add this to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):
~/.cursor/mcp.json
```
{
  "mcpServers": {
    "ludo-ai": {
      "url": "https://mcp.ludo.ai/mcp",
      "headers": {
        "Authorization": "ApiKey YOUR_API_KEY"
      }
    }
  }
}
```

Setup with VS Code

Add to VS CodeVS Code asks for your key once and stores it securely.

Or create .vscode/mcp.json (MCP: Open User Configuration for every project). VS Code asks for your key once and stores it securely:
.vscode/mcp.json
```
{
  "inputs": [
    {
      "type": "promptString",
      "id": "ludo-api-key",
      "description": "Ludo.ai API key",
      "password": true
    }
  ],
  "servers": {
    "ludo-ai": {
      "type": "http",
      "url": "https://mcp.ludo.ai/mcp",
      "headers": {
        "Authorization": "ApiKey ${input:ludo-api-key}"
      }
    }
  }
}
```
Use Copilot Chat in Agent mode: the Ludo tools appear in the tools picker.

Setup with Windsurf

In Cascade's MCP menu, choose Open MCP config file and add this:
mcp_config.json
```
{
  "mcpServers": {
    "ludo-ai": {
      "serverUrl": "https://mcp.ludo.ai/mcp",
      "headers": {
        "Authorization": "ApiKey YOUR_API_KEY"
      }
    }
  }
}
```
Then press refresh in the MCP panel.

Setup with Cline

Click Configure MCP Servers in Cline and add this to cline_mcp_settings.json:
cline_mcp_settings.json
```
{
  "mcpServers": {
    "ludo-ai": {
      "type": "streamableHttp",
      "url": "https://mcp.ludo.ai/mcp",
      "headers": {
        "Authorization": "ApiKey YOUR_API_KEY"
      }
    }
  }
}
```

Setup with Zed

Add this to ~/.config/zed/settings.json, or use Settings > AI > MCP Servers > Add Remote Server:
~/.config/zed/settings.json
```
{
  "context_servers": {
    "ludo-ai": {
      "url": "https://mcp.ludo.ai/mcp",
      "headers": {
        "Authorization": "ApiKey YOUR_API_KEY"
      }
    }
  }
}
```

Setup with Kiro

Add this to ~/.kiro/settings/mcp.json (or .kiro/settings/mcp.json in a project):
~/.kiro/settings/mcp.json
```
{
  "mcpServers": {
    "ludo-ai": {
      "url": "https://mcp.ludo.ai/mcp",
      "headers": {
        "Authorization": "ApiKey YOUR_API_KEY"
      }
    }
  }
}
```

Setup with Other clients

Server URL (Streamable HTTP):
https://mcp.ludo.ai/mcp
Header:
Authorization: ApiKey YOUR_API_KEY
A client that only runs local (stdio) servers can bridge with mcp-remote (needs Node.js). Keep the header argument without spaces; the key goes in env:
```
{
  "command": "npx",
  "args": [
    "-y",
    "mcp-remote",
    "https://mcp.ludo.ai/mcp",
    "--header",
    "Authorization:${LUDO_AUTH}"
  ],
  "env": {
    "LUDO_AUTH": "ApiKey YOUR_API_KEY"
  }
}
```

CLI or MCP?

For AI agents, use the CLI: it uses far fewer tokens, and files go in by path instead of base64. MCP is for chat assistants that can't run commands. Explore the CLI

	Ludo CLI	MCP server
Setup	npm install, then ludo login in the browser	Add the server and API key to each client
Files	Pass local paths; results saved to disk	URLs and base64; results expire after 7 days unless downloaded
Token use	Low: reads only the commands it uses, and local files go in by path	High: loads every tool schema (30+) up front, and a local file has to be written out as base64 inside the tool call
Works in	Any terminal, any agent that can run commands, scripts and CI	MCP-enabled clients
Best for	Coding agents (recommended), building a game in a repo, batch work, automation	Chat assistants that can't run commands

Build with Ludo from your assistant

Ask for sprites, animations, 3D and audio in plain words.

Get your API key Compare all

Need help with integration?Join our Discord Contact us