Integration
Connect CalendarLink and Cursor
When New Upcoming Event fires in CalendarLink, your agent runs Add Followup Instruction to Agent in Cursor, or Agent Pull Request Created in Cursor to List Contacts in CalendarLink. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want CalendarLink and Cursor to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne 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.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)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)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)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)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)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)Example flows
What CalendarLink and Cursor can do together
From CalendarLink to Cursor
When New Upcoming Event in CalendarLink
then Add Followup Instruction to Agent in Cursor
From Cursor to CalendarLink
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 CalendarLink and Cursor
Triggers and actions 4 triggers · 19 actions
- New Upcoming Event
Triggered when a new upcoming event is added to your CalendarLink organisation.
- Create New Event
Creates an event in a CalendarLink collection and returns its add-to-calendar link. Times use the format 2026-09-01 09:00:00. Optionally turns on RSVP with a deadline, attendee limit and notification settings.
- Find Event
Searches your CalendarLink events for one whose title contains the text you give, and returns the first match with its add-to-calendar link, times and RSVP counts.
- List Contacts
Returns a page of the contacts in your CalendarLink organisation, 15 per page, along with how many pages there are.
- List Event Collections
Returns every event collection in your CalendarLink organisation, with each collection's ID, name, description, public link and event count.
- List Event Registrations
Returns a page of the people who signed up for one CalendarLink event, 15 per page. The event must have RSVP turned on.
- List Past Events
Returns a page of your CalendarLink events that have already finished, 15 per page, newest first.
- List Upcoming Events
Returns a page of your CalendarLink events that have not happened yet, 15 per page.
- Update Event Collection
Changes the settings of one CalendarLink event collection — its name, description, appearance, what visitors can add and whether sign-up is required. Only the fields you fill in are changed; the rest keep their current values.
- Agent Pull Request Created
Triggers when the selected Cursor cloud agent opens a new GitHub pull request.
- Agent Status Equals
Triggers when a run on the chosen Cursor agent reaches the status you select, such as Finished or Error.
- New Agent
Triggered when a new Cursor cloud agent is created.
- 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.
- 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.
- Delete Agent
Permanently deletes a Cursor cloud agent. This cannot be undone. Returns the ID of the deleted agent.
- Find Agent Status
Looks up a Cursor cloud agent by its ID and returns its status, name, repositories, latest run and link.
- Get run
Returns the status, timestamps, duration, final reply and pushed branches for one run of a Cursor cloud agent.
- 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.
- List agents
Returns the Cursor cloud agents for the connected user, newest first, optionally filtered by pull request URL.
- 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.
- List models
Returns the recommended Cursor models you can choose from when creating an agent, including their names, aliases, parameters and variants.
- List repositories
Returns the GitHub repositories the connected Cursor user can access through Cursor's GitHub App installation.
- List runs
Returns the runs of a Cursor cloud agent, newest first, including each run's status, duration, and final reply.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from CalendarLink
CalendarLink to StripeStripe is a payment processing platform for online businesses.
CalendarLink to PandaDocPandaDoc helps you build and deliver sales quotes and proposals and track presentations and close deals...
CalendarLink to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
CalendarLink to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
CalendarLink to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
CalendarLink to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
More into Cursor
ActiveCampaign to CursorActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to CursorOrganize anything with Airtable, a modern database created for everyone.
Asana to CursorAsana is a collaborative information manager for workspace.
ClickUp to CursorClickUp is an all-in-one app to plan, track, and manage your work in a beautifully intuitive environment.
Brevo to CursorBrevo is the leading CRM suite designed to cultivate long-term customer relationships and help businesses...
Calendly to CursorCalendly is a scheduling automation platform for eliminating the back-and-forth emails to find the perfect...
Questions
CalendarLink and Cursor, answered
What can start an automation from CalendarLink?
Any of CalendarLink's 1 trigger in the catalog, including New Upcoming Event. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Cursor when something happens in CalendarLink?
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 CalendarLink?
Yes. When something happens in Cursor, your agent can act in CalendarLink too. This page covers both directions: Cursor's triggers and CalendarLink's actions are listed here as well.
Do I have to build a connector for CalendarLink 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 CalendarLink 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.