Give every AI employee the right tools. Nothing more.
Connect the apps your business already uses, add private MCP servers, and decide what each AI employee can read, draft, send, or change. Yodu keeps the account, employee, task, and autonomy rule in one place.
business app toolkits available through Composio
catalog, connections, access, MCP, and skills
tool and skill access with a visible autonomy mode
custom MCP endpoints can be verified and re-tested
Connect once. Grant access deliberately.
A connected account belongs to the workspace. Access belongs to the employee. That distinction lets one team share the same systems without handing every credential and action to every role.
Connect an account
Authorize Gmail, GitHub, HubSpot, Stripe, Calendar, or another app from the catalog. Yodu stores a redacted connection reference, not a secret in the chat.
Choose the employee
Grant the app or skill to one AI employee, several employees, or the workspace. Every grant can be reviewed and revoked.
Set the autonomy level
Keep work draft-only, require approval for external actions, or allow bounded autonomous work when the process has earned it.
From inboxes and calendars to code and billing.
Search the live catalog by job, compare available actions, and connect the account that belongs to the workspace. Popular starting points include Gmail, Google Calendar, GitHub, HubSpot, Stripe, Notion, Shopify, Zendesk, and Resend.
Catalog availability and individual actions come from the connected provider and can change over time. Yodu shows the current toolkit before you grant access.
Bring any HTTPS MCP server into the same workspace.
Use custom MCP when the work depends on an internal API, a private data service, or a specialist product that is not in the app catalog. Add the endpoint, attach an optional auth header, verify the handshake, and then grant access like any other tool.
Add the HTTPS endpoint and a clear name.
Store an optional header value as an encrypted workspace secret.
Run a real MCP handshake and check the reported protocol health.
Give only the employees who need it access to its tools.
The same app can behave differently for different roles.
A research employee may only read. A sales employee may draft. A finance employee may need approval before a refund. Yodu keeps those decisions visible next to each grant.
Draft only
Read context and prepare output without taking an external action.
Approval required
Pause before sending, publishing, spending, or changing a source of truth.
Autonomous
Run a bounded, reviewed workflow without asking on every safe step.
Revoked
Remove access immediately while preserving the grant history.
Connect employees to tools — or connect your own AI client to Yodu.
MCP is a protocol, not one universal permission. Yodu keeps the direction, credential, workspace, and employee grant visible so each connection has a clear boundary.
Platform MCP
Claude Code, Claude Desktop, Cursor, or another external client operates one Yodu workspace through 53 curated tools and a scoped API key.
Employee MCP usage
A Yodu employee calls an approved external server while completing assigned work, subject to its tool grant and autonomy policy.
Custom MCP entries
The workspace registers and verifies a private HTTPS MCP server, stores its authorization safely, and chooses which employees receive access.
Tools provide actions. Skills provide judgment.
Install curated skills for research, communication, content, CRM, engineering, finance, legal, hiring, analytics, and orchestration. A skill explains how to approach the job; a tool gives the employee somewhere to act.
Choose the model separately from the tools.
Configure OpenAI, Anthropic, OpenRouter, or a supported Claude subscription token at workspace level. Then choose a model for an individual AI employee and let Yodu apply the change to the running workspace.
Tools and MCP questions
Connect the first tool your AI team actually needs.
Start with one account, one employee, and one useful task. Add access only when the work proves it needs more.