Productivity · Integration
MVP One
Add MVP One to your product for your customers, and give your AI agents governed access to it.
Embed an MVP One integration so your customers can drive their maintenance management from inside your product instead of retyping work into a second system. MVP One is a CMMS built around assets, preventive maintenance schedules, work orders and parts, and every site names its own asset hierarchy, priorities and work types, so mapping those is configuration per customer rather than code. fastn handles per-tenant authentication, token refresh, pagination and API upkeep, so a sensor reading, an inspection failure or a tenant request in your product can raise the right work order automatically.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own MVP One account so your product raises work orders against the right asset.
Read asset records and preventive maintenance schedules so your product shows what is due and when.
Update work order status, priority and assignment as your product's workflow progresses.
Map each site's own asset hierarchy, work types and priorities per tenant, with no code on your side.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads an asset's maintenance history before it recommends an action.
An agent creates or updates a work order within governed permissions, with the write logged.
An agent reacts to a completed work order and closes the loop in your product.
Example prompt
Show overdue preventive maintenance for this site's critical assets and raise work orders for the top five.
Set up MVP One in 4 steps
- 01Open the MVP One connector from your fastn dashboard.
- 02Have each customer authenticate their own MVP One account, scoped per tenant.
- 03Map the assets, work order fields and schedules your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the MVP One integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an MVP One integration without building it. Your customers connect their own MVP One account inside your product and work their work items, assignees and due dates there, with no per-customer code on your side.
- Handle the part that actually costs time: every team configures its own fields, statuses and workflow stages. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an MVP One update is not your on-call problem.
- One integration serves your product and your agents. The same governed MVP One connection powers in-product features and gives AI agents scoped, audited access, so you keep work items in step with what happens in your product without wiring it twice.
Used by these teams
Compare with
eMaint X5
monday.comWorks well with
ServiceNowOften used alongside
Tools the same teams tend to run next to MVP One, across other categories.
Notion
Box
Docusign
AWS Simple Storage ServiceMVP One integration FAQ
How do I add an MVP One integration to my product?
Enable the MVP One connector in your fastn dashboard, then let each customer authenticate their own MVP One account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no MVP One client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own MVP One account?
Yes. Every connection is scoped to the individual customer, so each authorises their own MVP One account and only ever sees their own work items, assignees and due dates. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this MVP One integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reads an asset's maintenance history before it recommends an action.
Who maintains the MVP One integration?
fastn does. When MVP One changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can my product create and update work in MVP One automatically?
Yes. Items can be created, updated, assigned and transitioned from your product, and changes made in MVP One can trigger your workflows in return.
Does it adapt to each team's own MVP One setup?
Yes. However a team has configured MVP One, whether that is custom fields, statuses and workflow stages or its own calendars and working hours, those are mapped per customer, so an unusual setup works without custom code from you.
What can I build with the MVP One integration?
A common starting point: connect their own MVP One account so your product raises work orders against the right asset. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the MVP One integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding MVP One does not change your per-connector cost. You can start free with 3 connected accounts.
Add MVP One to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.