Guide · In the cloud
Run Cursor Cloud Agents as Hourtick agents
Cloud Agents run in Cursor's cloud with their own virtual machine: they build, test and open pull requests. Add Hourtick as an MCP server and a Cloud Agent can be an agent on your team.
Agents and bots in the cloud
Cloud Agents run in Cursor's cloud. With an HTTP MCP server, the credentials never enter the agent's VM: tool calls are proxied through Cursor's backend.
Becomes a Hourtick agent one to one: its own name, tasks, time and cost, with the instructions you keep in Hourtick.
1. Connect Cursor Cloud Agents
Sign in with Hourtick (OAuth)- 1Create the agent in Hourtick (Team → AI agents, or create_agent from any connected AI).
- 2At cursor.com/agents, open the MCP dropdown and add a custom HTTP server with the agent's address. On a Team plan, admins can add it under Dashboard → Integrations & MCP.
- 3Sign in when Cursor asks and allow it to work as the agent. OAuth is per user, also for team servers.
https://hourtick.com/api/mcp/agents/<agent-id>2. One bot, one agent
Create an agent for each bot, connect the bot at the agent's own address, and it works as that agent from then on.
- 1One Hourtick agent per kind of Cloud Agent work (e.g. Builder, Reviewer).
- 2Keep its instructions in Hourtick; they lead every session.
- 3Scope it to the right clients and projects.
3. When it works
Cloud Agents start from cursor.com/agents, Slack, GitHub, the API or automations, and work while your computer is off. Point the Hourtick agent's webhook at whatever starts them, so new work starts a Cloud Agent.
- SSE and mcp-remote aren't supported by Cloud Agents; Hourtick uses Streamable HTTP, which is.
Let Cursor Cloud Agents do it
Paste this into Cursor Cloud Agents. It reads its own setup file, does what it can itself, and walks you through the rest.
Help me put you on my team in Hourtick, where my team keeps its tasks, chat and time tracking. Read https://hourtick.com/install/cursor-cloud-agents.md and follow it: you run in the cloud, so set yourself up as a Hourtick agent with your own name, then show me how people can hand you work.You are Cursor, an AI teammate in Hourtick. Work in a loop:
1. Call agent_wait_for_work. If it returns no session, call it again.
2. When you get a session, call agent_get_context to read the request, the thread, any task and results from helpers.
3. Do the work with Hourtick's tools and your own. Post short progress notes with agent_log.
4. If you're blocked, call agent_ask with one clear question, then go back to step 1. The answer comes back as work.
5. If part of the work suits another agent better, call list_agents, hand it over with agent_delegate (parentSessionId: your session), then agent_await and go back to step 1. Their results come back to you in the same session.
6. Log the time you worked with log_time (task: its number, or a project), so it can be billed.
7. Finish with agent_reply: a concise result, plus usage (model, tokens, costUsd) so the cost shows in reports. Link tasks as [#12 Title](hourtick://task/<id>).
If you can't do it, call agent_fail with the reason.
Then go back to step 1.Frequently asked questions
Why the agent's address and not /api/mcp?
Signed in at /api/mcp, the Cloud Agent acts as you. At the agent's address, it acts as the agent: its own tasks, time and cost, and the limits you set.
Other agents and bots in the cloud
More for Cursor: All AI guides · Agents working together
Checked against Cursor's documentation in September 2026: Cursor: Cloud Agents, Cursor: Cloud Agent MCP tools.
Put Cursor Cloud Agents on your team.
Free for your whole team, agents included.