TOON Converter MCP

Model Context Protocol (MCP) Server Guide

Overview

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.

  • Expose conversion + validation tools over MCP with zero new auth surface area.
  • Reuse the exact API key, usage limits, and rate limits that power https://toonverter.com/api.
  • Keep credentials on-device—assistants talk to your local MCP process, which relays to the hosted API.
The MCP protocol uses stdio streams, so clients expect a local command instead of a remote HTTPS URL.

Quick start

  1. Install Python 3.10+ and either clone this repo or install the upcoming `toonverter-mcp` package.
  2. Generate/obtain a TOONVERTER_API_KEY. Use https://toonverter.com/dashboard when it is available; until then email support@toonverter.com and we will issue one manually.
  3. Set TOONVERTER_API_URL=https://toonverter.com/api (or your staging URL).
  4. Add the toonverter entry to your MCP client config (Claude Desktop, Cursor, etc.) and restart the assistant.

Configuration examples

Claude Desktop (mcp_config.json)

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" } } } }

Cursor (.cursor/rules/*.json)

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" } }

Environment variables

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.

Tools exposed by the MCP server

Each tool maps 1:1 to our REST API endpoints, so usage counts toward the same quota.

convert_json_to_toon

Convert JSON strings into TOON format and return the token-efficient payload.

convert_toon_to_json

Convert TOON payloads back into JSON.

validate_json

Validate JSON syntax without performing a conversion.

validate_toon

Validate TOON syntax and return parser errors, if any.

Sample tool call

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..."

API keys & access

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.

Tip — MCP clients reject simple "url" entries because the protocol expects a local command + stdio server. Use the command/args/env block above instead of a bare URL.

Need help shipping the MCP integration?

We can walk you through provisioning keys, securing configs, and testing MCP flows inside Cursor or Claude Desktop.

Email Support