Connecting a remote MCP server

Add a server

In the MCP servers section, click Add MCP server. You can pick from a curated list of known servers or paste the URL of any remote server you have access to. Pinnora speaks two transports, Streamable HTTP and SSE, and works out which one the server uses, so you do not have to.

It is tested the moment you add it

When you add a server, Pinnora connects to it right away, lists its tools, and only then saves the connection. This is like calling a phone number once to hear it ring before you add it to your contacts. A bad URL or an unreachable server fails on the spot instead of saving quietly and breaking later. A server that exposes no tools is rejected, because there would be nothing for Atlas to call.

Authentication

Some servers are open. Many want proof of who you are. Pinnora supports a bearer token, which you paste when you add the server, and full OAuth, where you approve access on the server's own login screen and are returned to Pinnora. The row records which mode a server uses, so you can tell at a glance.

Reading a connected server

Once saved, each MCP server gets its own row showing how many tools it offers, which transport it speaks, and its auth mode. That row is also where you set the per-tool permissions covered in the next lesson. You can remove a server whenever you want, which withdraws its tools from Atlas immediately.