What MCP is

The short version

MCP stands for Model Context Protocol. It is an open standard for connecting an AI assistant to an outside server that offers tools and data. In Pinnora, it is how you give Atlas, the chat assistant, abilities that are not built into the product.

Think of MCP as a USB port for Atlas. It is a standard socket, so any server that speaks the protocol can plug in and offer its tools, and we do not have to build a one-off adapter for every service you might want.

Why you would reach for it

On its own, Atlas generates and manages creatives inside Pinnora. Connect an MCP server and it can also reach into whatever that server exposes. A documentation server lets Atlas look things up. A project-tracker server lets it read or file issues. A data server lets it pull numbers you keep somewhere else. You are not stuck with a fixed list of integrations: if a service offers a remote MCP server, you can connect it.

Why it sits at the top

MCP servers are the first category on the page, above Channels and Vendors, and that placement is on purpose. These connections change what Atlas itself can do, rather than where your finished creatives go. That is a bigger shift, so it reads first.

What to expect

Connecting a server is a real, live operation, not a setting you save and hope about. Pinnora contacts the server, confirms it is reachable, and reads the list of tools it offers before saving anything. If the server offers no tools, the connection is refused, because there would be nothing for Atlas to use. The next two lessons walk through connecting one and then controlling what it is allowed to do.