Encore integrates with Cursor to let AI agents declare and provision cloud infrastructure (databases, queues, cron jobs, etc.) directly in Go or TypeScript application code, eliminating separate Terraform or config files. The platform team retains control over cost-sensitive settings like instance sizes and replica counts via the Encore dashboard, while agents work within those guardrails. An MCP server lets Cursor read real database schemas, call endpoints, and inspect traces to verify behavior. Changes and their infrastructure requirements travel together in a single pull request, with preview environments automatically provisioned per PR. Merging deploys both code and infrastructure to AWS or GCP.
Table of contents
Declaring infrastructure in the code Cursor already writesGuardrails for AWS and GCPGiving Cursor the live picture with MCPWhat the loop looks likeWhat Encore adds to your Cursor workflowThe part that was left202 Impressions