Connect the MCP server
Give an MCP client scoped Prosewire tools with explicit read, mutation, and destructive-operation metadata.
Install
pnpm add --global @prosewire/mcpThe MCP server supports Node.js 24 or newer and communicates over stdio.
Configure a client
Create a publication-scoped key in Settings → Developer. Start with
content:read; add content:write only when the client must change content.
{
"mcpServers": {
"prosewire": {
"command": "prosewire-mcp",
"env": {
"PROSEWIRE_API_URL": "https://your-prosewire-deployment",
"PROSEWIRE_API_KEY": "pw_live_..."
}
}
}
}Do not commit client configuration containing a real key.
Restart the MCP client after changing the command or environment. If the server exits during startup, run prosewire-mcp in a shell with the same environment to surface configuration or connectivity errors.
Tool safety
| Tools | Classification | Behavior |
|---|---|---|
publication_get, posts_list, posts_get | Read-only | Retrieve publication or post data without persistence |
posts_create, posts_update | Mutating | Write content and require client approval |
posts_archive | Destructive | Remove a post from public surfaces and require client approval |
The server advertises read-only, idempotent, destructive, and approval metadata to MCP clients. Client support for those annotations varies, so confirm the target post and intended change before approving any mutation, especially an archive.
The API key determines the publication boundary. The optional blog argument on posts_list cannot broaden that boundary to another publication.