Skip to content
Model Context Protocol

Your assistant.
Your workspace.

Picmim speaks the Model Context Protocol, so Claude, Claude Code, Cursor, and any other MCP client can work directly inside your workspace: read the calendar, draft posts, schedule them, and pull analytics.

Get access → Read the setup guide

Available on request while MCP access rolls out.

In practice

Things you can just ask

No new interface to learn. You talk to the assistant you already use, and it does the work in Picmim.

  • “What is on my calendar next week?”

    Reads your scheduled and published posts across every connected account, with times in your workspace timezone.

  • “Find the gaps and draft three posts to fill them.”

    Spots the open slots, checks how similar posts performed, then writes drafts for you to review.

  • “Schedule that one for Tuesday morning.”

    Picks the window from your own posting history rather than a generic best-time chart.

  • “How did last month go?”

    Pulls a performance digest: totals, period-over-period movement, follower growth, and top posts.

Capabilities

What it can reach

Read-only tokens expose 21 tools. Read and write unlocks 42. Every one of them is the same tool Picmim's own assistant uses, so behaviour matches what you already know.

Calendar and scheduling

Read scheduled and published posts, find gaps in the calendar, and get posting windows suggested from your own performance history.

Content and media

Create, update, duplicate, and delete posts across nine platforms. Search your media library, import images, or generate and edit them.

Analytics

Pull workspace performance summaries, insights by focus area, and the patterns behind what worked.

Inbox and approvals

Read comments on published posts, reply to them, and move posts through approval, publishing, or cancellation.

Connect it

One endpoint, one token

Picmim is a remote MCP server over Streamable HTTP. Point your client at the endpoint, add your token, and the tools appear.

Endpoint

POST https://picmim.com/mcp

Client configuration

{
  "mcpServers": {
    "picmim": {
      "type": "http",
      "url": "https://picmim.com/mcp",
      "headers": {
        "Authorization": "Bearer pmk_your-token-here"
      }
    }
  }
}

Create a token in your workspace under Settings, then MCP Access. It is shown once, so store it somewhere safe.

Security

Scoped, hashed, revocable

An assistant with access to your accounts should be easy to reason about. Here is exactly what a token can and cannot do.

Two scopes, not one

A read-only token cannot write. The write tools are not merely blocked, they are never listed, so the assistant cannot try.

One workspace, one member

Every token is bound to a single workspace and the member who created it. It can never reach further than that person can.

Checked on every call

Membership is re-checked on each request. Remove someone from the workspace and their tokens stop working immediately.

Permissions follow demotion

If a member loses admin rights, their write token quietly drops to read-only on the next call. No cleanup needed.

Stored as a hash

Only a SHA-256 hash of the token is kept. The plaintext is shown once at creation and never again, not even to us.

Revoke or expire

Kill a token instantly, or give it an expiry date when you create it. Rate limited to 120 requests a minute.

FAQ

Questions worth asking

Which clients work with it?

Any client that supports remote MCP servers over Streamable HTTP. That includes Claude, Claude Code, Cursor, and a growing list of others. If your client accepts a server URL and a bearer token, it will work.

Can it post without asking me?

That depends on your client configuration and your token. A read-only token cannot post. A read and write token permits changes; Picmim marks write tools as destructive, but approval prompts are controlled by your MCP client and may be disabled. Only issue a write token to clients you trust, and review your client's approval settings.

What happens when I revoke a token?

It stops working on the next call. There is no cache to wait out and no session to expire. The same applies if the member who created it leaves the workspace.

Can I connect my social accounts through it?

No. Connecting accounts happens in the Picmim web app, where the OAuth flows live. The MCP server works with the accounts you have already connected.

How do I get access?

MCP access is rolling out per workspace. Get in touch and we will switch it on for yours, then you can create tokens under Settings, then MCP Access.

Point your assistant at it

Get MCP access switched on for your workspace, and your assistant can start working in Picmim today.

Get access → Read the setup guide