Connect AI Assistants

What is MCP?

The Model Context Protocol (MCP) is an open standard that lets AI assistants call external tools. PostRite exposes a set of tools — creating posts, scheduling, listing connected accounts, and more — that a compatible assistant can use on your behalf. The connection is authorized with OAuth 2.1, the same family of standards banks and identity providers use, so the assistant never sees your password and only gets the access you approve.

Enabling AI assistants for your organization

For security, AI-assistant access is off by default for every organization. Before an assistant can connect, the organization owner must enable it under Settings → Organization → AI assistants. There are two independent switches:

• Remote MCP access — allows assistants like Claude to connect through the MCP server (the flow described below).
• In-page browser agents (WebMCP) — exposes in-page tools to browser AI agents while a member is using the PostRite app.

Turning a switch off takes effect immediately: pending consents are rejected, existing connections stop working on their next request, and their tokens can no longer be refreshed.

Adding PostRite to Claude

In a Claude client that supports custom connectors, add a new connector and paste the MCP server URL above. Claude will open a PostRite sign-in and consent screen in your browser:

1. Sign in to your PostRite account (if you are not already signed in).
2. Choose the organization the assistant should act in. Access is bound to that one organization — the assistant can never reach data in your other workspaces. Only organizations whose owner enabled MCP access are selectable.
3. Review the requested permissions (scopes) and click Authorize. You are returned to Claude, now connected.

What the assistant can do

Every request the assistant makes runs with the exact same permissions your own account has in the chosen organization — it can never do more than you can. Available tools include:

• Posts — list, view, create, schedule, update, cancel, reschedule, and retry posts.
• Templates — list, view, create, update, and delete reusable content templates.
• Connected accounts — list your connected social accounts and check platform availability.
• Media — list media, import an image or video from a URL, and delete media.
• Analytics— read a post's engagement metrics, the organization's analytics summary, and top posts by engagement.
• Billing — read your plan, usage, and limits.

Understanding scopes

Scopes are fine-grained permissions. During consent you can see exactly which are requested; an assistant only receives the scopes you approve, and each one is enforced on every request:

• posts:read / posts:write — view / manage posts.
• templates:read / templates:write — view / manage templates.
• media:read / media:write — view / import or delete media.
• platforms:read — view connected accounts and availability.
• billing:read — view plan and usage (organization owners only).

Revoking access

You can disconnect an assistant at any time from within the AI client that holds the connection (remove the PostRite connector). Doing so revokes its tokens — the assistant immediately loses access. Access tokens are also short-lived by design, so even without an explicit revocation an assistant cannot retain access indefinitely.