Docs

Connect AI to Your Workspace

Model Context Protocol (MCP) setup for Claude and other AI clients

edtr.md is an AI-native Markdown workspace. Instead of a chatbot bolted onto the editor, we expose your files through a remote MCP server, so you can connect any MCP-compatible AI client and let it work on your files directly. Bring your own agent: Claude, Claude Code, Cursor, or anything else that speaks MCP.

The server

edtr.md runs a remote, streamable HTTP MCP server at:

https://edtr.md/api/mcp

Authentication is automatic. The first time your client connects, it receives a 401, opens a browser window with a sign-in and consent screen, and completes an OAuth flow against your edtr.md account. No API keys or tokens to copy.

Set up in your client

claude.ai

Go to Settings → Connectors → Add custom connector and paste the server URL above. Claude will prompt you to sign in and approve access the first time you use it.

Claude Code

claude mcp add --transport http edtrmd https://edtr.md/api/mcp

Cursor

Add the following to .cursor/mcp.json:

{
  "mcpServers": {
    "edtrmd": {
      "url": "https://edtr.md/api/mcp"
    }
  }
}

VS Code

Add the following to mcp.json:

{
  "servers": {
    "edtrmd": {
      "type": "http",
      "url": "https://edtr.md/api/mcp"
    }
  }
}

Other clients

Any client that supports streamable HTTP MCP transport and OAuth can connect using the same endpoint. Point it at https://edtr.md/api/mcp and complete the sign-in prompt when it appears.

What your AI can do

Once connected, your AI client has access to the following tools:

Tool	Description
`create_file`	Create a new Markdown file in your workspace.
`list_files`	List the files and folders in your workspace.
`read_file`	Read the contents of a file. Set follow_links to also pull in the notes it links to (wikilinks and relative links), one level deep.
`update_file`	Overwrite a file with new content.
`edit_file`	Make a surgical edit by replacing an exact snippet of text, without resending the whole file.
`save_document`	Save a document your AI wrote straight into your workspace. Reuses the file when the title is unchanged, and saves a full rewrite as a new version.
`search_files`	Search file names and content across your workspace.
`get_backlinks`	Find which files link to a given file, through wikilinks or relative links.
`move_node`	Rename and/or move a file or folder by giving it a new path.
`open_pr`	Open a GitHub pull request or GitLab merge request from a workspace connected to a repo.
`delete_node`	Delete a file or folder.
`publish_file` (Pro)	Publish a file to a public URL.
`unpublish_file`	Take a published file back down.
`list_workspaces`	List the workspaces you can access, owned and shared, with your role in each.

Files your AI creates land in a dedicated Claude workspace inside the editor, kept separate from your own files. Publishing requires a Pro plan; every other tool is available on the free plan.

Every tool also accepts an optional workspace argument, so your AI can work in any workspace you own or that is shared with you. Call list_workspaces to see them along with your role in each: owners and editors can read and write, while viewers get read-only access.

The server also ships ready-made prompts that show up in claude.ai's "/" command menu by their titles: Draft a document, Summarize notes, Publish as pull request, Save this conversation, New note, Find a note, Daily note, Extract tasks, Link my notes, Polish this note, and Write a blog post, so common workflows are one command away.

Automatic saving

You do not have to ask your AI to save anything. When a client produces a Markdown document in chat, it calls save_document and the file appears in your workspace, versioned and synced. This works the same from claude.ai, ChatGPT, Claude Code, or any other connected client. Write in your AI chat, and it lands in your workspace.

The tool keys off the document title. Ask for a small change and it updates the same file in place, so you keep one clean copy. Ask for a full rewrite and it is saved as a new version, for example my-post-v2.md, so the original is never lost. From there the downstream path is publishing: a document that starts in chat, lands in your workspace, and ships to your site as a GitHub pull request or GitLab merge request in one click.

Access and security

Every client authorizes independently through OAuth, so you approve each connection with a consent screen before it gets access. You can see and revoke connected clients at any time from inside the editor, under Menu → Connect AI. Files created or edited by an AI client are scoped to your account, the same as any other file you own.

Get started

Open the editor to find your workspace, or see pricing if you want to publish files created by your AI.