Wrenda MCP

What it is (and what it isn't)

Wrenda has two things called MCP. They point in opposite directions:

Use Wrenda MCP when you want to ask questions like “which pages did GPTBot hit this week?” from the tool you already work in, or hand an agent a task like “analyze the pricing page and enable the FAQ suggestion” without opening the dashboard.

1. Create an API key

1. Open Settings → API & MCP

   You need the admin role. The page lists every key with its preview, scopes, last use and expiry.

2. Create key

   Name it after what will hold it (“Claude Code — laptop”). Choose a scope: Read for reporting and questions, Read + Write if the agent should be able to change optimizations or purge cache. Pick an expiry — 90 days is a sensible default for a laptop.

3. Copy it — once

   The full key (aics_…) is shown exactly once, with the four configs below already filled in. Wrenda stores only a hash. If you lose it, revoke it and create another.

2. Connect a client

Replace <key> with your key. The endpoint is the same for every client: https://api.wrenda.ai/mcp.

claude mcp add --transport http wrenda https://api.wrenda.ai/mcp --header "Authorization: Bearer <key>"

{
  "mcpServers": {
    "wrenda": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.wrenda.ai/mcp",
        "--header",
        "Authorization: Bearer <key>"
      ]
    }
  }
}

{
  "mcpServers": {
    "wrenda": {
      "url": "https://api.wrenda.ai/mcp",
      "headers": {
        "Authorization": "Bearer <key>"
      }
    }
  }
}

# 1. Handshake
curl -s -X POST https://api.wrenda.ai/mcp \
  -H "Authorization: Bearer <key>" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"curl","version":"1.0"}}}'

# 2. List the tools
curl -s -X POST https://api.wrenda.ai/mcp \
  -H "Authorization: Bearer <key>" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/list"}'

# 3. Call one
curl -s -X POST https://api.wrenda.ai/mcp \
  -H "Authorization: Bearer <key>" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"list_domains","arguments":{}}}'

Transport

MCP Streamable HTTP, stateless — one JSON-RPC 2.0 request (or batch) per POST, JSON response. No sessions, no server-initiated streams.

Protocol version

2025-03-26

Auth header

Authorization: Bearer aics_…

Domain arguments

Accept the hostname (shop.acme.com) or the domain id. Unknown → a readable error telling the agent to call list_domains.

Discovery

GET https://api.wrenda.ai/mcp returns { name, version, transport, docs } without auth.

3. Tools

Every result is JSON in content[0].text and again as structuredContent; errors are plain sentences an agent can act on. The example prompts are what you would type into the client.

Read — any key

Write — Read + Write keys only

Page Optimization payloads

create_page_optimization takes a render_target that decides the payload shape. Both are validated; the URL must be on the named domain and is canonicalised to origin + path.

Pass enable: true to switch it on immediately (the cached copy is versioned so crawlers see it on the next request); otherwise it lands as suggested for review in the dashboard.

4. Safety

Write scope

Read-only keys get a clear "This key is read-only" tool error on write tools — nothing changes. Give agents write keys only for the session that needs them.

Audit log

Every write-tool call is recorded in the audit log as mcp_<tool> with the key that made it. Read calls are not logged.

Rate limit

120 calls per minute per key. Over that the endpoint answers HTTP 429; well-behaved clients back off automatically.

Allowance

Optimizations created over MCP are the same as ones from the dashboard: they count against nothing extra, but purge_cache on a whole domain means every page is re-optimized on its next crawl, which does spend uncached requests. See Cache & purge.

Revoke

Revoking a key ends every client using it at once. Keys with an expiry stop working at the timestamp shown in the table.

Troubleshooting

Next