- Inside task containers — automatically injected via stdio transport. Every agent has access to these tools out of the box.
- External clients — connect over HTTP using a bearer token. Use from Claude Desktop, Codex CLI, or any MCP-compatible client.
How agents use these tools
The built-in MCP server gives agents workspace context they wouldn’t otherwise have. An agent working on a task can:- Check what else is happening — list tasks to avoid duplicating work or to understand the broader project state
- Spawn subtasks — create child tasks to parallelize work (the foundation of orchestrator mode)
- Coordinate with other agents — send prompts to running tasks and receive reports back
- Search for context — find past decisions, implementations, or debugging context across workspace conversations and task summaries
- Plan future work — create todos in the backlog for follow-up items
External client setup
To connect an external MCP client to your workspace:1
Open Settings
In Whim, go to Settings > Configuration > Whim MCP.
2
Copy the workspace MCP URL
3
Create a token
Click Create Token, copy it immediately, and store it securely. Whim only shows the full token once.
4
Configure your client
Use one of the examples below.
Client configuration examples
Claude Desktop / Claude Code (JSON)
Claude Desktop / Claude Code (JSON)
Codex CLI (~/.codex/config.toml)
Codex CLI (~/.codex/config.toml)
Generic HTTP client
Generic HTTP client
406 Not Acceptable when Accept headers are missing or incompatible.Tool reference
Task discovery
Task creation
Task lifecycle
Task organization
Configuration
Token management
Scope
Tokens are scoped to the workspace where they were created. Use a different
workspace’s URL and token to access another workspace.
Revocation
Revoke tokens from the Whim MCP settings page. Revoked tokens stop
working immediately.
Last-used tracking
Whim tracks when each token was last used, visible in the token management
UI.
Compatibility
Requires clients that can send a custom
Authorization header. Clients that
only support OAuth-based MCP auth will need a different connection path.
