Integration
Connect JIRA to Mx Technologies
When something happens in JIRA, your agent does the next thing in Mx Technologies. Describe it 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 JIRA and Mx Technologies 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 JIRA can start in Mx Technologies
When New Issue in JIRA
then Add account in Mx Technologies
When New or Updated Issue in JIRA
then Add budget 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 JIRA and Mx Technologies
Triggers and actions 2 triggers · 173 actions
Trigger
New IssuePolls for newly created issues in a project (ordered by creation date).
Trigger
New or Updated IssuePolls for issues created or updated recently (ordered by updated date).
Action
Add attachmentadd an attachment to an issue
Action
Add commentadd a comment to an issue
Action
Add Comment to IssueAdds a comment to the specified issue.
Action
Add filter as favoriteAdd filter as favorite
Action
Add gadget to dashboardAdd gadget to dashboard
Action
Add user to groupadd a user to a group
Action
Add voteadd the current user's vote to an issue
Action
Add worklogadd a worklog to an issue
Action
Archive issues by ID or keyarchive issues by ID/key
Action
Archive issue(s) by JQLArchive issue(s) by JQL
Action
Assign IssueAssigns an issue to a user by account ID.
Action
Bulk create issuebulk create issues
Action
Bulk create statusesBulk create statuses
Action
Bulk delete issuesbulk delete issues
Action
Bulk delete StatusesBulk delete Statuses
Action
Bulk delete worklogsbulk delete worklogs on an issue
Action
Bulk edit dashboardsBulk edit dashboards
Action
Bulk edit issuesbulk edit issue fields
Action
Bulk fetch issuesbulk fetch issues by ID/key
Action
Bulk move issuesbulk move issues
Action
Bulk move worklogsbulk move worklogs
Action
Bulk transition issue statusesbulk transition issue statuses
Action
Bulk unwatch issuesbulk unwatch issues
Action
Bulk watch issuesbulk watch issues
Action
Change filter ownerChange filter owner
Action
Copy dashboardCopy dashboard
Action
Create componentCreate component
Action
Create custom fieldCreate custom field
Action
Create dashboardCreate dashboard
Action
Create filterCreate filter
Action
Create groupCreate group
Action
Create IssueCreates a new issue in the specified project.
Action
Create issue linkcreate a link between two issues
Action
Create issue link typecreate an issue link type
Action
Create issue typecreate an issue type
Action
Create projectcreate a project
Action
Create project categorycreate a project category
Action
Create related workCreate related work
Action
Create usercreate a user
Action
Create versionCreate version
Action
Delete and replace versionDelete and replace version
Action
Delete attachmentdelete an attachment
Action
Delete commentdelete a comment
Action
Delete componentDelete component
Action
Delete custom fieldDelete custom field
Action
Delete dashboardDelete dashboard
Action
Delete filterDelete filter
Action
Delete IssueDeletes an issue by its key or ID.
Action
Delete issue linkdelete an issue link
Action
Delete issue link typedelete an issue link type
Action
Delete issue typedelete an issue type
Action
Delete projectdelete a project
Action
Delete project asynchronouslydelete a project asynchronously
Action
Delete project categorydelete a project category
Action
Delete related workDelete related work
Action
Delete userdelete a user
Action
Delete versionDelete version
Action
Delete voteremove the current user's vote from an issue
Action
Delete watcherremove a watcher from an issue
Action
Delete worklogdelete a worklog
Action
Export Archived IssuesExport archived issue(s)
Action
Get all dashboardsGet all dashboards
Action
Get all projectsGet all projects
Action
Get attachment contentget attachment content
Action
Get attachment metadataget attachment metadata
Action
Get available transitionsGet available transitions
Action
Get bulk available transitionsget transitions available for bulk transition
Action
Get commentget a single comment
Action
Get comments by IDsget comments by IDs
Action
Get componentGet component
Action
Get create issue metadataGet create issue metadata
Action
Get create metadata issue types for a projectget create-metadata issue types for a project
Action
Get custom fieldFetches a custom field's definition by its ID, including its name, description and field type. Returns found = false when no field has that ID.
Action
Get dashboardGet dashboard
Action
Get edit issue metadataget edit metadata for an issue
Action
Get favorite filtersGet favorite filters
Action
Get filterGet filter
Action
Get groupGet group
Action
Get IssueReturns the details of a single issue by its key or ID.
Action
Get Issue CommentsReturns all comments for the specified issue.
Action
Get issue linkget an issue link
Action
Get issue link typeget an issue link type
Action
Get issue link typeslist issue link types
Action
Get Issue TransitionsReturns the workflow transitions available for the specified issue.
Action
Get issue typeget an issue type
Action
Get issue watchersget watchers of an issue
Action
Get issue worklogsget worklogs on an issue
Action
Get is watching issue bulkcheck watching status for multiple issues
Action
Get my filtersGet my filters
Action
Get ProjectReturns the details of a single project by its key or ID.
Action
Get project categoryFetches a project category by ID, with its name and description. An error occurs if the category is not found.
Action
Get project componentsget all components of a project
Action
Get project versionsget all versions of a project
Action
Get recent projectsget recently viewed projects
Action
Get related workGet related work
Action
Get statusGet status
Action
Get status categoryGet status category
Action
Get transitionsget available transitions for an issue
Action
Get userget a user
Action
Get user groupsget groups a user belongs to
Action
Get users from grouplist members of a group
Action
Get versionGet version
Action
Get votesget votes on an issue
Action
Get worklogget a worklog
Action
Get worklogs by IDsget worklogs by IDs
Action
Get worklogs by issue ID and worklog IDget worklogs by issue ID and worklog ID (internal)
Action
List Project Issue TypesReturns the issue types available, optionally for a given project.
Action
List ProjectsReturns a paginated list of projects visible to the user.
Action
List usersLists the users visible to the connected Jira account. Takes no search criterion.
Action
Merge versionsmerge one version into another
Action
Move versionMove version
Action
Remove filter as favoriteRemove filter as favorite
Action
Remove gadget from dashboardRemove gadget from dashboard
Action
Remove groupRemove group
Action
Remove user from groupremove a user from a group
Action
Restore custom field from trashRestore custom field from trash
Action
Restore deleted or archived projectrestore a deleted or archived project
Action
Search for dashboardsSearch for dashboards
Action
Search for filtersSearch for filters
Action
Search for issues using JQL enhanced search (GET)Search for issues using JQL enhanced search (GET)
Action
Search for issues using JQL enhanced search (POST)search for issues using enhanced JQL (POST)
Action
Search Issues (JQL)Searches for issues using a JQL query.
Action
Transition IssueMoves an issue to a new status by performing a workflow transition.
Action
Unarchive issues by keys or IDunarchive issues by key/ID
Action
Update commentupdate a comment
Action
Update componentUpdate component
Action
Update custom fieldUpdate custom field
Action
Update dashboardUpdate dashboard
Action
Update filterUpdate filter
Action
Update gadget on dashboardUpdate gadget on dashboard
Action
Update Issueedit an issue
Action
Update issue link typeupdate an issue link type
Action
Update issue typeupdate an issue type
Action
Update projectupdate a project
Action
Update project categoryupdate a project category
Action
Update related workUpdate one related-work link on a Jira project version. Reads the version's existing related work, overlays only the fields you supply, then writes the merged object back — so anything you leave blank keeps its current value.
Action
Update versionUpdate version
Action
Update worklogupdate a worklog
Action
Add accountCreates a manual account for an MX user. Manual accounts sit under the Manual Institution member and never aggregate data from a financial institution.
Action
Add budgetCreates a budget for a category on an MX user.
Action
Add categoryCreate a custom category for a user.
Action
Add goalCreate a goal for a user.
Action
Add memberCreate a member (connection between a user and a financial institution) to start aggregation.
Action
Add transactionCreates a manual transaction on a manual account belonging to an MX user.
Action
Add userCreates a new MX user. The returned user guid is what other MX actions (such as Add member) use to identify the user.
Action
Aggregate memberStarts 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.
Action
Delete accountDelete a manually created account.
Action
Delete budgetDeletes a budget belonging to an MX user.
Action
Delete categoryDelete a custom category.
Action
Delete goalDelete a goal.
Action
Delete memberDelete a member connection.
Action
Delete userDelete a user.
Action
Get accountRead an account's attributes.
Action
Get budgetRetrieves a specific budget for an MX user.
Action
Get institutionRead an institution's attributes.
Action
Get memberRead a member's attributes and connection status.
Action
Get merchantReturns information about a particular merchant, such as its logo, name, and website.
Action
Get transactionRead a transaction's attributes.
Action
Get userRetrieves the attributes of a specific MX user.
Action
List accountsLists all accounts belonging to an MX user. Returns up to 1000 accounts in one call.
Action
List categoriesLists all categories for an MX user, including default and custom categories.
Action
List goalsLists all goals for an MX user.
Action
List institutionsLists financial institutions available through MX, optionally filtered by name, country and supported product.
Action
List membersList all members belonging to a user.
Action
List merchantsLists merchants in the MX system, optionally filtered by a name substring.
Action
List transactionsList all transactions for a user.
Action
Update accountUpdates 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.
Action
Update budgetUpdate a specific budget.
Action
Update categoryUpdate a custom category.
Action
Update goalUpdates an existing savings or payoff goal for an MX user. Only the fields you fill in are changed.
Action
Update memberUpdates a member's credentials, id, metadata, background aggregation setting or use cases. At least one value to update must be supplied.
Action
Update transactionUpdate a transaction's category, description, or other editable attributes.
Action
Update userUpdate 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 JIRA
JIRA to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
JIRA to Google SheetsGoogle Sheets
JIRA to Google DriveGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
JIRA to MailchimpMailchimp marketing automation and email platform.
JIRA to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
JIRA to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
More into Mx Technologies
HubSpot to Mx TechnologiesHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Mx TechnologiesSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Mx TechnologiesSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Mx TechnologiesGoogle Sheets
Gmail to Mx TechnologiesGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Mx TechnologiesGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
JIRA and Mx Technologies, answered
What can start an automation from JIRA?
Any of JIRA's 2 triggers in the catalog, including New Issue and New or Updated Issue. 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 JIRA?
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 JIRA?
Mx Technologies has no triggers in the catalog today, so automations start in JIRA. 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 JIRA 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.
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.