Build and deploy Cursor agents to your AWS or GCP cloud

Write your agent with the Cursor SDK and deploy it with Encore. It runs as a service in your own cloud account, with its database, queues, schedules and secrets provisioned for it. Start from a working agent in one click.

One stack,
from agent to cloud

Write the agent with the Cursor SDK. Encore runs it and everything it needs in your AWS or GCP account.

Agent

Cursor SDK

The agent loop runs inside your service with Agent.create. Its tools are your own typed APIs, and its conversations are stored in your database.

Custom toolsStreamingResume
Orchestration

Encore

Runs the agent as a service, wires up its Postgres, Pub/Sub, cron and secrets, and deploys it on every push. Each tool call shows up in tracing.

DeploymentsInfrastructureTracing
Your cloud

AWS and Google Cloud

The agent, its data and its secrets live in your own account. Only model calls leave it, to Cursor.

AWSGoogle Cloud

From your editor to your cloud

Build the agent like any other backend service, deploy it to your own account, and let your systems put it to work.

BUILD

Write the agent
with the Cursor SDK

The agent loop runs inside an Encore service. Its tools are typed calls to your other services, so it can do what your APIs do and nothing else. Run it locally with encore run, with a real database, before you deploy anything.

agent/runtime.ts
// Encore provisions this in your cloud.
const db = new SQLDatabase("agent", { migrations: "./migrations" });
const agent = await Agent.create({
// The user's own key, sent with the request.
apiKey: key,
model: { id: "composer-2.5" },
// Only your tools: no shell, no filesystem.
tools: ["mcp"],
local: {
cwd: WORKSPACE,
// Conversations stored in that database.
store: postgresAgentStore,
customTools: {
save_note: {
description: "Save a note for later.",
execute: ({ title, body }) =>
notes.save({ title, body }),
},
},
},
});
DEPLOY

Deploy to your AWS or GCP
in one click

Connect your AWS or GCP account and Encore provisions everything the agent declares in code, from its databases and Pub/Sub topics to its secrets. Nothing to configure by hand, and every git push redeploys it.

RUN

Every run streamed
and traced

Each message runs the agent inside your service. Its reply streams to your UI as it's written, every run is stored in your database, and each tool call shows up in tracing. Subscribe the same agent to a Pub/Sub topic or give it a cron job, and it runs on events or on a schedule too.

Remember that the offsite is on March 12 in Lisbon.
search_notesquery: "offsite"
save_notetitle: "Team offsite"
list_notes
agent · reply
Saved as “Team offsite”: March 12, in Lisbon. It's your third note.

Deploy agents to your/