Model Context Protocol (MCP) Server Guide
Run the TOON Converter MCP server locally so Claude Desktop, Cursor, and other MCP-aware assistants can call the same conversion API you already ship.
Add this block under "mcpServers" then restart Claude Desktop so it loads the server:
{
"mcpServers": {
"toonverter": {
"command": "python",
"args": ["-m", "toonverter_mcp"],
"env": {
"TOONVERTER_API_KEY": "sk_live_your_key",
"TOONVERTER_API_URL": "https://toonverter.com/api"
}
}
}
}
Create or update a rule file with the entry below. Cursor reads from .cursor/rules rather than a single .cursorrules file.
{
"name": "toonverter",
"command": "python",
"args": ["-m", "toonverter_mcp"],
"env": {
"TOONVERTER_API_KEY": "sk_live_your_key",
"TOONVERTER_API_URL": "https://toonverter.com/api"
}
}
Include these environment variables with your MCP server definition so we can authenticate requests on your behalf.
| Name | Required | Description |
|---|---|---|
TOONVERTER_API_KEY |
Yes | API key from https://toonverter.com/dashboard. While the portal is offline, email support@toonverter.com for a managed key. |
TOONVERTER_API_URL |
Yes | Base URL for the hosted API. Leave as https://toonverter.com/api unless you run a staging stack. |
Each tool maps 1:1 to our REST API endpoints, so usage counts toward the same quota.
Convert JSON strings into TOON format and return the token-efficient payload.
Convert TOON payloads back into JSON.
Validate JSON syntax without performing a conversion.
Validate TOON syntax and return parser errors, if any.
Once configured, assistants automatically call the tool. Example Claude Desktop transcript:
# Claude Desktop transcript
User: "Convert this JSON payload to TOON"
Assistant (tool call):
{
"tool": "convert_json_to_toon",
"arguments": {
"json_string": "{\"name\": \"Alice\", \"team\": \"Growth\"}"
}
}
Assistant: "Here is the TOON output..."
Visit https://toonverter.com/dashboard/api-keys to generate keys. During maintenance windows or if the dashboard is temporarily unavailable, email support@toonverter.com and we will provision one manually.
Keys are shared between the REST API and the MCP server, so you only need to manage one credential.