Integration
Connect Moxo to CMS.gov
When New Account fires in Moxo, your agent runs List dataset records in CMS.gov. 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 Moxo and CMS.gov 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 Moxo can start in CMS.gov
When New Account in Moxo
then List dataset records in CMS.gov
When New User in Moxo
then Run SQL query in CMS.gov
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 Moxo and CMS.gov
Triggers and actions 2 triggers · 21 actions
Trigger
New AccountTriggers when a new client account is created in Moxo.
Trigger
New UserTriggers when a new user (team member or client) is added to Moxo.
Action
Cancel FlowCancels a running flow.
Action
Complete StepCompletes a step in a flow, optionally with a note.
Action
Create AccountCreates a client account (company) in Moxo.
Action
Deactivate UserDeactivates a Moxo user so they can no longer sign in.
Action
Get AccountReturns one client account with its users.
Action
Get ActionReturns one action with its status and assignees.
Action
Get FlowReturns one flow with its template, status and progress.
Action
Get UserReturns one Moxo user by ID, with their name, email, kind, status, accounts and personas.
Action
List AccountsReturns the client accounts (companies) in your Moxo organization.
Action
List ConversationsReturns your conversations.
Action
List Data TablesReturns your data tables with their columns.
Action
List FlowsReturns flows, optionally filtered by status, template, account or search term.
Action
List TemplatesReturns the flow templates in your Moxo organization.
Action
Post Flow Chat MessagePosts a chat message in a flow's conversation.
Action
Send Conversation MessageSends a message to a conversation.
Action
Update AccountUpdates a client account's name, domain or status.
Action
Update UserUpdates a Moxo user's profile: name, title, department, phone or account.
Action
Find datasetsSearch the CMS Provider Data (DKAN) catalog for datasets by keyword/facets.
Action
Get datasetGet full metadata for a single CMS Provider Data dataset by identifier.
Action
List dataset recordsQuery/list rows from a single CMS Provider Data datastore resource (a dataset's distribution) with optional column/condition filters and pagination.
Action
Run SQL queryRun a read-only SQL SELECT statement against one or more CMS Provider Data datastore resources.
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 Moxo
Moxo to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Moxo to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Moxo to StripeStripe is a payment processing platform for online businesses.
Moxo to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Moxo to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Moxo to PipedrivePipedrive is a sales CRM and pipeline management tool.
More into CMS.gov
HubSpot to CMS.govHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to CMS.govSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to CMS.govSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to CMS.govGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to CMS.govGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to CMS.govGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Moxo and CMS.gov, answered
What can start an automation from Moxo?
Any of Moxo's 2 triggers in the catalog, including New Account and New User. Describe the moment in plain language and your agent picks the right one.
What can your agent do in CMS.gov when something happens in Moxo?
Any of CMS.gov's 4 actions, including Find datasets, Get dataset, List dataset records and Run SQL query. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from CMS.gov to Moxo?
CMS.gov has no triggers in the catalog today, so automations start in Moxo. If you need the other direction, ask: your agent reads CMS.gov's API documentation and adds it.
Do I have to build a connector for Moxo or CMS.gov?
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 Moxo and CMS.gov 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.