A Model Context Protocol (MCP) server for interacting with the DeepWriter API. This server provides tools for creating, managing, and generating
Deepwriter MCP becomes available to MCP clients through the deepwriter mcp mcp server. A Model Context Protocol (MCP) server for interacting with the DeepWriter API. This server provides tools for creating, managing, and generating content for DeepWriter projects through the standardized MCP interface.
A Model Context Protocol (MCP) server for interacting with the DeepWriter API. This server provides tools for creating, managing, and generating content for DeepWriter projects through the standardized MCP interface.
Once connected, the assistant can call these 3 tools directly:
Building — This will compile the TypeScript code into JavaScript in the build directoryTesting — You can test the MCP server locally using the provided test scripts:Debugging — For detailed logs, run the server with the DEBUG environment variable:The server is distributed via npm as @smithery/cli, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.
Before the server will start you need to supply one environment variable: DEEPWRITER_API_KEY. Keep credentials in your client's env block or a secrets manager rather than committing them.
Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Deepwriter MCP sits in that group, and the shape of its toolset — Building, Testing, Debugging — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.
| Tool | What it does |
|---|---|
| Building | This will compile the TypeScript code into JavaScript in the build directory. |
| Testing | You can test the MCP server locally using the provided test scripts: |
| Debugging | For detailed logs, run the server with the DEBUG environment variable: |
{
"mcpServers": {
"deepwriter": {
"command": "npx",
"args": ["-y", "@smithery/cli"],
"env": {
"DEEPWRITER_API_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| DEEPWRITER_API_KEY | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.