DataMind Oda is built from plugins, and a bundle groups plugins together. You can extend it: a bundle can add new capabilities to Oda, and it can connect an MCP server so Oda can use another service's tools in your chats. This page covers installing an extension, approving what it runs, and checking that a connection works.
A bundle is a package folder on this computer that declares the plugins it adds. Ask Oda to install it, and point Oda at the folder:
Oda performs the installation and the bundle selection itself; do not install the package with package manager commands.
The Plugins page lists your app's plugins and bundles, each shown with the details its package declares. You can switch one plugin's row, or a whole bundle, on or off.
overridden and that setting wins.You can check what is loaded on this computer in Settings > Plugins; Built-in plugins covers that list.
An MCP server gives Oda the tools of another service. Ask Oda to set up the connection as part of a bundle; to connect tools to Oda in general, see Memory, skills and connectors.
To add and manage servers yourself, see MCP servers.
A switch, an install or a replaced package can report one of these states:
| State | What it means | What to do |
|---|---|---|
failed | The plugin could not load, and it needs diagnosis. | Keep the message it reports, and repair the same bundle instead of installing another copy of it. |
overridden | A higher-priority setting on this computer decides the plugin's state. | Change the setting that decides it, or leave it as it is. |
restart-required | The change is not live yet. | Restart DataMind Oda. Replacing an installed package always needs a restart before its new code is used. |
In a chat, ask Oda to install it and tell Oda where the bundle is on this computer. Oda performs the install itself and asks for your approval, because installing runs the bundle's plugin code.
The bundle's plugin code. Installing a bundle executes its plugin code on this computer, so Oda needs Full access or your approval. If the package wants to run build scripts, they are listed and must be approved separately. For how wider access is approved, see When Oda needs more access.
Some packages want to run their own build steps during an install. Oda does not run them on its own: it lists the scripts and waits, and they run only if you approve them. Approve only a bundle you trust.
Yes. Switch the plugin's own row and the rest of the bundle is untouched; only that plugin's state changes. Switching the bundle itself turns its plugins off or on together.
A higher-priority setting, such as a settings file on this computer, decides that plugin's state. That setting wins, so the switch cannot change it. Change the setting that decides it, or leave it as it is.
The new code is not loaded yet. Some changes are not live, and Oda reports restart-required until a restart loads them. Replacing an installed package always needs a restart before its new code is used.
The plugin could not load, and it needs to be fixed before it can load again. Keep the message it reports, and repair the same bundle instead of installing another copy of it.
Yes. A connection can bundle a server that answers at an HTTP address, or a local command that runs on this computer. Ask Oda to set the connection up for you.
Use it: ask Oda to call one of the server's tools. The tools a connection offers are named after the server it came from, and a working call shows that the connection is up.
On the MCP servers tab of Settings > Connectors: add, edit, test and remove servers there. See MCP servers; to connect tools to Oda in general, see Memory, skills and connectors.
The name, description and icon the plugin's package declares, read before the plugin runs. An icon may be SVG, PNG, JPEG or WebP up to 256 KiB and must stay inside the package's folder. When a package declares none of these, the card falls back to the package's name and description and to default artwork.