Post to social media from Notion

Integrations

A Notion Custom Agent can manage your OmniSocials content through a custom MCP connection in the agent's settings. The connection is remote: Notion talks directly to the hosted OmniSocials MCP endpoint.

Custom MCP servers are available on Notion's Business and Enterprise plans.

Before you start

A Notion workspace admin must allow custom MCP servers once:

In Notion, open Settings → Connections
On the Manage tab, turn on Enable custom MCP servers

If your workspace only allows approved connections, the admin also adds the OmniSocials URL under Approved connections → Add approved connection → Custom MCP server.

Setup

Create an API key in OmniSocials (Settings → API)
In Notion, open your Custom Agent's Settings
Go to Tools & Access
Click Add connection → Custom MCP server
Enter the MCP base URL:

Text
https://mcp.omnisocials.com

For authentication, choose the header-based option (bearer token) and paste your OmniSocials API key as the token
Click Connect

Verifying

Mention your Custom Agent in any page and ask:

List my connected social accounts on OmniSocials

A successful response with your accounts confirms the integration. A 401 means the Bearer token is wrong. Double-check you copied the full key including the omsk_live_ prefix.

What you can do

A Notion Custom Agent can:

Create, schedule, update, and publish posts
Upload media from URLs
List connected accounts and media library items
Query analytics for posts and accounts

The agent respects your API key's scopes. For example, a key without posts:write can't create posts.

Tips for working with Notion Custom Agents

Custom Agents work well with structured databases. Consider building a content calendar database in Notion and wiring an agent to push new rows to OmniSocials.
Give the agent a trigger (e.g. "when status changes to Ready") so it publishes the post without manual intervention.
Store platform-specific copy in separate database columns and let the agent map those to per-platform content on the post body.

Limitations

Notion's custom MCP connections are new and may change
Rate limits on the Notion side can limit how often an agent makes calls. OmniSocials' own 100 req/min limit applies independently.
The Bearer Token method sends the key on every request, so it's secure. The key is not exposed in the connector URL.

Last modified on October 20, 2026

Muse OpenClaw

Before you start

A Notion workspace admin must allow custom MCP servers once:

In Notion, open Settings → Connections

On the Manage tab, turn on Enable custom MCP servers

If your workspace only allows approved connections, the admin also adds the OmniSocials URL under Approved connections → Add approved connection → Custom MCP server.

Setup

Create an API key in OmniSocials (Settings → API)

In Notion, open your Custom Agent's Settings

Go to Tools & Access

Click Add connection → Custom MCP server

Enter the MCP base URL:

Text

https://mcp.omnisocials.com

For authentication, choose the header-based option (bearer token) and paste your OmniSocials API key as the token

Click Connect

Tips for working with Notion Custom Agents

Custom Agents work well with structured databases. Consider building a content calendar database in Notion and wiring an agent to push new rows to OmniSocials.

Give the agent a trigger (e.g. "when status changes to Ready") so it publishes the post without manual intervention.

Store platform-specific copy in separate database columns and let the agent map those to per-platform content on the post body.

Limitations

Notion's custom MCP connections are new and may change

Rate limits on the Notion side can limit how often an agent makes calls. OmniSocials' own 100 req/min limit applies independently.

The Bearer Token method sends the key on every request, so it's secure. The key is not exposed in the connector URL.

Last modified on October 20, 2026