Chapter 20 · Operate

Integrations

After this chapter you can connect your ad platforms, social channels, SaaS tools, and remote MCP servers from one place, read each connection's health, and control exactly what Atlas is allowed to do with an external tool.

7 lessons · 31 min

Integrations is where you connect Pinnora to the services you already use. It is one page per project, grouped into three sections: remote MCP servers that extend Atlas, the ad and social channels you publish to, and the SaaS tools you want your creatives to reach.

This chapter is about plumbing, not making creatives. A connection here never acts on its own. It exists so another part of Pinnora, the Ads Manager, the social calendar, or Atlas, can act through it.

Two things to know going in. Connecting and disconnecting is limited to organization owners and admins, so members get a read-only view. And not every platform in the list is live in every deployment, so this chapter leads with the connections that are actually proven in production and is honest about which ones need extra setup first.

  1. The Integrations hubFind the hub, recognize its three sections, and know whether your role can connect things.4 min
  2. Connecting a platform or vendorConnect a channel or tool the right way, starting with the ones that are proven in production.5 min
  3. Managing and disconnecting connectionsRead a connection's real status, reconnect before a token lapses, and remove a connection cleanly.4 min
  4. What each connection unlocksPredict which Pinnora surface a given connection feeds before you wire it up.4 min
  5. What MCP isExplain what the Model Context Protocol adds to Atlas and when you would reach for it.4 min
  6. Connecting a remote MCP serverAdd a remote MCP server by URL or from the curated list, with the right transport and auth.5 min
  7. Controlling what Atlas can do with external toolsSet a per-tool allowlist on an MCP server and understand when Atlas has to ask before acting.5 min

Reference

Keep going