Read, write, and update docs with the MCP

The Falconer MCP lets coding agents like Claude CodeCode, Cursor, and CursorCodex read, search, create, and edit your Falconer docs directly — without leaving your editor or chat interface.

Prerequisites

A Falconer account with a Pro subscription (required for API key access)
Claude Code or CursorClaude Code, Cursor, or Codex (or any client that supports remote HTTP MCP servers)

Set up the MCP

Follow the Set up MCP and CLI guide to install the CLI, authenticate, and add the MCP server for Claude Code or Cursor. guide to authenticate with OAuth and connect the remote MCP server to Claude Code, Cursor, or Codex. No local installation required.

Use the agent

Once connected, the agent can search, read, create, edit, organize, and editmanage your Falconer docs.

Search for a doc

Ask the agent:

Search my Falconer docs for our API authentication guide

Or in Claude Code, the agent will call search automatically when you reference internal knowledge.

Search returns excerpts. Use read with the document ID to get the full content after a search.

Read a specific doc

Paste a Falconer link into your conversation:

Read this doc: https://falconer.com/editor/abc123__api-auth-guide

The agent fetches the full markdown content and uses it as context.

Create a new doc

Try something like:

Summarize what we just discussed and save it as a Falconer doc

The agent calls create with the markdown content and returns the URL of the new doc. It lands in your Private collection — you can review and publish it from there.

Edit existing docs

Permissions apply. The agent can only access docs your account has permission to see.

You can ask for specific updates, like:

Update the Falconer doc ‘Deployment runbook’ — change all references to staging-v1 to staging-v2

The agent reads the doc first and then makes the update.

You can also ask for generic updates, like:

Update all of our deployment-related docs based on this session

Upload images or videos

Add media to a doc by referencing a local file:

Add this screenshot to the 'Deployment runbook' doc: ./screenshots/deploy-step1.png

The agent uploads the file and inserts the ready-to-use snippet into the document content.

Manage comments

The agent can read and interact with comments on any doc you have access to:

Show me all open comments on the 'API authentication guide'

Resolve all comments on the 'Onboarding doc' that have been addressed

Organize docs and folders

You can ask the agent to move, reorganize, or create folders:

Create a folder called 'Runbooks' inside the Engineering collection

Move the 'Deployment runbook' doc into the Runbooks folder

Show me the navigation tree for the Engineering section

Publish a doc

Once you've reviewed a draft in your Private collection, ask the agent to publish it:

Publish my 'API rate limiting' draft into the Engineering collection

Update permissions

Control who can access a doc:

Update the 'Incident response runbook' so the whole company can view it