🔌

MCP Protocol Integration

Shulam runs a native MCP server. Tool discovery, compliance-gated access, and trust scoring for every MCP client in your network.

Technical Note

Shulam exposes a fully compliant Model Context Protocol (MCP) server. Any MCP-compatible client — Claude Desktop, Cursor, custom agents — can connect directly and discover available tools, resources, and prompts. Trust scores and compliance gates are enforced at the protocol level.

What it does

✓Native MCP server support — Shulam is an MCP server out of the box.
✓Tool discovery lets MCP clients find and invoke trust-scored tools automatically.
✓Compliance-gated tool access ensures agents only use tools they are authorized for.
✓Trust-scored MCP clients — every connecting client gets a trust score based on behavior.

How it works

1
Point your MCP client at Shulam
Add the Shulam MCP server URL to your client configuration. Authentication uses your API key and AAIN.
2
Discover tools and resources
Your client automatically discovers available tools, resources, and prompts. Compliance gates filter what each agent can see.
3
Invoke with trust
Every tool invocation is trust-scored and logged. BARNABAS handles MCP auth while PHILIP routes requests to the right soul.

Which souls use it

BARNABAS

MCP Auth

Authenticates MCP clients and manages tool access permissions.

PHILIP

Routing

Routes MCP requests to the appropriate soul based on tool type and trust level.

Technical details

Protocol

Model Context Protocol (MCP) — JSON-RPC 2.0 over stdio or HTTP+SSE

Authentication

API key + AAIN (Autonomous Agent Identification Number) per client

Capabilities

Tools, resources, prompts, and sampling — with compliance gates on each

Compatible clients

Claude Desktop, Cursor, VS Code + Continue, custom MCP clients, and any MCP-compatible agent

Ready to connect via MCP?

Point your MCP client at Shulam and start discovering trust-scored tools.

Get started