Reference· 3 minUpdated 4d ago

MCP - Model Context Protocol#

TetraFi docs ship as an MCP server. Any MCP-aware agent - Claude Desktop, Cursor, Windsurf, Continue, or your own - can search, read, and introspect the corpus the same way your IDE autocomplete does.

The manifest lives at /docs/mcp/manifest.json. Point any MCP client at that URL to discover the full tool set.

What you get#

list_docs

Enumerate every doc page with slug + metadata.

read_doc

Raw markdown + frontmatter for any slug.

search_docs

Ranked substring search across the corpus.

get_schema

Resolve an OpenAPI schema by name.

get_endpoint

Resolve an OpenAPI operation by id or method+path.

Install - Claude Desktop / Cursor#

Native MCP clients speak JSON-RPC over stdio. Drop this thin bridge into your claude_desktop_config.json (or Cursor's mcp.json):

JSON

1{
2  "mcpServers": {
3    "tetrafi-docs": {
4      "command": "npx",
5      "args": ["-y", "mcp-remote", "https://tetrafi.io/docs/mcp/manifest.json"]
6    }
7  }
8}

8 linesjson

Restart the client. tetrafi-docs appears as an available tool set; the assistant can now call search_docs, read_doc, and the rest.

No MCP client? The same endpoints work as plain REST - curl https://tetrafi.io/api/mcp/search-docs?q=rfq returns JSON.

Direct REST examples#

Bash

1# List every published doc
2curl https://tetrafi.io/api/mcp/list-docs
3
4# Read a single page as markdown + frontmatter
5curl "https://tetrafi.io/api/mcp/read-doc?slug=integration/taker-guide"
6
7# Ranked search
8curl "https://tetrafi.io/api/mcp/search-docs?q=webhook%20signature&limit=5"
9
10# Resolve a schema by name
11curl "https://tetrafi.io/api/mcp/get-schema?name=Quote"
12
13# Resolve an endpoint by operationId OR method+path
14curl "https://tetrafi.io/api/mcp/get-endpoint?operationId=submitRFQ"
15curl "https://tetrafi.io/api/mcp/get-endpoint?method=POST&path=/rfq"

15 linesbash

MCP - Model Context Protocol#

What you get#

Install - Claude Desktop / Cursor#

Direct REST examples#

See Also#

Related topics