Workspace to the SDK as an in-process MCP server, so every file and shell operation the agent runs is routed through Mirage instead of the host filesystem.
This is distinct from Claude Code, which points the claude CLI at a FUSE mountpoint. Use this SDK integration when you build your own agent with claude_agent_sdk.query() and want Mirage tools rather than the built-in file tools.
Install
Usage
build_options wires a workspace into a ready-to-use ClaudeAgentOptions: it registers the Mirage MCP server, restricts the agent to Mirage’s tools, and injects a system prompt describing the mounted paths.
Composing with other MCP servers
UseMirageServer directly to combine Mirage with other servers: