Integration
Connect MOCO to Instatus
When New Client fires in MOCO, your agent runs Add component in Instatus. 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 MOCO and Instatus 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 MOCO can start in Instatus
When New Client in MOCO
then Add component in Instatus
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 MOCO and Instatus
Triggers and actions 26 triggers · 38 actions
- New Client
Triggers when a new client is created.
- New Company
Triggers when a new company is created.
- New Expense
Triggers when an expense is created.
- New Exported Invoice (Bookkeeping)
Triggers when a new invoice is exported (for the bookkeeping).
- New Incoming Payment
Triggers when a new incoming payment is created.
- New Invoice
Triggers when a new invoice is created.
- New Invoice Status
Triggers when the status of an invoice is changed.
- New Offer
Triggers when a new offer is created.
- New Outgoing Payment
Triggers when a new outgoing payment is created.
- New Planning Entry
Triggers when a new Planning Entry is created.
- New Presence
Triggers when a new Presence is created.
- New Project Assignment
Triggers when a person is assigned to a project.
- New Purchase
Triggers when a new purchase is created.
- New Recurred Expense
Triggers when an expense is recurred.
- New Task
Triggers when a new task is created.
- New Time Entry
Triggers when a new time entry is created.
- Unarchived Project
Triggers when a project is made active again.
- Updated Company
Triggers when a company was updated.
- Updated Expense
Triggers when an expense was updated.
- Updated Invoice
Triggers when an invoice was updated.
- Updated Lead
Triggers when a lead was updated.
- Updated Planning Entry
Triggers when a Planning Entry was updated.
- Updated Presence
Triggers when a Presence was updated.
- Updated Project
Triggers when a project was updated.
- Updated Purchase
Triggers when a purchase was updated.
- Updated Time Entry
Triggers when a time entry was updated.
- Create Comment
Creates a new Comment.
- Create Company
Creates a new company (customer only).
- Create Contact
Creates a new contact person.
- Create Expense
Creates a new Expense.
- Create Incoming Payment
Creates a new incoming payment.
- Create Lead
Creates a new lead.
- Create Outgoing Payment
Creates a new outgoing payment.
- Create Project
Creates a new Project.
- Create Purchase
Creates a new Purchase.
- Create Task
Creates a new project task.
- Create Time Entry
Create a new time entry.
- Find Company
Finds an existing Company.
- Find Contact
Finds an existing Contact.
- Find Expense
Finds an existing Expense.
- Find Invoice
Finds an existing Invoice.
- Find Lead
Finds an existing lead.
- Find Offer
Finds an existing Offer.
- Find Planning Entry
Finds an existing Planning Entry.
- Find Project
Finds an existing project.
- Find Purchase
Finds an existing Purchase.
- Find Task
Finds an active Task for a Project.
- Find Time Entry
Finds an existing Time Entry.
- Find User
Finds an existing active user.
- Record Presence
Record a new presence.
- Add component
Creates a new component on an Instatus status page and returns the created component.
- Add incident update
Posts a new update to an existing incident on an Instatus status page, optionally changing the incident status and affected component statuses.
- Add maintenance
Schedules a new maintenance on an Instatus status page, with its affected components, timing and subscriber notification options.
- Add subscriber
Adds a subscriber (by email or phone) to a status page, subscribed to all components or to specific ones.
- Create Incident
Creates a new incident on an Instatus status page, optionally marking affected components and notifying subscribers.
- Delete incident
Deletes an incident from an Instatus status page.
- Get component
Returns one component on an Instatus status page, including its name, current status, description and group.
- Get incident
Returns a single incident on a status page, including its updates, affected components and the teammate who created it.
- Get maintenance
Returns one scheduled maintenance on a status page, including its updates and affected components.
- List components
Returns the components on an Instatus status page, with each component's name, status and group.
- List maintenances
Returns the scheduled, in-progress and completed maintenances on an Instatus status page.
- List status pages
Returns the status pages in your Instatus account, including each page's id, name, subdomain and current status.
- List subscribers
Returns the subscribers of an Instatus status page, optionally filtered by email/phone search or subscription status.
- Update component
Updates a component on an Instatus status page, such as its name, description, status, order or group.
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 MOCO
MOCO to ip-apiip-api resolves an IP address or domain name to a physical location.
MOCO to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
MOCO to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
MOCO to StripeStripe is a payment processing platform for online businesses.
MOCO to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
MOCO to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Instatus
HubSpot to InstatusHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to InstatusGoogle Sheets
Gmail to InstatusGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to InstatusGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
MOCO and Instatus, answered
What can start an automation from MOCO?
Any of MOCO's 26 triggers in the catalog, including New Client, New Company, New Expense and New Exported Invoice (Bookkeeping). Describe the moment in plain language and your agent picks the right one.
What can your agent do in Instatus when something happens in MOCO?
Any of Instatus's 14 actions, including Create Incident, Update component, Add component and Add incident update. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Instatus to MOCO?
Instatus has no triggers in the catalog today, so automations start in MOCO. If you need the other direction, ask: your agent reads Instatus's API documentation and adds it.
Do I have to build a connector for MOCO or Instatus?
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.