← Studio

Connect the writing MCP

Stories are written by an agent through the MCP, then land in your Studio as drafts — where you edit, restructure, and ground them before publishing. Point your agent here once and go.

  1. You pick stories in the Studio
  2. Your agent builds them via the MCP
  3. Updates land back in the Studio to edit & publish

The round-trip

  1. Pick in the Studio. Browse the pre-screened feed and start the stories you want to work on. The app fills a light scaffold (subject, source, a framing hint) — that’s just a starting point; your MCP model does the real writing.
  2. Copy the story id. Every draft shows its sty_… id with a copy button (and a one-click “agent instruction”). Hand it to your agent.
  3. The agent builds it via the MCP — get_story → model/index → analyze → grounded sections — discussing the framing with you as it goes. You’re using a stronger model here, so this is where the depth comes from.
  4. Refresh the Studio. The updates are there. Edit anything by hand, then publish once the gate is green.

1 · Endpoint

https://blog.cidx.link/mcp

2 · Connect both servers

⚠ You need two MCPs connected: cidx (the builder — models & indexes) and cidx-press (the writer — this app). The writer reads & narrates what the builder makes, so both must be on. See plans →

Builder — cidx Standard ($19)+

Builds the models & indexes the stories are grounded in.

claude mcp add --scope user --transport http cidx https://www.cidx.link/mcp

Writer — cidx-press Professional ($49)

This engine — analyzes, writes grounded, and publishes. URL only; Claude opens a browser to sign in (OAuth), like cidx.link.

claude mcp add --scope user --transport http cidx-press https://blog.cidx.link/mcp

Claude Desktop / other clients: add custom connectors with the URLs www.cidx.link/mcp and https://blog.cidx.link/mcp, and sign in when prompted.

Prefer a token over the browser? (either server)

Mint a CIDX personal access token at cidx.link/account/api (one token, whole suite), then append it:

claude mcp add --scope user --transport http cidx-press https://blog.cidx.link/mcp \
  --header "Authorization: Bearer cidx_pat_YOUR_TOKEN"

3 · Authenticate

In Claude run /mcp, then Authenticate each server (browser sign-in). Both should read connected before you start.

4 · Drive it

Give your agent a prompt like this:

Connect to the CIDX Press MCP. Browse the latest feed (list_subjects mode=feed), pick a model-ready story, and write it up:
1. Build a compartment model and/or composite index for it with the cidx MCP.
2. analyze_model / analyze_index to get the reading.
3. create_story, add_evidence, add_section, and bind_claim so every consequential claim is grounded.
4. Leave it as a DRAFT — I'll review and publish it in the Studio.

What the agent can do

  • list_subjects · propose_framing — find & screen modelable happenings
  • analyze_model · analyze_index · compare_scenarios · seek_goal · review_changes — read the evidence
  • create_story · add_evidence · set_scenario · set_goal · add_section · bind_claim — write it, grounded
  • critique_draft · version_story · publish_story — check & ship (publish refused until grounded)