MCP Server Documentation — Setup & JSON-RPC API

Connect Claude, Cursor or LM Studio to the Arttron MCP server: real JSON config, a JSON-RPC tools/call example and the REST API reference for scripts.

Getting Started

1. Authentication

Send your key as a Bearer token: Authorization: Bearer YOUR_API_KEY.

2. Get Your API Key

claude.ai connector (no API key needed)

Open Settings → Connectors → Add custom connector, paste the connector URL and approve the OAuth prompt. claude.ai registers itself, so no API key is required.

MCP (JSON-RPC)

The MCP endpoint speaks JSON-RPC 2.0 over Streamable HTTP. Point your client at https://arttron.dev/api/mcp and authenticate with a Bearer API key — the twelve tools are discovered automatically.

Connector URL

https://arttron.dev/api/mcp

Note: /api/mcp/stream is the legacy SSE route kept for the REST API only. It is not an MCP endpoint, so it will not work in MCP clients or connectors — always use https://arttron.dev/api/mcp.

Send JSON-RPC 2.0 to the MCP endpoint with the Authorization header; the tool result arrives in the result.content blocks.

MCP client configuration

{
  "mcpServers": {
    "arttron": {
      "url": "https://arttron.dev/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

JSON-RPC request (tools/call)

POST /api/mcp
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json
Accept: application/json, text/event-stream

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "dns_lookup",
    "arguments": { "domain": "example.com", "type": "MX" }
  }
}

REST API

The plain REST endpoints below are a separate, script-friendly API — they are not MCP transports. Listing tools is public; calling a tool needs a Bearer key.

REST request

POST /api/mcp/tools/call
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

{
  "tool": "dns_lookup",
  "input": { "domain": "example.com", "type": "MX" }
}

Available Tools

All twelve tools are served by the MCP endpoint https://arttron.dev/api/mcp. Use the Authorization header with your API key.

dns_lookup — Resolve DNS records
ip_lookup — Geolocate IP addresses
qr_generate — Generate QR codes
list_versions — List available versions
download_dev_server — Download server binary
proxy_image — Proxy external images

Rate Limits

Free tier: 200 tool calls per month for MCP keys and 100 for API keys — that monthly quota is the headline limit.

Per-tool limits apply on top of the monthly quota (for example 20 DNS lookups/s, 30 IP lookups/min, 15 image proxies/s); all are counted per API key.

Need help?

Back to MCP

What the MCP documentation covers

The documentation walks from zero to a first tool call. Step one is authentication: create a free account and generate an API key, or, for claude.ai, register the connector URL and approve the OAuth prompt so no key is needed. Step two is the client configuration — the mcpServers block below points your client at the Streamable HTTP endpoint.

The rest of the page is the wire format. The MCP endpoint speaks JSON-RPC 2.0; a tools/call request names the tool and passes its arguments, and the result arrives in content blocks. Worked example: a tools/call for dns_lookup with {"domain":"example.com","type":"MX"} returns the MX records for example.com. A separate, script-friendly REST surface is documented for callers that do not speak JSON-RPC.

How to connect a client

Sign in and create an API key, or add the connector URL in claude.ai and approve OAuth.
Paste the mcpServers block with the endpoint https://arttron.dev/api/mcp and your Bearer key.
Restart the client; it discovers all twelve tools during the MCP handshake.
Call a tool, for example dns_lookup, and read the result from the content blocks.

Frequently asked questions about the docs

Which endpoint should I use?

Always https://arttron.dev/api/mcp for MCP clients. The /api/mcp/stream path is the legacy SSE route kept only for the REST API and is not an MCP endpoint.

Do I need an API key with claude.ai?

No. Adding the connector URL at Settings → Connectors → Add custom connector registers the client over OAuth 2.1, so no API key is required there.

Can I call the tools from a script?

Yes. The REST surface — tools/list is public and tools/call needs a Bearer key — is documented on the same page for callers that do not speak JSON-RPC.