IWork Studio vs .prompts
A side-by-side look at the IWork Studio and .prompts MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
.
.promptsDeveloper Tools.prompts, the home to all your AI prompts, everywhere you need them.38FairAuth: not declaredVerdict: choose IWork Studio for developer tools work as a local process; choose .prompts for developer tools. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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 | . .prompts | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 37/100 · Fair | 38/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing |
Tools & capabilities
IWork Studio tools
No tool names declared yet. Check the project README from the listing page.
.prompts 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.
IWork Studio
{
"mcpServers": {
"iwork-studio": {
"command": "uvx",
"args": [
"--from",
"iwork-studio@latest",
"iwork-studio-mcp"
]
}
}
}
.prompts
No confirmed install command for .prompts yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
IWork Studio is categorized under Developer Tools and uses a local stdio subprocess. .prompts belongs to Developer Tools and uses an install path we have not confirmed yet. Pick IWork Studio for developer tools work and .prompts 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. .prompts has no confirmed install command yet — follow its own setup instructions.
IWork Studio has no declared pricing — check the project's own site. .prompts 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 iwork-studio and prompts as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, IWork Studio has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 2 GitHub stars. .prompts has 38/100 (Fair) with 5 views, 0 installs and 0 GitHub stars.
