Integration
Connect Cursor and LawPay
When Agent Pull Request Created fires in Cursor, your agent runs Get Event in LawPay, or New Event in LawPay 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 LawPay 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 LawPay can do together
From Cursor to LawPay
When Agent Pull Request Created in Cursor
then Get Event in LawPay
When New Agent in Cursor
then Create Charge in LawPay
From LawPay to Cursor
When New Event in LawPay
then Add Followup Instruction to Agent in Cursor
When New Transaction in LawPay
then Launch Agent in 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 LawPay
Triggers and actions 5 triggers · 23 actions
Trigger
Agent Pull Request CreatedTriggers when the selected Cursor cloud agent opens a new GitHub pull request.
Trigger
Agent Status EqualsTriggers when a run on the chosen Cursor agent reaches the status you select, such as Finished or Error.
Trigger
New AgentTriggered when a new Cursor cloud agent is created.
Action
Add Followup Instruction to AgentSends 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 runCancels 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 AgentPermanently deletes a Cursor cloud agent. This cannot be undone. Returns the ID of the deleted agent.
Action
Find Agent StatusLooks up a Cursor cloud agent by its ID and returns its status, name, repositories, latest run and link.
Action
Get runReturns the status, timestamps, duration, final reply and pushed branches for one run of a Cursor cloud agent.
Action
Launch AgentCreates a Cursor cloud agent and immediately starts its first run on the task you describe. Returns the new agent and its run.
Action
List agentsReturns the Cursor cloud agents for the connected user, newest first, optionally filtered by pull request URL.
Action
List artifactsReturns 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 modelsReturns the recommended Cursor models you can choose from when creating an agent, including their names, aliases, parameters and variants.
Action
List repositoriesReturns the GitHub repositories the connected Cursor user can access through Cursor's GitHub App installation.
Action
List runsReturns the runs of a Cursor cloud agent, newest first, including each run's status, duration, and final reply.
Trigger
New EventTriggers when a new LawPay gateway event occurs, such as a transaction being authorized or completed.
Trigger
New TransactionTriggers when a new charge, refund or credit is created in LawPay.
Action
Cancel Recurring ChargeCancels a LawPay recurring charge so no further payments are collected.
Action
Capture ChargeCaptures an authorization-only LawPay card charge so its funds settle.
Action
Create ChargeCharges a customer in LawPay using a saved payment method or a one-time payment token.
Action
Create CreditSends funds to a customer's card or bank account in LawPay without an original charge (the Credit feature must be enabled on the account).
Action
Get Current MerchantReturns the LawPay merchant tied to the secret key, including its operating, trust and eCheck accounts.
Action
Get EventReturns one LawPay gateway event, such as a transaction being authorized, with its data.
Action
Get Recurring ChargeReturns a LawPay recurring charge with its schedule, totals and next payment date.
Action
Get TransactionReturns one LawPay charge, refund or credit by its ID, including any refunds applied to a charge.
Action
List Recurring Charge OccurrencesReturns the scheduled payments of a LawPay recurring charge with their due dates and status.
Action
Refund ChargeRefunds part or all of a LawPay charge back to the original card or bank account.
Action
Search TransactionsReturns LawPay transactions matching a text search, date range or account, newest first.
Action
Void TransactionVoids a LawPay charge, refund or credit that has not been captured yet, releasing any hold.
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 LawPay
HubSpot to LawPayHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to LawPayGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to LawPayGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to LawPayGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to LawPayGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
ActiveCampaign to LawPayActiveCampaign is a marketing automation, email marketing, and CRM platform.
Questions
Cursor and LawPay, 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 LawPay when something happens in Cursor?
Any of LawPay's 12 actions, including Create Charge, Create Credit, Capture Charge and Get Current Merchant. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from LawPay to Cursor?
Yes. When something happens in LawPay, your agent can act in Cursor too. This page covers both directions: LawPay's triggers and Cursor's actions are listed here as well.
Do I have to build a connector for Cursor or LawPay?
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 LawPay 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.