Skip to main content
Model Context Protocol (MCP) is an open standard that lets AI agents discover and call external tools through a lightweight JSON-RPC interface. MIRA implements the MCP client side — any MCP-compatible server can expose tools that both reasoning engines can invoke automatically.

​
Why MCP matters

Without MCP, every new tool requires a custom integration. With MCP, any tool that speaks the protocol is immediately available to MIRA:
  • No custom code — add a server URL or command, and the tools appear automatically
  • Namespaced — each server’s tools are prefixed to avoid collisions
  • Safe — MIRA prompts you before executing any tool the first time

​
How it works

┌─────────────┐      JSON-RPC 2.0        ┌─────────────────────┐
│   MIRA NAE  │ ─── list_tools ────────► │   MCP Server        │
│   or RLM    │ ◄── tool definitions ─── │  (stdio or SSE)     │
│             │ ─── call_tool ─────────► │                     │
│             │ ◄── tool result ──────── │                     │
└─────────────┘                          └─────────────────────┘
  1. MIRA connects to the server and calls list_tools to discover available tools.
  2. Tool definitions (name, description, JSON schema for inputs) are injected into the engine’s context.
  3. When the engine decides to use a tool it calls call_tool with validated arguments.
  4. The server executes the tool and returns the result as text or structured data.

​
Transport types

MIRA supports two MCP transports:
TransportDescriptionBest for
stdioMCP server runs as a subprocess; MIRA communicates via stdin/stdoutLocal CLI tools, scripts
SSEMCP server runs as an HTTP server; MIRA connects via Server-Sent EventsRemote APIs, shared team servers

​
MCP tool namespacing

Tools are prefixed with the server name to prevent collisions: 
my-server/search_web
my-server/read_file
another-server/query_db
The engine sees the full namespaced name and uses it when calling the tool.

​
Next steps

Add a stdio server

Connect a local CLI-based MCP server

Add an SSE server

Connect a remote HTTP-based MCP server
Edit this page — Open a pull request