PLATE DOCMCP

Give the agent your own tools

The Model Context Protocol is how an agent gets tools it was not shipped with. Point Osmium at an MCP server and its capabilities become things the agent can call while it works on your code.

Per workspace, off by default

MCP servers are configured per workspace, so a client project does not inherit your internal tooling. Nothing is enabled until you enable it.

What people wire up

Database introspection, issue trackers, internal HTTP APIs, documentation search. Anything with an MCP server becomes available without waiting for us to build an integration.

It composes with local models

Tool calling works with local models that support it — most of the curated coding models do. Check the tool-calling row on any model page.

What it does not do

Tool calling depends on the model. A few local models, mostly the vision and older uncensored ones, have no tool support in their template.