Skip to main content
The Model Context Protocol (MCP) is an open standard for sharing tools between AI systems. AFK supports both exposing your tools via an MCP server and consuming tools from external MCP servers.

Architecture

Expose tools via MCP server

Make your AFK tools available to any MCP-compatible client:
1

Define your tools

2

Create the MCP server

3

Start serving

Consume tools from external MCP servers

Discover and use tools from any MCP server:
1

Connect to an MCP server

2

Discover available tools

3

Attach to an agent

MCP tools are transparent. Once attached to an agent, MCP tools behave exactly like local tools — same validation, same policy gates, same telemetry. The agent doesn’t know (or care) whether a tool is local or remote.

Security

Require auth tokens for all MCP connections:
Configure allowed origins for browser-based clients:
Apply policy rules to MCP-exposed tools:
Limit request rates per client:
Always authenticate MCP servers in production. An unauthenticated server exposes your tools to anyone who can reach the endpoint.

MCP server vs A2A

Next steps

A2A Protocol

Share full agents across systems.

Security Model

Full security architecture.