MCP servers for DataMind Oda

A pushed MCP server is a server the company adds once for all its DataMind Oda users, so each person gets the tools of another service without adding the server themselves. You manage these servers in DataMind OS: open Admin > Oda and go to the MCP tab. The dialogs and their buttons are described on MCP servers and skills, and the user side is on Memory, skills and connectors.

Add a server

1. On the MCP tab, add the server: a hosted service with a Server address, or a program that runs on each user's computer with a Local command (stdio).
2. Fill in the values the server needs: Headers for a hosted service, Environment variables for a local program.
3. Choose the delivery, Managed or Install once, and the roles that receive the server. Both choices are explained below.
4. Save.

A company can keep up to 32 pushed servers. The count is of the servers still in the list, so removing one frees a slot; a save past the limit is refused: You can add up to 32 MCP servers.

The name Oda uses

Oda knows each pushed server by a short slug and shows it as org_ followed by that slug, for example org_google-drive.

• The server's name holds up to 80 characters. An empty name is refused: Enter a display name.
• The slug is made from the name. It uses 1 to 20 lowercase letters, digits, - or _, and starts with a letter or digit: Use 1 to 20 lowercase letters, digits, - or _, starting with a letter or digit. A name that has no Latin letters or digits gets a random slug instead.
• The slug is fixed once the server is added, and it is never given to another server, not even after the first one is removed. Reusing it is refused: An MCP server with this name already exists or existed before.

How a server connects

• A Server address must start with https://: Enter the full server address, starting with https://. An empty address is refused: Enter the server address.
• Plain http:// is accepted only for localhost and 127.0.0.1: Use an https:// address. Plain http:// is allowed only for localhost and 127.0.0.1.
• A user name and password inside the address is refused; send the value as a header instead: Remove the user name and password from the address and send them as a header instead.
• A server that runs as a program on each user's computer is started by its Local command (stdio): Enter the command to run. The command takes up to 64 arguments.
• A Server address takes a sign-in method: none, Headers, or OAuth. Header values are kept only with the Headers method: Headers are only sent when the sign-in method is Headers. A client ID is kept only with the OAuth method: A client ID applies only to the OAuth sign-in method.
• A local server takes no sign-in method; it gets its settings from environment variables: Local servers take their settings from environment variables, not a sign-in method.

Headers and environment variables

Values travel with the server: Headers are sent on every request, and Environment variables feed a local command. Up to 32 value rows are kept.

• Header names use letters, digits and dashes: Header names use letters, digits and - only. Environment variable names use letters, digits and _, and cannot start with a digit: Variable names use letters, digits and _, and cannot start with a digit.
• A name may appear only once: Each name may appear only once: Two header names that differ only in case count as the same name; environment variable names are compared as written.
• Some header names belong to Oda, which sets them on every request itself. Saving one of them is refused: Oda sets this header itself:
• Each row holds either a shared value or a value per user:
  • A shared value is stored once for everyone. It is kept encrypted and is never shown back to you.
  • Otherwise, each user enters their own value, kept on their computer.
• A shared row needs a value: Enter the shared value, or let each user enter their own: On an edit, leave the value empty to keep the stored one.
• If the DataMind server cannot store shared values, saving one is refused.

Who receives a server

• With no roles picked, everyone who uses Oda receives the server.
• With roles picked, a person receives the server when they hold any of those roles. Up to 64 roles can be picked.
• Only active roles count. Picking an inactive role is refused on save: Every role must be an active role.
• If all the picked roles later become inactive or are removed, the server reaches nobody. It does not fall back to everyone; pick active roles again to restore it.

Delivery, updates and removal

• Choose Managed or Install once when the server is added. The choice is fixed afterwards; to change it, remove the server and add it again.
• Managed: your edits reach every user who has the server, and removing the server takes it away from them.
• Install once: each user's Oda installs a copy once, and the user owns it. Your later edits do not reach an installed copy, and removing the server leaves the copies in place.
• Oda checks for company changes on its own every 10 minutes, so saved changes reach users without anyone doing anything.
• An edit marks the server as changed, and Oda restarts it, with the new settings, for the users who have it. Servers you did not change keep running as they are.
• A change that no longer finds the server is refused: MCP server not found.

Who can manage pushed servers

Managing them needs the DataMind Oda settings permissions; Manage DataMind Oda for your company shows where they are given.

Questions, answered

What does Oda call a server I push?

Oda shows it as org_ followed by its slug, for example org_google-drive. The slug is made from the server's name and cannot change after the server is added.

How many MCP servers can I push?

Up to 32. The check counts the servers still in the list, so removing one frees a slot. A save past the limit is refused: You can add up to 32 MCP servers.

Can I reuse the name of a server I removed?

No. The slug is never given to another server, even after the first one is removed: An MCP server with this name already exists or existed before. Give the new server a different name.

Where can a pushed server's address point?

Any host, as long as the address starts with https://. Plain http:// is accepted only for localhost and 127.0.0.1: Use an https:// address. Plain http:// is allowed only for localhost and 127.0.0.1. A user name and password inside the address is refused; send the value as a header instead.

Which header names does Oda keep for itself?

Some header names belong to Oda, which sets them on every request. Saving one of them is refused: Oda sets this header itself: Use a different header name.

Can two headers or variables share a name?

No: Each name may appear only once: Two header names that differ only in case count as the same name. Environment variable names are compared as written.

Do users keep a copy of a server I remove?

An Install once copy stays on the user's computer, because the user owns it. A Managed server is taken away from users when you remove it, or when their roles no longer give them the server.

Does editing a server restart anything?

Yes. Oda restarts a server whose settings changed, with the new settings, for the users who have it. Servers you did not change keep running as they are.

Can I change a shared value later?

Yes. On an edit, leave the value empty to keep the stored one, or type a new value to replace it. A shared row cannot be saved without a value: Enter the shared value, or let each user enter their own:

Do local servers need a sign-in method?

No. A local server takes its settings from environment variables: Local servers take their settings from environment variables, not a sign-in method. A sign-in method belongs to a Server address, and a client ID is kept only with the OAuth method: A client ID applies only to the OAuth sign-in method.