Skip to main content
CaptureFlow’s remote MCP server lets an AI assistant work with your CaptureFlow content: read your ideas, inputs and posts, create ideas and drafts, and propose posts for your approval.
Nothing is ever published without your approval. An assistant can propose a post; you accept or reject it in CaptureFlow.

Connecting

  1. Add the server URL in your assistant (see the page for your assistant).
  2. Sign in to CaptureFlow when the assistant asks.
  3. Choose the workspace and what the assistant may do: Read only, Read and create drafts or Full access. You can narrow what it asked for.
Your connected assistants are listed in Settings > API & MCP > Connected apps, where you can disconnect them at any time. Read-only URL: an assistant connected to /mcp/readonly can read, never change anything. Use it when you only want answers about your content.

Tools

Each tool matches an API operation and needs the same scope. Tools are annotated: reads are readOnlyHint, and only update_post_draft and withdraw_post_proposal are destructiveHint (they replace or take back something).

Good to know

  • Workspaces: when you belong to several, tools take a workspace_id; list_workspaces lists them. See Workspaces.
  • Safe retries: tools that change something take an optional idempotency_key, except refresh_input_upload_url and complete_input_upload, which are safe to repeat on their own (conventions).
  • More permissions: if a tool needs a scope you didn’t grant, the assistant asks you to approve it (or tells you to reconnect).
  • Errors come back as tool errors with the same code as the API, explained on the errors page.
  • Your data is used only to serve you, never to train AI models. The assistant receives only what its permissions allow.