Get started

MCP integration

Your brand.
In your AI workflow.

Bring the brand knowledge and content work in Postomatic into your AI assistant. Explore ideas with your own context close at hand.

Open Developer Centre See the setup

For workspaces with enabled MCP access.

MCP / Your connected context
Your AI assistantCodex · Claude Code · Cursor
PostomaticRead access
Brand BrainKnowledge & voice
OpportunitiesQuestions & relevance
Your contentCalendar & articles
Only the access you grant

Ask with context

Less copy and paste.
More to work with.

Give your assistant a permitted view of the knowledge, opportunities and content already in Postomatic.

Keep your brand in the conversation.

Read your Brand Brain summary to bring products, audience, voice and expertise into the task you’re working on.

Explore Brand Brain

Explore what deserves an answer.

Inspect ranked content opportunities for the permitted brand. Use the available reasoning and evidence to discuss a useful next direction.

See the work already in motion.

Read calendar entries and article records before deciding what to discuss next. Keep the planning context close to the conversation.

Ask from a clearer picture.

Inspect publishing state and available Search Console evidence. Separate what has been published from what the data currently shows.

Connect your client

A small setup.
A useful connection.

Choose your client below. Developer Centre provides the current connection configuration for your workspace.

  1. 01

    Open Developer Centre.

    Use a workspace with enabled MCP access. An owner or administrator can create the connection.

  2. 02

    Choose the brand.

    Create the recommended read-only credential for the brand your assistant needs to inspect.

  3. 03

    Add it to your client.

    Use the endpoint and one-time credential in the current configuration. Then list the available tools in your client.

Terminal
export POSTOMATIC_API_KEY="YOUR_ONE_TIME_API_KEY"
codex mcp add postomatic --url https://app.postomatic.co/api/mcp --bearer-token-env-var POSTOMATIC_API_KEY
Codex reads the bearer token from the environment variable when it connects.

Replace YOUR_ONE_TIME_API_KEY with the credential from Developer Centre. Keep it in your client’s secret storage.

Your connection. Your control.

Useful access.
Clear boundaries.

Brand by brand.

The credential can access only its granted brands and permitted tools.

Read first.

The recommended connection reads context. Article creation and publishing stay in the product workflow.

Revoke when you need to.

Remove credential access in Postomatic and inspect the recorded integration activity.

Your MCP questions

Know what
you’re connecting.

What is MCP?

Model Context Protocol gives a compatible AI client a way to use tools from another service. Postomatic’s MCP server makes permitted brand and content information available to your assistant through a scoped connection.

Which AI clients can I connect?

Postomatic provides setup configurations for Codex, Claude Code and Cursor. Other clients need support for stateless Streamable HTTP and bearer-token authentication. Use the current configuration from Developer Centre when connecting.

What can my assistant read?

With the relevant permission, it can list granted brands, read a Brand Brain summary and inspect ranked opportunities, calendar entries, articles, publishing state, available performance evidence and integration audit events. Results stay within the credential’s brand grants and scopes.

Can my assistant create or publish articles through MCP?

The recommended MCP connection is read-only. The current toolset does not create articles, change calendar entries or publish content. A separate, explicitly confirmed tool can replay the saved result of an existing verified connection test; it cannot create a new external effect.

Which plan and permissions do I need?

Your workspace needs current plan entitlement and enabled API and MCP access. An owner or administrator creates and manages the credential. Developer Centre shows whether the connection is available for your workspace; check your current plan there before connecting.

How do I control or remove access?

Grant only the brands and scopes the client needs. The credential is shown once during setup, so store it securely in your client. You can revoke it in Postomatic when access is no longer needed; requests are subject to live access checks and appear in the integration audit trail.

Connect your context

Your assistant.
More familiar with your brand.

Check MCP availability and create your scoped connection in Developer Centre.

Open Developer Centre Compare plans