Add the claude.ai Connector

Overview

If you use claude.ai in the browser or the desktop app, you can connect it to your Postnomic account without ever generating or pasting a token. The claude.ai Connector uses OAuth — you click a button, sign in with your existing Postnomic (Auth0) account in a normal login window, and approve the connection. claude.ai stores and refreshes the resulting credential itself, so there's nothing for you to copy, store, or rotate by hand.

This is the easiest way to give Claude access to your blogs if you're working from claude.ai directly. If you're using a local agent or CLI tool instead (Claude Code, an editor extension, or any other MCP client running on your machine), use a Personal Access Token instead — see Connect a Local Agent (Personal Access Token) — OAuth-based connectors are specific to claude.ai's hosted environment.

Step 1: Add the connector

In claude.ai, open Settings.
Go to the Connectors section.
Click Add custom connector.
Enter the server URL:
```
https://mcp.postnomic.com/mcp
```
Click Connect.
You'll be redirected to a normal Postnomic/Auth0 sign-in page — sign in with the same account you use for the Postnomic dashboard.
Review the requested permissions and approve the connection.

Once approved, claude.ai redirects you back and the connector shows as connected. No token ever appears on screen — the entire exchange happens through the OAuth redirect, and claude.ai holds the resulting credential on your behalf.

How the OAuth flow works

The diagram below shows the shape of the exchange. claude.ai never talks to Auth0 or to the Postnomic MCP server directly for sign-in — it goes through Postnomic's API, which acts as an OAuth proxy in front of Auth0, and only receives back a token scoped to your account.

claude.ai sends you to the Postnomic API to add the connector.
The API's OAuth proxy redirects you to Auth0 to sign in — this is the same Auth0 login used by the Postnomic dashboard.
After you approve, Auth0 returns control to the API, which issues an OAuth token scoped to your account.
claude.ai uses that token to call the Postnomic MCP server, which forwards every tool call to the API as you — exactly like a Personal Access Token does for local agents.

What it can do

Once connected, Claude has access to the same set of tools a Personal Access Token would give a local agent — because the connector authenticates through the same underlying account, not a separate integration. Everything the connector does still runs as you: it can only see and modify the blogs you're a member of, and only with the role you hold on each.

Available tools include listing your blogs and posts, reading a post's content and analytics, creating and updating posts and translations, uploading images, and publishing, unpublishing, scheduling, or archiving posts. Nothing the connector does bypasses the quota, role, or subscription checks that apply everywhere else in Postnomic.

Troubleshooting

You must be signed in to Postnomic. The OAuth flow redirects to the same Auth0 login used by the dashboard — if you don't already have a Postnomic account, sign up first, then add the connector.
MCP access requires a paid plan. Free-tier accounts can complete the OAuth sign-in, but tool calls are rejected once claude.ai forwards them to the API. Upgrade to Plus, Pro, or Enterprise to actually use the connector's tools.
Connection expired or stopped working? OAuth credentials can expire or be revoked (for example, if you changed your Postnomic password or revoked app access in Auth0). Remove the connector from claude.ai's Connectors settings and add it again to run through the sign-in flow once more.
Wrong blogs showing up, or none at all? The connector always reflects your current blog memberships and roles at the time of the call — if you were just added to or removed from a blog, try the action again; there's nothing to reconnect.

Was this article helpful?

Back to category