Connecting & consent

Easy Writer ships a headless local server, easywriter-mcp, that speaks the Model Context Protocol over stdio. An MCP client — such as Claude Desktop — launches it with a project path and calls its tools to read and change that one project.

Connect Claude Desktop

Use the Claude subscription you already pay for — no API key needed. The app writes the exact snippet for you: Help ▸ Connect Claude Desktop shows a ready-to-paste config with the server path and your current project filled in. In Claude Desktop, open Settings ▸ Developer ▸ Edit Config and merge it into claude_desktop_config.json, then restart Claude Desktop:

{
  "mcpServers": {
    "easywriter": {
      "command": "C:\\Path\\To\\easywriter-mcp.exe",
      "args": ["C:\\Path\\To\\your-project.ewriter"]
    }
  }
}

The command is the server executable (it ships beside the app); the single argument is the project to operate — an .ewriter file or a project folder.

How it behaves

• One project. The server operates the single project it was launched with, through the same engine the desktop app uses.
• Address by name. Tools take object names (entities also resolve by alias); when a name is ambiguous, the tool says so rather than guessing.
• Every change is one undo step, saved immediately. A mutating tool applies its change as one undoable step and saves the project right away; undo_last reverts the most recent one.
• Safe alongside the app. If the same project is open in the desktop app, the app notices the server's saves and offers to merge them — that is the intended workflow, not a conflict. The server likewise adopts changes the app makes on disk before each tool call, so neither clobbers the other.

Consent

The client (Claude Desktop) mediates consent: it shows you which server it is launching and asks before calling tools, per its own settings. The server itself performs no network access — it only reads and writes the local project files you pointed it at.