Skip to main content

Community catalog

OtoDock has a growing community catalog — tools, ready-made agents, and skills you can install in a click from the dashboard. The integrations on the previous page are themselves curated community tools. The catalog is where everything beyond the always-present built-in tools comes from, plus anything new the community ships.

Install more tools​

Admins browse and install from Admin → MCP Servers → Browse Community — one click fetches and sets up the tool, and admin installs apply immediately. Some tools ask for a credential or a bit of configuration afterward (an API key, a server address).

Managers browse the same catalog from their agent's MCPs settings. When a manager asks for a tool that isn't installed yet, it goes to the admins as an install request. Once an admin approves it, OtoDock installs the tool and enables it for that agent. Agents can file the same requests from chat — see Using Tools.

For tools that are configured through instances (an SSH host, a metrics server), the approval dialog lets the admin pick which instance the requesting agent gets. When the only thing missing is an instance, the request waits as an amber "Needs instance" to-do instead of failing, and completes on its own the moment an instance covering the agent exists.

Install ready-made agents​

From the Agents page, choose Browse Community Agents to find ready-made agents that arrive with their tools, persona (agent.md), skills, apps and checks, and, where relevant, starter tasks and onboarding guides. The apps can be shared, with one copy the whole team uses, or personal, with a copy for every member.

When you install, the dialog shows what each app may do and what each check runs, and your consent there approves them, so they work from the very first chat. An admin's consent covers every member's copy. A creator's consent covers the shared apps and the creator's own copy, and every other member approves their own.

One click installs the agent and sets up everything it needs. Anything that still needs an admin, such as a tool instance or a skill package, becomes a clear to-do instead of a failure. Afterwards it's a normal agent you can reshape freely (see Creating an Agent).

Templates follow new versions​

When the catalog has a newer version of a template you installed, the agent's managers see an Update on the template's card and on the agent's Configuration tab. An update brings in the new version of every part of the template you haven't changed, and adds anything new. Anything a manager edited is kept as it is, with the new version stored beside it and a Take the new version button to switch to it. A task, check or app that a manager removed or switched off stays that way, and the update's report lists it as left out. An update also turns on the core tools the platform gained since you installed the agent. An agent that was built by asking another agent has no template, so it never updates.

Keeping tools current​

Community tools can update themselves automatically on a weekly schedule, so improvements land without manual work. A single platform-wide setting controls this (Admin → Setup, on by default). To pick up a new version sooner, an admin opens Admin → MCP Servers, clicks Check Updates, and presses Update on the tool's row.

Two safeguards apply whenever a tool is installed or updated:

  • A tool whose source changed waits for an admin. If the catalog now fetches a tool from a different package, image or repository than the one you installed, it doesn't update on its own until an admin accepts the new source under Admin → MCP Servers.
  • Python tools install from prebuilt packages only, unless the tool's catalog entry allows building a named dependency from source. Any other dependency with no prebuilt package for your server fails the install with a message naming it, and an update that fails rolls back to the version you had.
note

The catalog grows over time, so the best place to see what's available is the dashboard on your own install — admins browse it under MCP Servers, and managers browse it from their agent's MCPs settings.

Next steps​