Build solutions, not workarounds.
What do you want Anchor and Hamsa 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 Hamsa
When New Proposal Sent in Anchor
then Add knowledge base item in Hamsa
When Agreement Amended in Anchor
then Add phone number in Hamsa
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 Hamsa
Triggers and actions 4 triggers · 27 actions
Trigger
Agreement AmendedTriggers when an agreement is amended.
Trigger
New Proposal SentTriggers when a proposal is sent to a client.
Trigger
Proposal ApprovedTriggers when a proposal is approved. The payload is the resulting agreement (a proposal becomes an agreement on approval).
Trigger
Proposal PublishedTriggers when a proposal is published.
Action
Add Service to AgreementAdds a service to a signed Anchor agreement as a new amendment.
Action
Create ContactCreates a new client contact in Anchor.
Action
Find Contact by IDLooks up a single contact by its Anchor ID.
Action
List ContactsReturns a list of contacts (client businesses), optionally filtered by search text or status.
Action
Publish ProposalPublishes a proposal draft as a proposal and, unless set to silent, emails the client.
Action
Submit ChargesSubmits charges on an agreement to issue an invoice now or schedule one for a future billing date.
Action
Add knowledge base itemCreate a new knowledge base item for a voice agent.
Action
Add phone numberAdd a phone number for a user.
Action
Add transcription jobCreate a new asynchronous job (e.g. transcription).
Action
Add TTS voiceCreate a new text-to-speech voice.
Action
Add voice agentCreate a new AI voice agent.
Action
Assign phone numberAssign a phone number to a voice agent.
Action
Delete knowledge base itemDelete a knowledge base item by ID.
Action
Delete phone numberDelete a phone number.
Action
Delete TTS voiceDelete a text-to-speech voice by ID.
Action
Get campaignGet a campaign by ID.
Action
Get conversationGet a call conversation record by ID.
Action
Get jobGet a single job's details by ID.
Action
Get voice agentRetrieve a specific voice agent by ID.
Action
Initiate voice agent callInitiate an outbound call with a voice agent via Twilio.
Action
List jobsList jobs.
Action
List knowledge base itemsReturn a list of knowledge base items.
Action
List phone numbersReturn a list of phone numbers for a user.
Action
List TTS voicesRetrieve the list of available TTS voices.
Action
List voice agentsRetrieve a list of the account's voice agents.
Action
Transcribe audioGenerate a speech-to-text transcription from audio (not streamed).
Action
Update voice agentUpdate an existing voice agent's configuration.
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 Hamsa
MySQL to HamsaConnect directly to a MySQL database and run SQL statements from your automations.
TimelinesAI to HamsaTimelinesAI allows you to share access to your personal or business Whatsapp account, integrate it with...
HubSpot to HamsaHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to HamsaSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to HamsaSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to HamsaGoogle Sheets
Questions
Anchor and Hamsa, 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 Hamsa when something happens in Anchor?
Any of Hamsa's 21 actions, including Update voice agent, Add knowledge base item, Add phone number and Add transcription job. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Hamsa to Anchor?
Hamsa has no triggers in the catalog today, so automations start in Anchor. If you need the other direction, ask: your agent reads Hamsa's API documentation and adds it.
Do I have to build a connector for Anchor or Hamsa?
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.