Platform MCP tools

Complete reference for the 53 tools exposed by Yodu's workspace-scoped Platform MCP server.

The Platform MCP server exposes exactly 53 curated tools. Every tool derives the workspace from the verified API key; no tool accepts an organization ID.

Read workspace state

Requires workspace:read and current workspace membership.

Tool	Purpose
`get_workspace`	Return the workspace identity bound to the connection
`get_workspace_overview`	Summarize employees, work, and needs-attention activity for up to 90 days
`get_workspace_settings`	Read model routing and runtime resource limits (owner or admin)
`list_agents`	List workspace employees, status, runtime identity, and channel
`list_agent_configs`	List one employee's bounded, versioned operating-document bodies (owner or admin)
`list_models`	List model references runnable in the workspace (owner or admin)
`get_agent_skills`	Read one employee's defaults, overrides, and effective skill loadout (owner or admin)
`list_connected_tools`	List safe connected-app metadata, grants, and cloud-coding state for one employee (owner/admin)
`list_agent_files`	List bounded, versioned custom-file metadata; content is never returned (owner or admin)
`list_secrets`	List workspace- and employee-scoped secret names and metadata, never their values
`list_role_templates`	List role templates available when creating an employee
`list_memory`	List shared memory, or one employee's local memory with owner/admin access
`read_memory`	Read shared memory or, with owner/admin access, an employee-local document by ID
`list_tasks`	List work with optional employee, status, priority, label, and search filters
`read_task`	Read one task with comments, approval summaries, evidence-file metadata, and activity
`get_runtime_health`	Read an allowlisted runtime health summary and successful file-sync time
`get_runtime_state`	Read safe current connection, container, queue, backup, and sync state without host internals
`get_runtime_command_status`	Read one org-scoped command's status and retry timing without payloads, errors, or worker details
`list_custom_mcp_servers`	List the workspace's custom MCP servers with header names only, never values (owner or admin)
`list_scheduled_jobs`	List scheduled jobs and run status; raw provider error text is never returned

Create work and context

Requires workspace:write and current workspace membership.

Tool	Purpose
`create_memory`	Create shared or owner/admin employee-local memory in Markdown
`update_memory`	Update shared or owner/admin employee-local memory
`create_task`	Add a task to the board and dispatch the assignment workflow
`update_task`	Update task content, priority, due date, link, assignee, or status and wake the employee when needed
`move_task`	Move or reorder a board task; status transitions wake the assignee
`comment_task`	Add an authenticated user comment or reply and wake the task's employee

Configure employees

Requires workspace:write and an owner or admin role.

Tool	Purpose
`create_agent`	Create a recruitment draft from a role template
`provision_agent`	Provision a drafted employee into the managed runtime
`repair_workspace_runtime`	Force-rebuild the workspace runtime from Yodu's saved config (safety backup first); disruptive while the stack restarts
`activate_memory`	Publish a sourced memory draft as live runtime context
`set_memory_status`	Move memory to draft, superseded, or archived without deleting history
`set_workspace_model_routing`	Set primary and cross-provider fallback models
`set_workspace_runtime_resources`	Set gateway memory/CPU limits
`set_agent_autonomy`	Set an employee's overall permission mode (how strictly the approval gate applies). The fully ungated mode is intentionally not settable via API. Per-tool switches live in `set_agent_tool_access`
`write_agent_config`	Write any of the seven versioned employee operating-document kinds
`set_agent_model`	Select an available workspace model for an employee
`set_agent_role`	Reassign an employee to a different workspace role (by roleId)
`set_agent_skills`	Add or remove skill overrides relative to the employee's role baseline
`set_agent_cloud_coding`	Enable or disable Claude Code or Codex for one employee; disabling cancels that provider's live sessions
`set_agent_tool_access`	Enable or disable one connected app or custom MCP server for one employee
`create_scheduled_job`	Create a recurring job that delivers a prompt to an employee on a cron schedule (evaluated in the job's timezone)
`update_scheduled_job`	Update a scheduled job's schedule, timezone, prompt, assignment, or status (the next run is recomputed on change)
`delete_scheduled_job`	Delete a scheduled job by ID
`run_scheduled_job`	Run a scheduled job immediately without changing its cadence
`write_agent_file`	Provision a safe custom file beneath an employee's `skills/` or `scripts/` path

The scheduler evaluates every cron expression against the job's timezone, an IANA name such as America/New_York. A missing or invalid timezone falls back to UTC. Changing a job's cron expression or timezone through create_scheduled_job or update_scheduled_job recomputes the next run immediately, so the schedule matches the declared wall clock from the first fire.

Write protected configuration

Requires secrets:write and an owner or admin role. Values are encrypted and never returned by a tool response.

Tool	Purpose
`add_custom_mcp_server`	Register an HTTPS MCP server with optional encrypted request headers
`remove_custom_mcp_server`	Remove a custom MCP server and its encrypted headers, then update every agent's runtime
`set_model_provider_key`	Store supported model-provider access for the workspace
`connect_cloud_agent`	Connect a Claude Code routine (from claude.ai/code/routines) so employees can delegate coding tasks to cloud sessions; the trigger token is encrypted and write-only
`set_workspace_secret`	Store a named workspace-wide or employee-scoped tool secret

Cloud coding agents

Tool	Purpose	Requires
`connect_cloud_agent`	Connect a Claude Code routine; the trigger token is encrypted, write-only	`secrets:write`, owner or admin
`connect_cloud_coding_repo`	Connect a GitHub repo for interactive (sidecar) coding — no routine, no token; the session uses the workspace's Claude subscription	`secrets:write`, owner or admin
`list_cloud_agent_connections`	List connected cloud coding agents (id, label, repo, trigger id, status); tokens are never included	`workspace:read`
`get_cloud_agent_setup_guide`	Return the canonical routine prompt template and the numbered claude.ai setup steps (plan, GitHub, routine, Environment, API trigger); read-only	`workspace:read`

Deliberate exclusions

There is no tool to read a stored secret value, select a different workspace, manage billing, impersonate a user, change members, delete the workspace, decide an approval, create an OAuth app connection, or invoke the raw runtime bootstrap. read_task returns only an allowlisted task DTO with approval summaries and evidence-file metadata; raw evidence JSON, activity data, and attachment properties are excluded. list_agent_files returns metadata only, never file bodies. Runtime health and scheduled-run responses omit arbitrary diagnostic payloads and raw provider error text. Destructive reach is limited to configuration entries the same connection created: a custom MCP server registration (remove_custom_mcp_server) and a scheduled job (delete_scheduled_job); employee and workspace deletion stay in the app. Workspace repair is exposed through repair_workspace_runtime (owner/admin only, safety backup first); the underlying bootstrap fetch and container lifecycle stay internal. list_secrets deliberately returns names and safe metadata so clients can detect existing configuration before a rotation; it never returns credential material. Platform MCP is a curated operator surface, not a mirror of Yodu's private application API.