Integrate

Model Context Protocol

Jeden maintains bounded persistent MCP connections and exposes server tools, resources, prompts, notifications, and health through native commands.

Configuration

User servers load from ~/.jeden/mcp.json. Project servers load from <cwd>/.jeden/mcp.json. Both use the standard mcpServers shape.

.jeden/mcp.json
{
  "mcpServers": {
    "example": {
      "command": "/absolute/path/to/server",
      "args": ["--stdio"]
    }
  }
}

Operate servers

Interactive
/mcp
/mcp list
/mcp tools
/mcp resources
/mcp prompts
/mcp notifications
/mcp test
/mcp reload
/mcp reconnect

Tool naming

Generic MCP tools can list and call every configured server. Eligible tools may also be projected into the native registry as mcp__<server>__<tool>. Names remain unique and capability health reflects the current server connection.

Same policy

MCP does not bypass Jeden policy. A server tool is still subject to the active approval mode, hooks, capability health, and workspace contract.

Stay in the loop. Never miss out.

Subscribe to our newsletter and unlock Wisent insights.