Developers / MCP Integration

MCP Integration

Read documentation, investigate execution records or connect remote tools through distinct MCP interfaces.

Dyadic Documentation

The official MCP server searches the generated reference. It describes interfaces; it never executes API operations, runs code or grants additional permissions.

Endpoint: https://api.dyadic.app/documentation/mcp
Transport: Streamable HTTP, stateless JSON responses
Public access: No API key is required for public API contracts and SDK documentation.

Server URL

https://api.dyadic.app/documentation/mcp

In an MCP client, add a remote HTTP server using this URL. Configuration formats differ between clients. This server accepts POST; it does not provide a persistent SSE stream. Third-party browser origins are not accepted; native or server-side MCP clients can connect without a browser Origin header. Protocol versions: 2025-06-18 and 2025-03-26.

Available Tools

Tool	Purpose
`categories`	Browse major sections, categories and languages.
`search`	Find modules, functions and API operations. Choose fuzzy, exact or keyword matching; filter and paginate results.
`read`	Read an exact reference returned by search, with paged declarations and text.
`api`	Read an operation's parameters, authentication and response contract. It does not invoke the operation.

Search Example

JSON-RPC tools/call

{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"search","arguments":{"query":"chat completions","mode":"fuzzy","limit":5}}}

Read the exact ref from a search result using read. For an API lookup, supply a contract (openai, platform, anthropic or gateway), the exact path and HTTP method.

Use With Iris

Open Store, then MCP Servers. Dyadic Documentation is the first official server. Iris uses the same generated references through local read tools; no external research or model call is required by the documentation server itself. Account Off and per-method switches apply. Custom agents with explicit MCP selections must select this server.

Agent Black Box MCP

Connect to https://api.dyadic.app/v1/blackbox/mcp with a Bearer API key. This is a separate service: it records and investigates the key's runs and includes mutations. Initialize with protocol 2025-06-18 or 2025-03-26, retain the returned Mcp-Session-Id and send it on later requests. It supports SSE, resource subscriptions and session deletion.

blackbox_read permits run, timeline, graph, integrity, comparison and finding reads; blackbox_write permits recording, triage and bookmarks. Content needs blackbox_content with read access, and erasure/deletion needs blackbox_manage with read access. Discover current permission-filtered tools with tools/list. Resources use blackbox://runs/{run_id}.

Reported events are claims with provenance. Chain verification does not prove semantic correctness, and simulations never prove that an action happened. Keep destructive operations tied to the user's requested scope.

Hosted Remote MCP Tools

Responses can call a public HTTPS MCP server when the key's MCP switch permits it. The request selects the server, allowed tools, credentials and approval behavior; approval is required by default. Follow the current Responses schema and its approval request/response items. Workspace Store connections retain their own account and method switches. Installing a skill does not enable a server or grant credentials. See Skills And Agents for package boundaries.

Private Engineering References

The public endpoint excludes backend and internal source documentation. Workspace access follows the authenticated actor and requires administrator access, checked on every read. The browser engineering reference uses the existing administrator session. A normal API key does not grant private engineering access. Never copy session cookies into an external MCP client.

Browse API and SDK documentation or open the Engineering tab there. Documentation maps are reference data, not execution authority.