// mcp

Every primitive, every agent.

Gyrence is a native Model Context Protocol server. Point Claude Desktop, Cursor, Continue, Windsurf — or any MCP-aware agent — at one URL and the five primitives appear as tools. No HTTP wiring. No bespoke schemas. Identical credits to the REST API.

Get your MCP URL Read the MCP docs

// setup

30 seconds in the client of your choice.

Generate an API key in the console, then paste the config below. The same URL works for every MCP client — only the config file location differs.

Edit ~/Library/Application Support/Claude/claude_desktop_config.json

json

{
  "mcpServers": {
    "gyrence": {
      "url": "https://www.gyrence.com/api/mcp/<YOUR_API_KEY>"
    }
  }
}

Restart Claude Desktop. The five gyrence_* tools appear in the tools menu.

Replace <YOUR_API_KEY> with a key starting mc_ from /app/api-keys. The key is embedded in the URL — keep it scoped per project.

// tools

Five tools your agent already knows how to use.

Same input schemas as /api/v1/*. Same response envelope. Same credit cost. The MCP endpoint and the HTTP endpoint share a single handler — billing parity is by construction.

gyrence_search2 + per result cr

Resolve a natural-language query into ranked, deduped URLs. Optional inline fetch returns clean markdown in one call.

gyrence_fetch1 (http) / 3 (browser) cr

Fetch any URL as clean markdown, lightly-cleaned HTML, link graph, and metadata. Auto-escalates to a headless browser on soft blocks.

gyrence_gyresum of per-page costs cr

Walk a site breadth-first from a seed URL within a page budget. Same-domain by default, partial-success semantics, markdown per page.

gyrence_extract5 cr

Schema-guided structured extraction powered by an LLM. Describe what you want, receive strict JSON.

gyrence_map1 flat cr

Enumerate every URL on a site via its sitemaps with a depth-1 homepage fallback. No fetching, no rendering.

// why mcp

The shortest path from agent to the open web.

No glue code

Skip the fetch wrapper, schema definitions, retry logic, and tool registration. Your agent sees gyrence_* the moment the client reloads.

Billing parity

MCP and HTTP share one handler. A gyrence_fetch tool call costs exactly what /api/v1/fetch costs — same credit, same usage event, same activity feed.

Schema-compatible

MCP tool inputs match the OpenAPI spec at /openapi.json. Your agent's reasoning about parameters carries over from REST docs unchanged.

Drop us into your agent.

Free workspace, first key in under a minute, MCP URL ready the moment the key is created.

Get an MCP URL