Connect an agent
Register the Jio bridge with an MCP-capable client and validate the capabilities it receives.
The agent remains responsible for reasoning and tool selection. Jio appears to it as an MCP server whose tools operate against one remote workspace.
Connection model
local agent → local Jio bridge → authenticated connection → remote workspaceThe local bridge should hold only the connection state needed to reach the workspace. Project files, build tools, and command execution stay remote.
Register the MCP server
For Codex, use Jio's conflict-safe project installer after the CLI path succeeds:
jio mcp install --project . --config .jio/jio.toml \
--identity .jio/identity.json --jsonClient-specific configuration
Other MCP clients use different configuration files and process-launch conventions. Translate the fields below to your client's documented stdio-server format.
{
"mcpServers": {
"jio": {
"command": "/absolute/path/to/jio",
"args": [
"mcp",
"--config",
"/absolute/path/to/project/.jio/jio.toml",
"--identity",
"/absolute/path/to/project/.jio/identity.json"
]
}
}
}Use absolute paths because editor and desktop clients may launch with a different working directory or PATH from your terminal. The policy selects the remote endpoint, workspace, and trust mode; the identity authenticates the local client. Do not place secret values in the client configuration.
Check capabilities
Plan
Confirm that the client lists Jio, then call jio_plan and review the reported environment, trust mode, egress, and TTL without allocating compute.
Start
Call jio_session_start explicitly after reviewing the plan. Tool discovery and bridge startup do not allocate a worker.
Read
Ask the agent to list the workspace root and inspect a known file.
Write
Create and update a disposable file, then confirm the change exists on the remote machine.
Execute
Run a harmless command and verify working directory, output, and exit status.
Reject
Attempt an operation that policy forbids and confirm the agent receives a clear denial.
Keep the connection narrow
Do not mount your home directory or forward broad local shell access as a shortcut. If the agent needs a file, materialize it in the remote workspace through an explicit workflow.
See the full MCP integration, review MCP tool groups, or use troubleshooting when discovery fails.