Search documentation

Search guides, connectors and tools

MCP servers

MCP, the Model Context Protocol, is an open standard for connecting AI to software. Many services offer an MCP server, and so can your own internal tools. Tunori can connect to any MCP server that is reachable on the internet: its tools are discovered when you connect it and become tools your agents can use, like those of any other integration.

Connecting an MCP server needs the Admin role.

Servers from the directory

You do not need to know a server's address. Add Integration also lists servers from a curated directory of popular MCP servers, in the same list as the other connectors and with their own logos. Pick one like any other connector:

  • Some servers run in several regions. Choose yours under Region.
  • Some are hosted per customer. Enter the address of your own instance under Your server URL; the form may link to where to find it.
  • Most servers send you to approve access on their own sign-in page and then bring you back to Tunori. The form explains what will happen under How connecting works.

Some servers only accept apps that you register with them yourself. The form then says so, links to the provider's Setup guide, and asks for your app's details: register the Redirect URI shown in the form with the provider, then enter the Client ID and, if the app has one, the Client secret. For other directory servers that send you to sign in, you can still use an app of your own under Advanced.

Connecting any other server

Choose MCP Server in Add Integration, enter the Server URL, and choose how Tunori signs in under Authentication:

  • Detect automatically: the default. Tunori connects without signing in first and switches to OAuth when the server asks for it. Use it when you are not sure what the server expects.
  • Sign in with OAuth: you approve access on the server's own sign-in page and are brought back.
  • OAuth with your own app: for servers that only accept apps registered with them by hand. Create an OAuth app with the provider, register the Redirect URI shown in the form, and enter the app's Client ID (and Client secret, if it has one).
  • Bearer token / API key: for servers that hand out a fixed token. Paste it into Token; it is sent with every request.
  • No authentication: for servers with open access.

Except for automatic detection, the method you choose is the one that is used. If it does not fit the server, for example because the server asks for a sign-in although you chose no authentication, nothing is connected and the form tells you which method to choose instead.

Only servers on the public internet can be connected, not addresses on your own computer or private network.

After connecting

The integrations list shows how each MCP server signs in: OAuth, OAuth (your app), Token or No authentication.

An agent only gets the server's tools that you switch on in its settings, where you can also require approval for each of them. Because tools come from the server, they are not listed in this documentation; you see them once the server is connected.

Tunori keeps an OAuth sign-in fresh on its own. If the server asks you to sign in again, the integration shows an error with a Reconnect button; see when something stops working. A server that uses a token has nothing to reconnect: if the token changes, delete the integration and add it again.