MCP Servers
Extend the assistant with external tools via the Model Context Protocol.
Beyond its built-in capabilities, MeghaOS can connect to MCP (Model Context Protocol) servers — external tool providers that expose their own capabilities. Once connected, an MCP server's tools appear to the assistant just like any built-in tool and can be used in chat and workflows.
How it fits in
MeghaOS launches the MCP servers you configure, discovers the tools each provides, and folds them into the same pipeline as everything else — so MCP tools are ranked, selected, and run exactly like native capabilities.
Connecting a server
Add MCP servers in Settings → Integrations → MCP. For each server you provide how to start it and any environment it needs; MeghaOS connects on start and registers its tools. No servers are connected out of the box.
Why use MCP
Connect any MCP-compatible server — databases, SaaS APIs, dev tools — to give MeghaOS new abilities without building anything.
MCP tools are ranked, selected, and executed just like native tools, and can drive generated UIs and workflows.
MCP tools flow through the same path as built-in capabilities, so everything in Capabilities & Tools — relevance ranking, safety gating, workflow participation — applies to them too.