MCP server

Postlyra runs an MCP server at:

https://mcp.postlyra.com

Point an MCP client at it with a Postlyra API token and the client can read your brand's voice and pillars, push content ideas, browse the idea queue, and write drafts into Planning.

It is the same engine the REST API and the CLI use, so dedup, idempotency and brand scoping behave identically whichever path you take.

Why you would use it

The CLI mines a whole time window blindly: every commit in the last 7 days goes to an AI, which picks what is worth writing about.

MCP is for when an agent is already reasoning about the material. If Claude Code just finished a feature with you, it knows which part was interesting in a way a commit-log scan never will. It can call get_mining_context, read your local files itself, and push two good ideas instead of eight generic ones.

What it cannot do

No tool can publish or approve

push_ideas adds ideas with status new. create_draft adds drafts with status draft. Both land in a human review queue.

There is no tool that approves a draft, schedules a slot, or publishes anything. An agent telling you it "posted" or "scheduled" something is wrong.

The server also never reads your machine. It has no access to your git history, your notes or your files. An agent running locally reads those itself and sends only the finished ideas.

Brands

One token reaches every brand on the account. Each call acts on exactly one, resolved most-explicit first:

1. The tool's brand argument, holding a brand_id from list_brands.
2. The X-Postlyra-Brand header, if the client sends one.
3. The account's only brand, if there is exactly one.

An account with several brands and no brand argument gets an error naming list_brands. There is no way to reach a brand your token's user does not belong to.

In a session touching more than one brand, call list_brands once at the start and pass brand explicitly on every call after that.

Authentication

A plain Sanctum bearer token. No OAuth, no client registration, no separate connection object.

Claude.ai and ChatGPT connectors will not work yet

Those clients discover a server through OAuth metadata this server does not advertise. Any client that lets you paste a bearer token works today, which includes Claude Code. A hosted connector needs OAuth support that is not built yet.

Next

• Connect a client
• Tool reference
• The mining flow
• Limits