Docweave MCP vs IWork Studio
A side-by-side look at the Docweave MCP and IWork Studio MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Docweave MCP for developer tools work as a local process; choose IWork Studio for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Docweave MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You want tools like
generate_pdf, read_pdf.
Choose IWork Studio when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 61/100 · Good | 37/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Freemium | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 2 |
| Directory activity | 4 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 2 | Not listed |
| Full listing | View Docweave MCP | View IWork Studio |
Tools & capabilities
Docweave MCP tools 2
generate_pdfGenerate a PDF from raw HTML, a public URL, or a template + JSON data. Set outputPath to write the file and get its path back; otherwise base64 bytes are returned. The canonical way for an AI agent to turn content into a shareable, correctly-formatted PDF.read_pdfRead a PDF and return its text as markdown (or plain text). Accepts a public URL, base64 bytes, or a local file path. Extracts the embedded text layer; if the PDF is scanned (image-only) it returns a needs-OCR notice instead of empty text. The canonical way for an AI agent to ingest a document's contents.
IWork Studio tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Docweave MCP
{
"mcpServers": {
"docweave-mcp": {
"command": "npx",
"args": [
"-y",
"@docweave/mcp"
]
}
}
}
IWork Studio
{
"mcpServers": {
"iwork-studio": {
"command": "uvx",
"args": [
"--from",
"iwork-studio@latest",
"iwork-studio-mcp"
]
}
}
}
Frequently asked questions
Docweave MCP is categorized under Developer Tools and uses a local stdio subprocess. IWork Studio belongs to Developer Tools and uses a local stdio subprocess. Pick Docweave MCP for developer tools work and IWork Studio for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Docweave MCP is listed as freemium — a free tier with paid plans. Auth: api key required. IWork Studio has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add docweave-mcp and iwork-studio as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Docweave MCP has a quality signal of 61/100 (Good) with 4 views, 0 installs and 0 GitHub stars. IWork Studio has 37/100 (Fair) with 0 views, 0 installs and 2 GitHub stars.