Integration
Connect Siteleaf to Mx Technologies
When something happens in Siteleaf, 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 Siteleaf 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 Siteleaf can start in Mx Technologies
When New Collection in Siteleaf
then Add account 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 Siteleaf and Mx Technologies
Triggers and actions 4 triggers · 52 actions
- New Collection
Triggered when a new collection is created.
- New Document
Triggered when a new document is created.
- New Page
Triggered when a new page is created.
- New Site
Triggered when a new site is created.
- Add Collection
Create a new collection on a site.
- Create Document
Creates a new document.
- Create Page
Creates a new page.
- Delete Collection
Delete a collection.
- Delete Document
Delete a document.
- Delete Page
Delete a page.
- Get Document
Get a single document by id.
- Get Page
Get a single page by id.
- Get Site
Get a single site by id.
- List Collections
List collections for a site.
- List Documents
List documents in a collection, filterable by search/visibility/extensions.
- List Pages
List pages for a site, filterable by search/visibility/extensions.
- List Sites
List all sites for the authenticated user.
- Update Collection
Update a collection's title/path/metadata.
- Update Document
Update an existing document's title/body/tags/categories/metadata.
- Update Page
Update an existing page's title/body/metadata.
- Update Site
Update a site's settings.
- 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 Siteleaf
Siteleaf to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Siteleaf to StripeStripe is a payment processing platform for online businesses.
Siteleaf to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
Siteleaf to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Siteleaf to TwilioCloud communications platform for sending SMS/MMS messages, making and managing voice calls, and looking up...
Siteleaf to TypeformBuild and publish online forms, surveys, and quizzes with Typeform.
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.
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
Siteleaf and Mx Technologies, answered
What can start an automation from Siteleaf?
Any of Siteleaf's 4 triggers in the catalog, including New Collection, New Document, New Page and New Site. 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 Siteleaf?
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 Siteleaf?
Mx Technologies has no triggers in the catalog today, so automations start in Siteleaf. 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 Siteleaf 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.