Build solutions, not workarounds.
What do you want MySQL 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)Your MySQL database usually knows who needs a call, what changed and which recording came in, while Hamsa runs the voice agents that do the talking. Joining them lets rows in MySQL start outbound calls, create transcription jobs, refresh knowledge base items and update agent settings, then write results back to your tables.
Example flows
What MySQL can start in Hamsa
When New or Updated Row in MySQL
then Add knowledge base item 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 MySQL and Hamsa
Triggers and actions 4 triggers · 27 actions
- New or Updated Row
Triggers when a new row is added or modified.
- New or Updated Row (Custom Query)
Fires for each new or changed row returned by a SELECT statement you write against the connected MySQL database.
- New Row
Triggers when you add a new row.
- New Table
Fires when a new table appears in the connected MySQL database.
- Add Row
Adds a new row.
- Delete Row
Delete the rows in a table whose chosen column equals a value.
- Find Row
Finds a row in a table via a lookup column.
- Find Rows via Custom Query
Run an author-written SELECT against the connected MySQL database and return every row it produced. Mirrors PostgreSQL 715ae2ac, SQL Server 8e0bbb5d and Oracle 2c308e4d; MySQL placeholder style is ?.
- Find Row via Custom Query
Runs a SELECT statement you write against the connected MySQL database and returns the first row it matches.
- Update Row
Updates an existing row.
- Add knowledge base item
Create a new knowledge base item for a voice agent.
- Add phone number
Add a phone number for a user.
- Add transcription job
Create a new asynchronous job (e.g. transcription).
- Add TTS voice
Create a new text-to-speech voice.
- Add voice agent
Create a new AI voice agent.
- Assign phone number
Assign a phone number to a voice agent.
- Delete knowledge base item
Delete a knowledge base item by ID.
- Delete phone number
Delete a phone number.
- Delete TTS voice
Delete a text-to-speech voice by ID.
- Get campaign
Get a campaign by ID.
- Get conversation
Get a call conversation record by ID.
- Get job
Get a single job's details by ID.
- Get voice agent
Retrieve a specific voice agent by ID.
- Initiate voice agent call
Initiate an outbound call with a voice agent via Twilio.
- List jobs
List jobs.
- List knowledge base items
Return a list of knowledge base items.
- List phone numbers
Return a list of phone numbers for a user.
- List TTS voices
Retrieve the list of available TTS voices.
- List voice agents
Retrieve a list of the account's voice agents.
- Transcribe audio
Generate a speech-to-text transcription from audio (not streamed).
- Update voice agent
Update 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 MySQL
MySQL to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
MySQL to MailchimpMailchimp marketing automation and email platform.
MySQL to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
MySQL to ActiveCampaignActiveCampaign is a marketing automation, email marketing, and CRM platform.
MySQL to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
MySQL to SendGridSendGrid by Twilio — email delivery and marketing platform.
More into Hamsa
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.
Slack to HamsaSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to HamsaGoogle Sheets
Gmail to HamsaGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
MySQL and Hamsa, answered
Can a row in MySQL trigger a real phone call from Hamsa?
Yes. A new or updated row in MySQL can call the Initiate voice agent call action in Hamsa, and you can first use Find Row in MySQL to pull the phone number and agent id from a related table.
Can Hamsa send call results back into MySQL?
Hamsa has no triggers here, so the flow starts in MySQL. After an action such as Initiate voice agent call or Get conversation, the agent can use Add Row or Update Row in MySQL to store the returned details.
What can start an automation from MySQL?
Any of MySQL's 4 triggers in the catalog, including New or Updated Row, New or Updated Row (Custom Query), New Row and New Table. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Hamsa when something happens in MySQL?
Any of Hamsa's 21 actions, including Add knowledge base item, Add transcription job, List voice agents and Update voice agent. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Hamsa to MySQL?
Hamsa has no triggers in the catalog today, so automations start in MySQL. 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 MySQL 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.