Model Context Protocol (MCP)

ToolsAPI exposes a remote MCP endpoint at /mcp. MCP clients use the same owner-bound API-key model as the rest of ToolsAPI; MCP does not create a second account or credential store.

Authentication

Create or update a personal API key from My API Keys and grant it the mcp.connect scope. Send that secret as a bearer token:

Authorization: Bearer YOUR_TOOLS_API_KEY

X-Api-Key is accepted as a compatibility fallback for server-side clients. Do not place either credential in browser JavaScript, URLs, logs, screenshots, prompts or public configuration.

The mcp.connect scope only opens the MCP boundary. Every domain tool may require additional scopes and ownership checks. A client can discover only tools that its API key can actually invoke.

Endpoint and protocol

Canonical endpoint:

https://YOUR_TOOLS_HOST/mcp

The primary protocol revision is 2026-07-28, using the stateless MCP HTTP model. Current requests send MCP-Protocol-Version and Mcp-Method; calls to named tools also send Mcp-Name. The endpoint also keeps bounded stateless compatibility for 2025-11-25 and 2025-06-18 clients.

The server does not issue or depend on Mcp-Session-Id for this integration.

Available foundation tool

The first foundation release intentionally exposes only one harmless proof tool:

toolsapi.connection_status - confirms authenticated MCP connectivity and returns safe connection metadata. It is read-only, idempotent and closed-world.

WordPress, Fact Verify and automation tools are tracked separately so their domain scopes and ownership contracts can be reviewed independently.

Current-protocol example

POST /mcp
Authorization: Bearer YOUR_TOOLS_API_KEY
Content-Type: application/json
MCP-Protocol-Version: 2026-07-28
Mcp-Method: tools/call
Mcp-Name: toolsapi.connection_status

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "toolsapi.connection_status",
    "arguments": {},
    "_meta": {
      "io.modelcontextprotocol/clientInfo": {
        "name": "example-client",
        "version": "1.0"
      }
    }
  }
}

User and administrator views

/me/mcp shows the endpoint, supported protocol revisions, the signed-in user's MCP-capable key names/IDs and the tools visible to those keys. Secret key values are never rendered there.
/admin/mcp shows the registered tool catalog and recent structured MCP audit records. It is administrator-only.
/services provides service discovery without adding MCP to the main navbar.

Audit and diagnostics

Meaningful tool calls are written to the dedicated MCP audit log with safe actor, tool, protocol/client, result and correlation metadata. Tokens and credential-like context are redacted.

Unexpected operational tool failures are also logged through the normal ToolsAPI operational diagnostics path so they remain visible in #toolsapi independently of audit persistence. Expected authentication, protocol and validation rejections are returned to the client without generating operational-alert noise.

Cross-origin requests

Remote server-to-server MCP clients normally do not send a browser Origin header. If an Origin header is present in the foundation implementation, it must match the ToolsAPI request host; malformed or cross-host browser origins are rejected. Managed OAuth/client-origin support is tracked separately from the core transport.

Tornevall Networks