Platform MCP quickstart

Yodu's Platform MCP server uses stateless Streamable HTTP at:

https://app.yodu.ai/api/mcp

1. Create a client-specific key

Open Settings → MCP & API, create a key for the intended client, and copy it once. A key is bound to the active workspace and user.

2. Add the server

For Claude Code:

claude mcp add --transport http yodu https://app.yodu.ai/api/mcp \
  --header "Authorization: Bearer YOUR_YODU_API_KEY"

For JSON-based clients:

{
	"mcpServers": {
		"yodu": {
			"url": "https://app.yodu.ai/api/mcp",
			"headers": {
				"Authorization": "Bearer YOUR_YODU_API_KEY"
			}
		}
	}
}

See Client setup for client-specific locations and a generic connection checklist.

3. Start read-only

Ask the client to list the Yodu tools, then call get_workspace, get_workspace_overview, list_agents, and list_tasks. Use read_task for one selected item before changing board state; it includes discussion and safe linked approval/file metadata, but cannot decide an approval or read a file body.

Confirm the workspace name before any mutation. If it is wrong, revoke the key, switch workspace in Yodu, and create a new key.

4. Invoke writes deliberately

Use create_task or create_memory for a first bounded write. Existing tasks can be changed with update_task, ordered with move_task, and discussed with comment_task; those operations do not approve linked external actions. Employee configuration requires an owner or admin. Credential tools are guarded by secrets:write, are write-only, and never return the stored value. The current settings screen creates keys with all three scopes, so client-specific keys, current role checks, and deliberate tool approval remain important boundaries.

Review the complete Platform MCP tools and Scopes and security pages before using configuration or secret tools.