Skip to content
All documentation

Connectable MCP servers

Video

Connect your MCP servers once

2:56 · in English, with subtitlesVideo page · All video tutorials
Chapters (4)

OnlyMCP connects to any remote MCP server that is reachable over https. You add it once, in the dashboard under Connections, and its tools appear in every client connected to OnlyMCP, prefixed with the name you gave the connection.

How a server signs in

  • OAuth sign-in. You authorize OnlyMCP once, in a browser window of the server’s own provider. OnlyMCP never sees your password, stores the tokens it receives encrypted and renews them by itself.
  • Token. You paste a token once. It is stored encrypted and never shown again.
  • OAuth sign-in or token. The server accepts either, and you choose.
  • Custom header. For a server that expects its key in a header of its own, such as X-Api-Key: you name the header and paste the value once. It is stored encrypted.
  • Username and password. For a server behind Basic auth: you enter both once. The password is stored encrypted and never shown again; in a team, only members who manage the credentials see the username.

In a team, each connection decides whether one authorization is shared by everybody or whether every member signs in as themselves.

Your AI can connect a server too: connection_create adds one with any of these kinds, connection_update changes it and connection_delete removes it. A secret passed this way goes through the conversation; to keep it out of the conversation, enter it in the dashboard.

Picking a server

In the dashboard, Add a server opens a catalogue of suggested servers. You search it by name, description or address, each card shows how the server signs in, and a server you have already connected is marked as added. An administrator keeps the catalogue, so entries can be added, reordered or switched off at any time; GitLab and Gamma are among them. A server that is not in the catalogue connects just the same, by its address under Connections.

Servers with a checked address

The servers below were checked on the date given, against the provider’s documentation and against the server itself. The catalogue starts from this list and can differ from it, because an administrator may edit it. They are examples of what can be connected, not built-in integrations, and each one stays subject to its provider’s own terms.

A server that only runs as a local program on your machine cannot be connected, because OnlyMCP does not start programs on anybody’s behalf, see security.

A server connected during a session

A client lists the tools of its servers once per session, so the tools of a server you connect while a session is running may be missing in it until the client refreshes. Until then OnlyMCP’s own tools reach them. list_connections names your connections, connection_tool_schema shows what a tool takes, by its name <prefix>__<tool>, and connection_call runs it. Called this way, a tool has the same rights and counts the same against your plan as when the client calls it directly. connection_call reaches only the tools of a server connected after your client last listed its tools. A server that already existed at any of its listings, even switched off, is reached by its tools’ own names, so a block you set in a client holds for that client; for a tool such a server shows only since, reconnect the client. To block a tool for every client, switch it off in OnlyMCP.

Either way, a call to such a tool appears in your activity log as <connection>/<tool>, without its arguments and without its answer, see security.

Where to go next