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 Integrate → Scoped API keys. 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, posts_revisions_list, media_list | Read-only | Retrieve publication, post, revision, media reference, or quota data without persistence |
posts_create, posts_update, media_upload_start, media_upload_complete | Mutating | Write content or reserve and process storage; require client approval |
posts_revision_restore, posts_archive, media_delete | Destructive | Restore saved content, remove a post from public surfaces, or delete unreferenced primary media; 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 asserts that its slug or UUID matches the key’s publication; a mismatch is rejected.
The MCP upload tools deliberately split reservation and completion. The client must send the file itself to the signed URL between those calls using the returned method and headers. Do not pass image bytes through the MCP tool input. media_delete fails while a current post references the asset.
publication_import streams a local file and optional mediaFile to the scoped publication. Its required mode is preview or apply; preserveStates defaults to false, so imported posts remain drafts. The tool requires approval and never overwrites existing content. See portable import for limits and retry policy.