Expose deployment tools while leaving billing writes unavailable
At a glance
A platform builder let Claude and Cursor deploy and update projects through MCP with a deliberately limited tool surface. This workflow is listed under deployment, tool-permissions, audit-logs, agent-integration.
The integration exposes project creation, deployment, updates, domain changes and file operations. Billing write tools and account-management tools are absent. Actions are rate-limited, logged and passed through the platform's deployment scans.
How it went
The author reports deployments taking about two minutes and says repeated updates to the same link became the workflow they used most.
Worth knowing
The permission boundary is enforced by which tools exist, not only by instructions telling the model to avoid billing actions.
Save ideas in this browser. Upvotes count across the board.
Oct 15 release expands Mercury MCP from read to write: ChatGPT/Claude/Cursor can request sends/transfers and categorize expenses, but money only moves after Mercury-app approval.
Open-source TypeScript beta for agentic apps: define a capability once and expose it to UI, agent, HTTP, CLI, MCP, and A2A so Claude/ChatGPT/Cursor can call the same actions humans click—skip screen-scraping computer-use for lower tokens.
Stable open-source Azure MCP 3.0 adds Backup, Resilience, SRE Agent, Terraform/Advisor, Monitor/Cosmos/IoT toolsets plus clearer schemas, --learn, and secure-by-default resource creation so Copilot/Cursor/Claude agents can inspect and plan Azure work with predictable contracts.