Integrations

Your brand, connected to the tools you use.

Monobase integrations let agents read your briefs and files, publish what you approve and read the results. Your AI tools read your brand over MCP.

What a connection looks like inside Monobase.

  • Figma

    Your design system comes in from Figma.

  • Google Drive

    Agents read your briefs straight from Drive.

  • Publishing

    You publish approved posts from Monobase.

Context

Briefs and brand files your agents read while they work.

  • Google Drive

    Agents read briefs and files from Drive.

    Reads

  • Notion

    Agents read your Notion pages and databases.

    Reads

  • ClickUp

    Agents read tasks, docs and pasted links.

    Reads

Design and design systems

Your designers’ files and components, where they already live.

  • Storybook

    Agents read your public component stories.

    Reads

  • Canva Soon

    Agents work in your Canva designs.

Marketing

The channels you publish to, and the ones Monobase reads your results from.

Publish

  • LinkedIn

    You publish approved posts as a member.

    Reads and publishes

  • Mailchimp

    You send newsletters to your audience.

    Reads and publishes

  • Ghost

    You publish approved articles to Ghost.

    Reads and publishes

  • LinkedIn Company Pages Soon

    You post to your Company Page.

Read

  • Facebook and Instagram

    Agents read your Pages and Instagram posts.

    Reads

  • X

    Agents read your posts and their reach.

    Reads

  • TikTok

    Agents read your videos and their views.

    Reads

  • WordPress

    Agents read what your site published.

    Reads

Measurement and ads

Results read from the sources you connect, never guessed.

  • Google Analytics

    You see each channel’s traffic.

    Reads

  • Google Search Console

    You see search performance per page.

    Reads

  • Google Ads

    You see how your ads perform.

    Reads

AI tools over MCP

The other direction: your AI tools read your brand, and your agents use your own MCP servers.

  • Your own MCP servers

    Agents use the MCP servers you add.

Missing a tool? Add your own MCP server, signed in with a token or OAuth, or tell us which one you need.

Questions about Monobase integrations

Which integrations does Monobase have?

Monobase integrations connect your workspace to the tools your team already uses. Agents read briefs and files from Google Drive, Notion and ClickUp, take your design system from Figma and read your public Storybook. They publish approved posts to LinkedIn, newsletters through Mailchimp and articles to Ghost, read your Facebook, Instagram, X, TikTok and WordPress posts, and read results from Google Analytics, Search Console and Google Ads. Your AI tools read your brand over Monobase’s MCP server.

Can an agent publish on its own?

No. Agents draft, and a person approves before anything goes out. Three channels send today: LinkedIn posts as a member, Mailchimp newsletters and Ghost articles. The other channels are read, for your results and for Signals. Posting to LinkedIn Company Pages is coming soon.

Who can connect a tool, and what may agents do with it?

Owners and admins connect a tool with its own sign-in, and each connection picks exactly one account, such as one Page or one audience. For every tool of a connector you set whether an agent may always use it, must ask first or may never use it.

What happens when a connection breaks?

Monobase checks connections regularly. A broken one shows a reconnect state on its card and sends an alert to the Inbox, so nobody finds out from a failed post.

Can we connect our own MCP server?

Yes. Add an MCP server’s address and sign in with a bearer token or OAuth, and your agents can use its tools. A pasted API key isn’t accepted, by design.

How is this different from Monobase’s MCP server?

Integrations bring your tools’ data into Monobase and send approved work out. Monobase’s MCP server is the other direction: Claude, ChatGPT, Cursor and Copilot read your Brand System and design system, read-only by default.