Give your agents tools with MCP servers
From reading documents to driving GitHub: how MCP servers work in OtoDock, and how to enable them for an agent safely.
5 min read
Agents get their abilities from MCP servers — the open Model Context Protocol standard. OtoDock ships first-party servers for files, documents, notifications, tasks, and memory, and a community catalog that keeps growing.
Enable a server for an agent
In the admin area, browse the MCP catalog and install what the agent needs; then enable the server on that agent. Tools are per-agent on purpose: your research agent doesn't need GitHub write access, and your dev agent doesn't need your CRM.
Scopes and security
Every server-side agent session runs inside a kernel sandbox with network isolation — an MCP server only reaches what it was explicitly granted. Credentials an MCP needs are encrypted at rest and injected per session, never written into the agent's filesystem.
The community catalog
Community MCPs live in the public community-mcps repository — browse what exists, and contribute your own when something is missing.
Put your agents to work
Self-host free up to 5 users — running in minutes.