Build solutions, not workarounds.
What do you want Anchor and Leexi to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 Anchor can start in Leexi
When New Proposal Sent in Anchor
then Add meeting event in Leexi
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 Anchor and Leexi
Triggers and actions 4 triggers · 26 actions
- Agreement Amended
Triggers when an agreement is amended.
- New Proposal Sent
Triggers when a proposal is sent to a client.
- Proposal Approved
Triggers when a proposal is approved. The payload is the resulting agreement (a proposal becomes an agreement on approval).
- Proposal Published
Triggers when a proposal is published.
- Add Service to Agreement
Adds a service to a signed Anchor agreement as a new amendment.
- Create Contact
Creates a new client contact in Anchor.
- Find Contact by ID
Looks up a single contact by its Anchor ID.
- List Contacts
Returns a list of contacts (client businesses), optionally filtered by search text or status.
- Publish Proposal
Publishes a proposal draft as a proposal and, unless set to silent, emails the client.
- Submit Charges
Submits charges on an agreement to issue an invoice now or schedule one for a future billing date.
- Add meeting event
Create a meeting event (schedule a meeting to be recorded).
- Add team
Create a team in your Leexi workspace.
- Add user
Creates a user in your Leexi workspace. Requires the write_users permission scope on the API key.
- Delete meeting event
Deletes a Leexi meeting event. Requires the write_meeting_events permission scope on the API key.
- Delete team
Delete a team of the workspace.
- Delete user
Deactivates a Leexi user. Leexi never permanently deletes users: their calls and history are kept, sessions are revoked and they stop consuming a license. Deactivating an already inactive user still succeeds.
- Get call
Get a single Leexi call or meeting, including its topics, AI summary prompts, tasks and transcript.
- Get call note
Retrieve a single call note.
- Get meeting event
Retrieve a single meeting event.
- Get team
Retrieve a single team of the workspace.
- Get user
Retrieve a single user of the workspace.
- Launch meeting assistant
Sends the Leexi meeting assistant (bot) into a meeting event, or stops the bot that is already running.
- List call notes
List call notes for a given call.
- List calls
List the calls and meetings the API key can access, newest first by default, with optional filters on date, source, owner, participants, conversation type and customer contact.
- List teams
List all teams in your Leexi workspace.
- List users
List all users in your Leexi workspace.
- Request presigned recording upload URL
Requests a presigned URL for uploading a call recording before creating the call with Add call. Requires the write_calls permission scope on the API key.
- Update call note
Updates the translated text of a call note for one language. The original note text is not modified. Requires the write_calls permission on the API key.
- Update team
Update the name or active status of a team in your Leexi workspace. Only the values you fill in are changed.
- Update user
Updates a Leexi user. Only the fields you fill in are changed.
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 Anchor
Anchor to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Anchor to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Anchor to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Anchor to Google SheetsGoogle Sheets
Anchor to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Anchor to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Leexi
Questions
Anchor and Leexi, answered
What can start an automation from Anchor?
Any of Anchor's 4 triggers in the catalog, including New Proposal Sent, Agreement Amended, Proposal Approved and Proposal Published. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Leexi when something happens in Anchor?
Any of Leexi's 20 actions, including Update call note, Update team, Update user and Add meeting event. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Leexi to Anchor?
Leexi has no triggers in the catalog today, so automations start in Anchor. If you need the other direction, ask: your agent reads Leexi's API documentation and adds it.
Do I have to build a connector for Anchor or Leexi?
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.
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.