Agent-ready documentation

Give your AI agent a social media system that already knows your product.

The Cadencz MCP server connects Claude, Codex, and other MCP clients to your Website Brain, brand voice, content plan, calendar, and analytics. Ask for the work in plain language; Cadencz handles the same planning, writing, scheduling, and approval flow as the app.

Included on Pro, Team, Growth. See plan details

The short version

Your agent brings the request. Cadencz brings the context.

Good social content usually starts somewhere other than a social dashboard: a shipped feature, a customer question, a changelog, or a decision made while building. MCP lets an assistant reach the product context behind that work without asking you to rebuild the brief every time.

Cadencz keeps the Website Brain, voice guidance, content plan, schedule, and analytics connected. Your assistant can turn a useful idea into a platform-native draft or a reviewed week while the same Cadencz rules stay in force.

One product, one set of rules

MCP calls use the same Brain retrieval, allowances, quotas, role permissions, and approval boundaries as the Cadencz app. It is an additional interface, not a looser path into your account.

Quick start

Connect in a minute

Create one token, register the streamable HTTP endpoint, and start with a read-only question. Tokens are workspace-scoped and shown only once.

  1. 1Open Settings → MCP in Cadencz and mint a token. Copy it immediately; the raw token cannot be shown again.
  2. 2Add the server to your client with the token as a bearer header.
  3. 3Ask “What is scheduled this week?” to confirm the connection before asking the agent to write or schedule anything.

Endpoint note: this documentation page is served at /mcp, while the MCP transport runs on the API origin. In local development use http://localhost:8000/mcp; in production use https://api.cadencz.com/mcp.

Codex CLI
export CADENCZ_MCP_TOKEN="cdz_mcp_your_token_here"
codex mcp add cadencz \
  --url https://api.cadencz.com/mcp \
  --bearer-token-env-var CADENCZ_MCP_TOKEN

The environment variable keeps the one-time token out of your Codex configuration file.

Claude Code
claude mcp add --transport http cadencz https://api.cadencz.com/mcp \
  --header "Authorization: Bearer cdz_mcp_your_token_here"

Claude Desktop and JSON clients
{
  "mcpServers": {
    "cadencz": {
      "type": "http",
      "url": "https://api.cadencz.com/mcp",
      "headers": {
        "Authorization": "Bearer cdz_mcp_your_token_here"
      }
    }
  }
}

Any client that can send a static Authorization header and speak streamable HTTP can use the server.

Capabilities

A focused tool surface for content operations

Cadencz exposes 16 tools: eight for reading context and performance, six for creating and moving content, and two owner-only account tools. The assistant sees only the tools its role and plan allow.

16

tools

8

read tools

6

write tools

1

approval boundary

Read

list_workspaces
The workspaces this token can reach, and which one is current.
list_channels
Connected accounts, and whether the plan currently covers each one.
list_brains
The Website Brains in this workspace.
query_brain
Retrieve product context from a Brain for a question, using the same retrieval the Writer uses.
get_current_plan
This week's content plan and every item in it.
get_plan_usage
Allowance usage against the plan's caps for the current period.
list_scheduled_posts
What is committed to publish in the coming days.
get_analytics
Engagement totals per platform over a window you choose.

Write

compose_post
Write one platform-native post from an idea, grounded in the Brain. Draws one AI generation and saves a draft.
plan_week
Run Plan My Week end to end; each planned post draws from the shared AI allowance.
schedule_post
Commit a draft to a moment in time. Quota-checked, including the X link-post debit.
cancel_scheduled_post
Pull a scheduled variant back to draft.
approve_plan_item
Approve a plan item into a scheduled post.
publish_now
Queue for immediate delivery. Irreversible, so it requires confirm: true.

Owner only

connect_channel_link
Returns the URL where a human connects a platform. It never accepts credentials.
get_subscription
The account's plan.

Access

Tokens that respect your workspace and role

Acts as the person who minted it

A scheduler's token can compose, schedule, and approve. Owner-only tools remain hidden from its tool list.

Stored hashed, shown once

Cadencz stores only a SHA-256 hash. If a token is lost, revoke it and mint a new one from Settings → MCP.

Checked on every request

Plan access, seat membership, and feature gates are re-checked on every call instead of only when a token is created.

Scoped to one workspace

A token reaches the workspace it was minted in. Use a separate token when you work across multiple workspaces.

Safety

Agent access with real boundaries

An agent can be useful without becoming an uncontrolled publisher. These boundaries are enforced server-side, not left to the model's instructions.

No billing or credential tools

MCP cannot check out, cancel a plan, open the billing portal, mint another token, or accept platform credentials.

Publishing needs a second decision

publish_now refuses unless the call includes confirm: true.

The same allowances apply

Composing, planning, scheduling, and platform quotas are charged and checked exactly as they are in the app.

Errors are machine-readable

A refused call returns a structured reason such as plan_allowance_exceeded, so the assistant can explain what happened.
Structured error
{
  "code": "plan_allowance_exceeded",
  "message": "AI generation allowance reached",
  "allowance": "AI generation",
  "limit": 400,
  "used": 400
}

Examples

Useful requests to try

Once connected, ask for the outcome instead of navigating through a dashboard.

Ship a feature, market it

We just shipped scheduled retries. Write a LinkedIn post and an X post about it in our voice, then schedule them for Tuesday morning.

Fill the week from the changelog

Use the latest product updates in our Brain to plan this week's content around the two most useful ideas for founders.

Review before it goes out

What is scheduled for the next seven days? Flag anything that reads like an ad or makes an unsupported claim.

Learn from last month

Read our last 30 days of analytics, explain which format earned the most engagement, and use that insight in next week's plan.

Help

Troubleshooting

Which plans include the Cadencz MCP server?
The authorised MCP server is included on Pro, Team, Growth. The plan is checked on every request, so downgrading below an eligible plan stops existing tokens immediately.
Can Codex connect to Cadencz?
Yes. Register the Cadencz streamable HTTP endpoint in Codex with the bearer token created in Cadencz → Settings → MCP. The setup command is included on this page.
Can an MCP agent publish without approval?
Publishing is approval-first. The publish_now tool is irreversible and requires confirm: true, while the app's plan limits and role permissions still apply.
Does Cadencz receive platform passwords through MCP?
No. The connect_channel_link tool only returns a URL for a human to open. Credentials and API keys are never accepted over MCP.

If a tool is missing, check the token's role. Owner-only tools are intentionally hidden from scheduler tokens, and plan access is evaluated again on each request.

The server is listed in the official MCP Registry as com.cadencz/cadencz and on Smithery.

Ready when you are

Let your agent work with the context you already built.

Start with the Website Brain for free. Connect an MCP client from Pro onward, then keep the final publishing decision in your hands.