Integration
Connect Azure DevOps to Mx Technologies
When Completed Build fires in Azure DevOps, your agent runs Add user in Mx Technologies. 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 Azure DevOps and Mx Technologies 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 Azure DevOps can start in Mx Technologies
When Completed Build in Azure DevOps
then Add user in Mx Technologies
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 Azure DevOps and Mx Technologies
Triggers and actions 5 triggers · 40 actions
- Code Push (Git)
Triggers when commits are pushed to a Git repository in an Azure DevOps project.
- Completed Build
Triggers when a build finishes in an Azure DevOps project, with its result (succeeded, failed, partially succeeded or canceled).
- New Work Item
Triggers when a work item is created in an Azure DevOps project.
- New Work Item Comment
Triggers when someone comments on a work item in an Azure DevOps project.
- Updated Work Item
Triggers when a work item is updated in an Azure DevOps project, with the work item's current values and the list of fields that changed.
- Add Link to Work Item
Adds a link to an Azure DevOps work item: a related, parent, child, predecessor, successor or duplicate link to another work item, or a hyperlink to a web page.
- Create Work Item
Creates a new work item (such as a Task, Bug, Issue or User Story) in an Azure DevOps project.
- Find Work Item
Finds work items in an Azure DevOps project that match a Work Item Query Language (WIQL) query, returning the matching work item IDs, or the matching links for a link query.
- Trigger Build
Queues a new run of an Azure DevOps build pipeline, optionally for a specific branch or commit and with pipeline variables or parameters.
- Update Work Item
Updates an existing Azure DevOps work item: changes its title, description, state, assignee, area, iteration, priority or tags, and can add a discussion comment. Fields left blank are not changed.
- Add account
Creates a manual account for an MX user. Manual accounts sit under the Manual Institution member and never aggregate data from a financial institution.
- Add budget
Creates a budget for a category on an MX user.
- Add category
Create a custom category for a user.
- Add goal
Create a goal for a user.
- Add member
Create a member (connection between a user and a financial institution) to start aggregation.
- Add transaction
Creates a manual transaction on a manual account belonging to an MX user.
- Add user
Creates a new MX user. The returned user guid is what other MX actions (such as Add member) use to identify the user.
- Aggregate member
Starts an aggregation for a member, pulling the latest account and transaction data from the connected institution. MX may skip the aggregation if the data was updated recently.
- Delete account
Delete a manually created account.
- Delete budget
Deletes a budget belonging to an MX user.
- Delete category
Delete a custom category.
- Delete goal
Delete a goal.
- Delete member
Delete a member connection.
- Delete user
Delete a user.
- Get account
Read an account's attributes.
- Get budget
Retrieves a specific budget for an MX user.
- Get institution
Read an institution's attributes.
- Get member
Read a member's attributes and connection status.
- Get merchant
Returns information about a particular merchant, such as its logo, name, and website.
- Get transaction
Read a transaction's attributes.
- Get user
Retrieves the attributes of a specific MX user.
- List accounts
Lists all accounts belonging to an MX user. Returns up to 1000 accounts in one call.
- List categories
Lists all categories for an MX user, including default and custom categories.
- List goals
Lists all goals for an MX user.
- List institutions
Lists financial institutions available through MX, optionally filtered by name, country and supported product.
- List members
List all members belonging to a user.
- List merchants
Lists merchants in the MX system, optionally filtered by a name substring.
- List transactions
List all transactions for a user.
- Update account
Updates an account belonging to a member. Manual accounts can have every field updated; aggregated accounts only accept changes to Is Business, Is Hidden and Metadata.
- Update budget
Update a specific budget.
- Update category
Update a custom category.
- Update goal
Updates an existing savings or payoff goal for an MX user. Only the fields you fill in are changed.
- Update member
Updates a member's credentials, id, metadata, background aggregation setting or use cases. At least one value to update must be supplied.
- Update transaction
Update a transaction's category, description, or other editable attributes.
- Update user
Update a user's attributes.
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 Azure DevOps
Azure DevOps to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Azure DevOps to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Azure DevOps to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Azure DevOps to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Azure DevOps to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Azure DevOps to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Mx Technologies
Questions
Azure DevOps and Mx Technologies, answered
What can start an automation from Azure DevOps?
Any of Azure DevOps's 5 triggers in the catalog, including Completed Build, New Work Item, New Work Item Comment and Updated Work Item. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Mx Technologies when something happens in Azure DevOps?
Any of Mx Technologies's 35 actions, including Update account, Update budget, Update category and Update goal. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Mx Technologies to Azure DevOps?
Mx Technologies has no triggers in the catalog today, so automations start in Azure DevOps. If you need the other direction, ask: your agent reads Mx Technologies's API documentation and adds it.
Do I have to build a connector for Azure DevOps or Mx Technologies?
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 Azure DevOps and Mx Technologies 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.