An MCP server gives DataMind Oda the tools of another service, such as a task tracker or a code repository, and Oda can use them while it works in your chats. You add and manage your own servers on the MCP servers tab of Settings > Connectors.
The catalogue apps (such as ClickUp and GitHub) live on the Connectors tab beside it (Connectors). What a connected server gives Oda in a chat is covered in MCP tools and resources for Oda, a broken connection in MCP servers: recovery and troubleshooting, and connections that arrive with an installed bundle in Plugins and MCP connections.
https:/. The address may carry an access token, and it is stored encrypted.Authorization header.You can add at most 64 servers.
A server started by a Local command (stdio) runs as a program on this computer, outside Oda's usual command sandbox (Command sandboxing and approvals). Add only programs you trust.
A server named "<name>" already exists.https:/ is required. Plain http:/ works only for localhost, 127. and [::1]: Use an https:/ 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.Content-Type, cannot be changed: The header "<name>" is set by the app and cannot be changed.The command must be one line of text.Enter at most 64 arguments, each on one line."<name>" is not a valid variable name.Enter a timeout between 1 and 3600 seconds. Left empty, the default applies: 120 seconds for a server address and 60 seconds for a local command.<name> menu and choose Edit.Saved address <masked>. and Saved value.Test connection connects once, reads the server's tools and closes. It saves and changes nothing.
Connected., with Connected. for one and Connected. for none.The server refused the connection.The server address could not be found.The server refused access (HTTP <status>).The server asked for authorization.The server has no MCP endpoint at this address (HTTP 404).The address does not accept MCP requests (HTTP 405).The server did not answer within <seconds> seconds.The command was not found.The server certificate is not trusted by this computer.Could not connect to the server: <detail>Some servers ask for a browser sign-in before they give Oda their tools. While a server needs one, 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 reads Sign-in did not finish and Return to DataMind Oda for details, then try again. The page is shown in English only.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.The sign-in renews quietly while it stays valid. When it stops working, the row shows Sign-in needed with Sign in to use this server., and you sign in again from the row.
The switch beside a server reads Use <name>.
<name> menu and choose Remove.Remove <name>? and Its tools will no longer be available in chats.Removing a server cancels a sign-in that is still running, deletes the server and its stored details, and revokes its tokens where the sign-in server allows it.
<status>: <message>).https:/. A local command shows its name and how many arguments it has (1 argument or <count> arguments).Addresses, headers, commands, arguments and environment values are stored encrypted on this computer. The tab itself says: Connect MCP servers so DataMind Oda can use their tools in your chats.
…, and an unknown error's address is shortened the same way).Secure storage is not available on this computer, so connection details cannot be saved or read.The saved connection details could not be read.The connection details could not be saved.The connection details for this server are missing.No. The MCP servers list appears in the desktop app and the VS Code extension, not in the browser app. Without a desktop connection, a saved server cannot start; it stays at Connecting….
At most 64. When the list is full, adding another is refused: You can add at most 64 MCP servers.
Names run from 1 to 64 characters, with no leading or trailing spaces, and two servers cannot share one even with different capitalisation: A server named "<name>" already exists. Choose another name.
Credentials inside an address are refused, so a password never sits in the address string: Remove the user name and password from the address and send them as a header instead. Add the value as a header in the same dialog.
The app sets some header names itself, and those cannot be changed: The header "<name>" is set by the app and cannot be changed. Remove that row; the app supplies the header. Other header rules: names use letters, digits and dashes, one row per name, and up to 32 headers.
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. A server that needs stored details cannot connect until secure storage works.
That page answers only a request that belongs to a running sign-in; anything else gets Not found. Start the sign-in again from the server's row and finish it on the fresh page.
Connected: the server is up and its tools are available. Connecting…: Oda is still connecting. Not connected: the last connection could not be made. Turned off: you switched the server off. Sign-in needed: its saved sign-in is missing or no longer accepted. A reason follows the status when there is one.
Yes. The switch reads Use <name>; turning it off takes the server's tools out of your chats and keeps the server in the list. Turn it on again to connect it back.
So a token inside an address is never shown in full: the scheme and host stay, the last part of the address keeps only its first four and last two characters, as in https:/, and any query, fragment or credentials are never shown. Messages about a server are shortened the same way.