Totalum MCP
Connect Totalum to any AI coding agent. Your agent can create projects, run the AI builder, query and modify your database, and deploy to production — all through natural language.
Connect Totalum to any MCP-compatible AI coding agent. Once connected, your agent can create full-stack projects, run the AI builder, query and edit the database, and deploy to production — entirely through natural language. It takes two steps.
Get your API key
The MCP server uses the same tlm_sk_ key as the REST API — there is no separate MCP key.
Add Totalum to your AI agent
Pick your client below and paste the config. That's it — your agent can now build with Totalum.
#Step 1 — Get your API key
The MCP key is the same tlm_sk_ key used for the REST API. Reveal it in the API section of your Totalum account — it becomes available once your account has an active credit balance.
Treat the key like a password. In shared configs, prefer an environment-variable reference (e.g. ${TOTALUM_API_KEY}) over hard-coding the raw key.
#Step 2 — Add Totalum to your AI agent
https://api-accounts.totalum.app/api/v1/mcpapi-key: <your key>Pick your agent:
#Claude Code
Run in your terminal:
claude mcp add-json totalum-vcaas '{
"type": "http",
"url": "https://api-accounts.totalum.app/api/v1/mcp",
"headers": { "api-key": "<API_KEY>" }
}'Or add it to .mcp.json in your project root for team sharing. Use ${TOTALUM_API_KEY} instead of the raw key for environment-variable support.
#Codex
Add the server (this preserves your existing MCP servers):
codex mcp add totalum-vcaas --url https://api-accounts.totalum.app/api/v1/mcpThen add the api-key header in ~/.codex/config.toml (the CLI does not support custom headers):
[mcp_servers.totalum-vcaas]
url = "https://api-accounts.totalum.app/api/v1/mcp"
http_headers = { "api-key" = "<API_KEY>" }For environment-variable support, replace http_headers with env_http_headers = { "api-key" = "TOTALUM_API_KEY" } and set export TOTALUM_API_KEY="your_key".
#Cursor
Add to ~/.cursor/mcp.json (or .cursor/mcp.json for project-level):
{
"mcpServers": {
"totalum-vcaas": {
"url": "https://api-accounts.totalum.app/api/v1/mcp",
"headers": {
"api-key": "<API_KEY>"
}
}
}
}If you already have other MCP servers, add the "totalum-vcaas" entry inside your existing mcpServers object. Restart Cursor after saving.
#Windsurf
Add to ~/.codeium/windsurf/mcp_config.json (note: Windsurf uses serverUrl, not url):
{
"mcpServers": {
"totalum-vcaas": {
"serverUrl": "https://api-accounts.totalum.app/api/v1/mcp",
"headers": {
"api-key": "<API_KEY>"
}
}
}
}Restart Windsurf completely after saving.
#Claude Desktop
Add to claude_desktop_config.json. Claude Desktop is stdio-only, so mcp-remote bridges the HTTP server (requires Node.js):
{
"mcpServers": {
"totalum-vcaas": {
"command": "npx",
"args": [
"-y", "mcp-remote",
"https://api-accounts.totalum.app/api/v1/mcp",
"--header",
"api-key: <API_KEY>"
]
}
}
}Config file location:
- macOS —
~/Library/Application Support/Claude/claude_desktop_config.json - Linux —
~/.config/Claude/claude_desktop_config.json - Windows —
%APPDATA%\Claude\claude_desktop_config.json
Restart Claude Desktop after saving.
#OpenClaw
Method A — /mcp slash command (safe, preserves existing MCP servers):
/mcp set totalum-vcaas={ "command": "npx", "args": ["-y", "mcp-remote", "https://api-accounts.totalum.app/api/v1/mcp", "--header", "api-key: <API_KEY>"] }Requires commands.mcp: true in your config. Use /mcp show to verify and /mcp unset totalum-vcaas to remove.
Method B — config file (~/.openclaw/openclaw.json, under mcp.servers):
{
"mcp": {
"servers": {
"totalum-vcaas": {
"command": "npx",
"args": [
"-y", "mcp-remote",
"https://api-accounts.totalum.app/api/v1/mcp",
"--header",
"api-key: <API_KEY>"
]
}
}
}
}OpenClaw is stdio-only, so mcp-remote bridges the HTTP server as a local process. Restart the gateway after editing the config. Requires Node.js.
#Any other MCP agent
Use these values to configure any MCP-compatible agent. The server uses Streamable HTTP (not stdio), and the api-key header must be sent with every request. Some agents use serverUrl instead of url — check your agent's docs.
{
"mcpServers": {
"totalum-vcaas": {
"url": "https://api-accounts.totalum.app/api/v1/mcp",
"headers": {
"api-key": "<API_KEY>"
}
}
}
}For stdio-only agents, bridge the HTTP server with the mcp-remote npm package (requires Node.js).
#What your agent can do
The MCP tools map 1:1 to the REST API endpoints — anything the API can do, your agent can do through MCP:
- Create and manage full-stack projects
- Run the AI builder with natural language
- Query, create, and edit database records
- Deploy to production with CDN
- Manage secrets, files, versions, custom domains and webhooks
#See it in action
Create and deploy multiple websites in parallel using Claude Code + the Totalum MCP:
