An MCP server gives DataMind Oda the tools of another service in your chats. The MCP servers tab of Settings > Connectors is where servers you add yourself appear: add one, check that it connects, sign in when it asks, and remove it when you no longer need it.
Ready-made apps live on the Connectors tab instead (Connectors), and a connection can also arrive with an installed bundle (Plugins and MCP connections). What a connected server gives Oda in a chat is covered in MCP tools and resources for Oda.
The tab is part of the DataMind Oda desktop app and the VS Code extension; in the browser app it does not appear.
No MCP servers yet. Add one to use its tools in chats.https:/ / mcp. example. com/ mcp.Authorization header.Worth knowing:
http(s):/ / is treated as the Server address instead of a command.A server named "<name>" already exists.).https:/ /, and the field's hint says Streamable HTTP address. It may contain an access token; it is stored encrypted. Plain http:/ / is allowed only for localhost, 127. 0. 0. 1 and [::1] (Use an https:/ / address. Plain http:/ / is allowed only for localhost and 127. 0. 0. 1.). A user name or password inside the address is refused: Remove the user name and password from the address and send them as a header instead."<name>" is not a valid header name. Use letters, digits and dashes.), a name cannot be listed twice (The header "<name>" is listed twice.), and a name the app sets itself, such as Content-Type, cannot be changed (The header "Content-Type" is set by the app and cannot be changed.). Every name needs a value, and up to 32 headers are allowed.The command must be one line of text.). A local command runs as a program on this computer, outside Oda's usual command sandbox (Command sandboxing and approvals); add only programs you trust.Enter at most 64 arguments, each on one line.)."<name>" is not a valid variable name. Use letters, digits and underscores, starting with a letter.).Enter a timeout between 1 and 3600 seconds.). Left empty, the default applies, as the hint says: Leave empty for the default: 120 seconds for an address, 60 seconds for a local command.<name>) and choose Edit.Saved address <masked>. Leave empty to keep it., Saved value. Leave empty to keep it., Saved command <name>. Leave empty to keep it., <count> saved. Leave empty to keep them.Worth knowing:
Test connection connects once, reads the server's tools, and closes. It saves and changes nothing.
A good test answers Connected., with Connected. for one and Connected. for none; the dialog lists up to 30 of the tools. A failed test reads Could not connect: <message> and stays open, so you can fix the details and try again.
Some servers ask you to sign in before they give Oda their tools. While a server needs a sign-in, its row shows Sign in; while the browser step runs, it shows Finish in your browser….
You are signed in and You can close this tab and return to DataMind Oda.; if it cannot finish, it says Sign-in did not finish and Return to DataMind Oda for details, then try again. (The page is shown in English.)Signed in as <account>.Two kinds of server cannot sign in this way:
Only a server address can sign in; a local command cannot.Authorization value: This server sends its own Authorization header. Remove the header to sign in instead.The sign-in is renewed quietly while it stays valid. When it stops working, the server shows Sign-in needed with Sign in to use this server., and you sign in again.
<name> menu and choose Remove.Remove <name>? and Its tools will no longer be available in chats. You can add the server again later.Removing a server cancels a sign-in that is still running, deletes the server, and revokes its tokens where the sign-in server allows it. Add the server again whenever you need it.
<status>: <message>).https:/ / …abcd…12. A local command shows as Local command: <command> with its argument count (1 argument or <count> arguments).Addresses, headers and environment values are stored encrypted on this computer. The tab states its own promise: Connect MCP servers so DataMind Oda can use their tools in your chats.
The rest of Oda's record for a server holds only its name and settings, never the address, header or environment values.
A saved value is replaced, not shown: an address inside the app is always shortened, and error messages never echo a secret, because a known value is replaced with … and any address in a message is shortened the same way as in the row.
If secure storage is not available on this computer, Oda cannot save or read connection details and says so: Secure storage is not available on this computer, so connection details cannot be saved or read.
Other storage problems read:
The saved connection details could not be read. Restart the app, or edit the server and enter them again.The connection details could not be saved. Try again.The connection details for this server are missing. Edit the server and enter them again.connection lost; reconnecting when it starts retrying, and reconnected and re-synced tools when the server is back with its tool list refreshed.| Message | What it means | What to do |
|---|---|---|
The server refused the connection. | Nothing answered at the address. | Check that the server is running and that the address is right. |
The server address could not be found. | The address does not resolve. | Check the address for a typo. |
The server refused access (HTTP <status>). | The server answered but refused the request. | Check the address and your headers; if the server needs a sign-in, add its token as a header or choose Sign in where it is offered. |
The server has no MCP endpoint at this address (HTTP 404). | The address does not host an MCP endpoint. | Check that the address points at the server's MCP endpoint. |
The address does not accept MCP requests (HTTP 405). | The address is not the server's Streamable HTTP endpoint. | Use the server's Streamable HTTP address. |
The server did not answer within <seconds> seconds. | The server took too long to answer. | Try again; if it keeps happening, check the server. |
The command was not found. | The local command could not be started. | Check the command's name, or enter its full path. |
The server certificate is not trusted by this computer. | The server's certificate was not accepted. | Check the server's certificate; if you cannot fix it, ask your administrator. |
The server asked for authorization. | The server wants a sign-in token. | Add the token as an Authorization header, or choose Sign in if the server offers browser sign-in. |
Could not connect to the server: <detail> | The connection failed for another reason. | The text after the colon names the reason; fix it and try again. |
Could not complete the change: <message> | An action on the tab, such as saving or removing, did not go through. | Try the action again; if it keeps failing, contact your administrator with the message. |
Open Settings > Connectors, choose the MCP servers tab, and choose Add server. Give the server a name and its Streamable HTTP address (or a local command under Advanced), test the connection, and save.
Only on this computer: localhost, 127. and [::1]. Any other server needs an https:/ address.
In encrypted storage on this computer, and never in full anywhere in the interface: addresses are shortened, saved header and environment values are replaced, and error messages never echo a secret.
No. A rename alone does not restart the connection; changing the address, command, headers, environment values or timeout does. To retry a failed connection, choose Reconnect, save a change, or restart DataMind Oda.
Open Edit and leave the saved fields empty: each one says Leave empty to keep it. and keeps its stored value. Only the fields you fill in are replaced.
The default: 120 seconds for a server address, 60 seconds for a local command.
Its saved sign-in is missing or is no longer accepted. Choose Sign in on the row and finish the sign-in in your browser.
No. Browser sign-in is offered for servers with an address only; a local command cannot sign in. A server whose headers send their own Authorization value cannot use browser sign-in either.
If a working connection dropped and Oda could not bring it back after ten failed attempts, the tools are removed until DataMind Oda is reloaded or restarted. The server keeps its row, with a tool count of zero.
Nothing. It connects once, reads the server's tools, and closes; nothing is saved or registered. The server only starts after you save it.
The sign-in is cancelled, the server is deleted, and its tokens are revoked where the sign-in server allows it. Adding the server again starts fresh.