Integration
Connect Cursor and Grist
When Agent Pull Request Created fires in Cursor, your agent runs Create or Update Record in Grist, or New or Updated Record in Grist to Add Followup Instruction to Agent in Cursor. 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 Cursor and Grist 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 Cursor and Grist can do together
From Cursor to Grist
When Agent Pull Request Created in Cursor
then Create or Update Record in Grist
From Grist to Cursor
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 Cursor and Grist
Triggers and actions 7 triggers · 32 actions
- 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.
- New or Updated Record
Triggered when a row in a Grist table is created or updated.
- New or Updated Record (Instant)
Triggers when a Record is updated, or a new Record is added.
- New Record
Triggered when a new row is added to a Grist table.
- New Record (Instant)
Triggers when a new Record is created
- Add Column
Adds a column to a table in a Grist document.
- Add Table
Creates a new table in a Grist document, optionally with a starting set of columns.
- Create Document
Creates a new document in a Grist workspace and returns its document ID.
- Create or Update Record
Adds a row to a Grist table, or updates the existing row when the match column already holds the match value. Returns the row ID.
- Create Record
Adds a new row to a Grist table and returns its row ID.
- Create Workspace
Creates a new workspace in a Grist organization and returns its ID.
- Delete Document
Deletes a Grist document permanently.
- Delete Records
Deletes one or more rows from a Grist table by row ID.
- Delete Workspace
Deletes a Grist workspace along with every document inside it.
- Find Record
Searches a Grist table for a row whose column holds a given value and returns that row's ID and column values.
- Get Document
Returns the details of one Grist document — its name, web address, workspace, and organization.
- Get Org
Returns the details of one Grist organization (team site) — its name, subdomain, owner, and your access level.
- Get Workspace
Returns the details of one Grist workspace, including the documents it contains.
- List Columns
Returns the columns of a Grist table, with each column's ID, label, and type.
- List Orgs
Returns every Grist organization (team site) this connection can reach.
- List Tables
Returns the tables in a Grist document.
- List Workspaces
Returns the workspaces in a Grist organization, each with the documents it contains.
- Run SQL Query
Runs a read-only SELECT statement against a Grist document and returns the rows.
- Update Document
Renames a Grist document or changes whether it is pinned. Anything left blank stays as it is.
- Update Record
Changes the column values of one row in a Grist table. Columns left blank keep their current values.
- Update Workspace
Renames a Grist workspace.
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 Cursor
Cursor to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Cursor to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Cursor to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Cursor to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Cursor to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Cursor to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Grist
MySQL to GristConnect directly to a MySQL database and run SQL statements from your automations.
Fillout Forms to GristCreate powerful forms, surveys and quizzes your audience will answer with Fillout Forms.
Google Tasks to GristGoogle Tasks provides a simple to-do list and task management system integrated into Gmail and Google...
ActiveCampaign to GristActiveCampaign is a marketing automation, email marketing, and CRM platform.
Questions
Cursor and Grist, answered
What can start an automation from Cursor?
Any of Cursor's 3 triggers in the catalog, including Agent Pull Request Created, New Agent and Agent Status Equals. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Grist when something happens in Cursor?
Any of Grist's 21 actions, including Create Document, Create or Update Record, Create Record and Create Workspace. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Grist to Cursor?
Yes. When something happens in Grist, your agent can act in Cursor too. This page covers both directions: Grist's triggers and Cursor's actions are listed here as well.
Do I have to build a connector for Cursor or Grist?
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 Cursor and Grist 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.