MCP server

Native Model Context Protocol server. Live at mcp.turtleqr.com. Seven tools today, more coming.

What it does

Lets AI agents (Claude, Cursor, ChatGPT, custom) call TurtleQR's API as if it were a built-in capability. Your agents create codes, track scans, edit destinations without ever leaving the chat.

Get an API key

The MCP server authenticates with a TurtleQR API key. Create one in the dashboard:

Sign in at app.turtleqr.com
Go to API keys
Click Create API key, name it (e.g., "Claude desktop"), copy the token (shown once)

The token starts with qr_live_ or qr_test_.

Connect Claude Desktop

Add this to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "turtleqr": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.turtleqr.com/mcp",
        "--header",
        "Authorization:Bearer qr_live_YOUR_KEY_HERE"
      ]
    }
  }
}

Restart Claude Desktop. Try: "Create a TurtleQR code that points to https://example.com".

Connect Cursor

Add to your Cursor MCP config (~/.cursor/mcp.json):

{
  "mcpServers": {
    "turtleqr": {
      "url": "https://mcp.turtleqr.com/mcp",
      "headers": {
        "Authorization": "Bearer qr_live_YOUR_KEY_HERE"
      }
    }
  }
}

Tools available now

`create_qr`	Mint a new dynamic QR code
`list_qr_codes`	List the workspace's codes
`get_qr_code`	Read one code by id
`update_qr_target`	Change a code's destination, expiration, or status
`delete_qr_code`	Soft-delete (recoverable)
`get_qr_scans`	List recent scans for a code
`whoami`	Confirm authentication and workspace scope

Manual test with curl

The protocol is JSON-RPC 2.0 over POST. Smoke-test without a client:

curl -s -X POST https://mcp.turtleqr.com/mcp \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' | jq

# With auth, call a tool:
curl -s -X POST https://mcp.turtleqr.com/mcp \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer qr_live_YOUR_KEY" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call",
       "params":{"name":"whoami","arguments":{}}}' | jq

What's next for MCP

OAuth 2.1 with dynamic client registration so Claude.ai web (not just desktop) can connect without an API key. Tools for visual customization (when QR rendering ships in Phase 1.5), bulk operations, smart routing rules (Phase 2), and webhook management (Phase 2).