--- title: "Connect Clerk and Cursor - APIANT.ai" description: "When \"New User\" fires in Clerk, your agent runs \"Add Followup Instruction to Agent\" in Cursor." canonical: "https://apiant.ai/connect/clerk-to-cursor" --- # Connect Clerk and Cursor When **New User** fires in [Clerk](https://apiant.ai/connections/clerk), your agent runs **Add Followup Instruction to Agent** in [Cursor](https://apiant.ai/connections/cursor), or **Agent Pull Request Created** in Cursor to **Create User** in Clerk. Describe the whole flow and it is built, tested on every scenario and kept running. Clerk **1** trigger Clerk **6** actions Cursor **3** triggers Cursor **11** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Clerk and Cursor to do together? Give your AI client this address. `https://mcp.apiant.ai` One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser. ### Set it up in your client ### Claude Code Run this in the directory you want to work in. `claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai` Start Claude Code there, approve the server, and sign in in the browser page it opens. [Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code) ### Claude, web and desktop Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Cursor Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Zed Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Codex and the ChatGPT desktop app Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Any other MCP client Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) Example flows ## What Clerk and Cursor can do together ### From Clerk to Cursor - When **New User** in Clerk then **Add Followup Instruction to Agent** in Cursor - When **New User** in Clerk then **Launch Agent** in Cursor ### From Cursor to Clerk - When **Agent Pull Request Created** in Cursor then **Create User** in Clerk - When **New Agent** in Cursor then **Update User** in Clerk Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships. Everything your agent can do with Clerk and Cursor ## Triggers and actions 4 triggers · 17 actions - Trigger **New User** Triggers when a new user is created in Clerk. - Action **Ban User** Ban a user, preventing them from signing in. - Action **Create Invitation** Invite a new user to the Clerk instance by email; they receive a sign-up link. - Action **Create User** Creates a new user in Clerk. - Action **Delete User** Deletes a user from Clerk. - Action **Unban User** Remove a ban on a user, restoring their ability to sign in. - Action **Update User** Updates an existing user in Clerk. - Trigger **Agent Pull Request Created** Triggers when the selected Cursor cloud agent opens a new GitHub pull request. - Trigger **Agent Status Equals** Triggers when a run on the chosen Cursor agent reaches the status you select, such as Finished or Error. - Trigger **New Agent** Triggered when a new Cursor cloud agent is created. - Action **Add Followup Instruction to Agent** Sends a follow-up instruction to an existing Cursor cloud agent, either starting a new run or steering the run in progress. Returns the new run or how the steer was delivered. - Action **Cancel run** Cancels the active run of a Cursor cloud agent. The run ends in the Cancelled state; start a new run to continue the conversation. - Action **Delete Agent** Permanently deletes a Cursor cloud agent. This cannot be undone. Returns the ID of the deleted agent. - Action **Find Agent Status** Looks up a Cursor cloud agent by its ID and returns its status, name, repositories, latest run and link. - Action **Get run** Returns the status, timestamps, duration, final reply and pushed branches for one run of a Cursor cloud agent. - Action **Launch Agent** Creates a Cursor cloud agent and immediately starts its first run on the task you describe. Returns the new agent and its run. - Action **List agents** Returns the Cursor cloud agents for the connected user, newest first, optionally filtered by pull request URL. - Action **List artifacts** Returns the files a Cursor cloud agent has produced, with each file's path, size and last modified time. Returns at most 100 artifacts. - Action **List models** Returns the recommended Cursor models you can choose from when creating an agent, including their names, aliases, parameters and variants. - Action **List repositories** Returns the GitHub repositories the connected Cursor user can access through Cursor's GitHub App installation. - Action **List runs** Returns the runs of a Cursor cloud agent, newest first, including each run's status, duration, and final reply. ## Each app on its own - [ **Clerk** Clerk is a user authentication and management platform that lets developers add sign-in, profiles, and...](https://apiant.ai/connections/clerk) - [ **Cursor** Cursor is an AI-powered code editor that understands your codebase, supports natural-language coding...](https://apiant.ai/connections/cursor) Reviews ## What our customers say ## More from Clerk - [ **Clerk to LinkedIn** LinkedIn is a professional networking platform enabling job seekers, companies, and thought leaders to...](https://apiant.ai/connect/clerk-to-linkedin) - [ **Clerk to Facebook** Facebook is a social media and advertising platform used by individuals and businesses to connect, share...](https://apiant.ai/connect/clerk-to-facebook) - [ **Clerk to Anthropic** Anthropic builds Claude, a family of large language models.](https://apiant.ai/connect/clerk-to-anthropic) - [ **Clerk to GoHighLevel** All-in-one sales and marketing platform agencies white-label and resell to their clients — contacts...](https://apiant.ai/connect/clerk-to-gohighlevel) - [ **Clerk to Supabase** Supabase is an open-source backend-as-a-service providing a Postgres database, authentication, storage, and...](https://apiant.ai/connect/clerk-to-supabase) - [ **Clerk to ElevenLabs** ElevenLabs is an AI audio research and deployment company.](https://apiant.ai/connect/clerk-to-elevenlabs) ## More into Cursor - [ **ActiveCampaign to Cursor** ActiveCampaign is a marketing automation, email marketing, and CRM platform.](https://apiant.ai/connect/activecampaign-to-cursor) - [ **Airtable to Cursor** Organize anything with Airtable, a modern database created for everyone.](https://apiant.ai/connect/airtable-to-cursor) - [ **Asana to Cursor** Asana is a collaborative information manager for workspace.](https://apiant.ai/connect/asana-to-cursor) - [ **ClickUp to Cursor** ClickUp is an all-in-one app to plan, track, and manage your work in a beautifully intuitive environment.](https://apiant.ai/connect/clickup-to-cursor) - [ **Brevo to Cursor** Brevo is the leading CRM suite designed to cultivate long-term customer relationships and help businesses...](https://apiant.ai/connect/brevo-to-cursor) - [ **Calendly to Cursor** Calendly is a scheduling automation platform for eliminating the back-and-forth emails to find the perfect...](https://apiant.ai/connect/calendly-to-cursor) Questions ## Clerk and Cursor, answered ### ### What can start an automation from Clerk? Any of Clerk's 1 trigger in the catalog, including New User. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Cursor when something happens in Clerk? Any of Cursor's 11 actions, including Add Followup Instruction to Agent, Find Agent Status, Get run and Launch Agent. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Cursor to Clerk? Yes. When something happens in Cursor, your agent can act in Clerk too. This page covers both directions: Cursor's triggers and Clerk's actions are listed here as well. ### ### Do I have to build a connector for Clerk or Cursor? No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running. ### ### Can my AI client use Clerk and Cursor without building an automation? Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both. ### ### What happens when something fails? Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships. ### ### Is there a free plan? Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.