MCP Servers

Model Context Protocol (MCP) servers enable Large Language Model (LLM) agents to safely interact with IXO ecosystem services through specialized server interfaces.

Secure Access

Controlled access to IXO services with robust security mechanisms

Standardized APIs

Consistent API patterns across all MCP server types

Architecture Overview

MCP servers act as secure gateways between AI agents and IXO services:

Blockchain

Access on-chain data and transactions via MultiClient SDK

Matrix

Secure communication within decentralized messaging infrastructure

Applications

Integration with user-facing applications like IXO Portal

Security Model

Each MCP server implements three core security components:

Decentralized Identity (DID)

Secure, blockchain-verified agent identities

UCAN Tokens

User Controlled Authorization Network credentials for authentication

Capability Based Access Control

Fine-grained permissions for resource access

Available Servers

Access IXO blockchain functionality:

Query on-chain data and entity states
Submit authorized transactions
Monitor blockchain events
Access MultiClient SDK features

const client = new BlockchainMCP({
  endpoint: "https://mcp.ixo.earth/blockchain"
});

// Query entity state
const entity = await client.getEntity(entityId);

Documentation MCP server

These docs run their own MCP server, so an agent can search and read them as tools instead of scraping HTML. It is public, needs no authentication, and is rate limited to 120 requests per minute per IP.

Property	Value
Endpoint	`https://docs.ixo.world/mcp`
Transport	Streamable HTTP, stateless (JSON-RPC 2.0 over `POST`)
Server card	`https://docs.ixo.world/.well-known/mcp.json`
Registry document	`https://docs.ixo.world/mcp/server.json`
Tools	`search_docs`, `read_page`

search_docs

Ranked full-text search across every documentation page and API endpoint.

query (string, required) — natural-language or keyword query
limit (integer, 1–20, default 8) — how many pages to return

Each result carries the page title, canonical URL, Markdown URL, description, and a snippet.

read_page

Returns a page as Markdown.

url (string) — a full docs URL, or
path (string) — a site path such as /build-an-oracle/quickstart

Connect

{
  "mcpServers": {
    "ixo-docs": {
      "type": "http",
      "url": "https://docs.ixo.world/mcp"
    }
  }
}

A GET on the endpoint returns 405 — the transport reserves GET for server-initiated streams, which a stateless server does not offer — with a JSON body naming the protocol version, the tools, and the server card. Read the server card first when you want the tool schemas before opening a connection.

Tip

Not using MCP? Every page serves Markdown at <url>.md or on Accept: text/markdown, /llms.txt indexes the whole site, and /llms-full.txt returns the entire corpus in one request.

Integration Guides

Blockchain Integration

Connect AI agents to the IXO blockchain

Matrix Integration

Enable secure agent communication

Personal Agent ADK

Access Impact Oracle services

Client Integration

Integrate with IXO applications

Tip

For service auth and endpoint ownership, use the Authentication Matrix and Networks and Endpoints.