About Fiix MCP by usefulapi
Fiix MCP by usefulapi is a hosted server for accessing Fiix accounts from MCP clients. It provides read-only lookup of maintenance and account records, with OAuth-based sign-in and no local installation.
Key features
- 01Find Fiix objects
- 02Read objects by ID
- 03Count objects
- 04Access work orders, assets, purchases and accounts
Use cases
- 01Look up a work order or asset
- 02Count records in Fiix
- 03Review purchase orders and accounts
MCP support
Exposes Fiix search, retrieval and counting tools to MCP clients. It is a hosted remote MCP server and uses OAuth sign-in.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://fiix.usefulapi.io/mcpclaude mcp add --transport http io-usefulapi-fiix https://fiix.usefulapi.io/mcp{"mcpServers":{"io-usefulapi-fiix":{"type":"http","url":"https://fiix.usefulapi.io/mcp"}}}Open in Cursor{"servers":{"io-usefulapi-fiix":{"type":"http","url":"https://fiix.usefulapi.io/mcp"}}}Open in VS Code{"mcpServers":{"io-usefulapi-fiix":{"type":"http","url":"https://fiix.usefulapi.io/mcp"}}}{"mcpServers":{"io-usefulapi-fiix":{"serverUrl":"https://fiix.usefulapi.io/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEFiix MCP by usefulapi
Use your Fiix account from Claude, Cursor, or any MCP client. It reads work orders, assets, purchase orders and accounts, and it changes nothing. Hosted, no local install: connect with your own credentials.
Live endpoint: https://fiix.usefulapi.io/mcp · Homepage: https://usefulapi.io
Connect
- Claude (claude.ai, Desktop): open Customize → Connectors, click + Add → Add custom connector, and paste
https://fiix.usefulapi.io/mcp. - Claude Code:
claude mcp add --transport http fiix https://fiix.usefulapi.io/mcp, then run/mcpto log in. - VS Code: Add to VS Code.
- Cursor and other clients: add the URL as a remote MCP server:
{
"mcpServers": {
"fiix": {
"url": "https://fiix.usefulapi.io/mcp"
}
}
}
Add only the URL. Do not add an Authorization header or an API key to the client config: the server signs you in with OAuth, and the login page asks for your Fiix credentials.
Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/fiix/
On first connect you provide your Fiix subdomain (the part before .macmms.com), an Application Key, an Access Key and a Secret Key. A Fiix administrator creates the keys under Settings → Connect Management → Fiix API Application Settings, and the API needs a Fiix Enterprise plan. The server validates them and stores them per user. No keys go in config files.
Tools
| Tool | Type | What it does |
|---|---|---|
fiix_find_objects | read | Find objects |
fiix_get_object | read | Get object by id |
fiix_count_objects | read | Count objects |
fiix_usage_status | meta | Usage status (free-tier meter) |
fiix_request_feature | meta | Request a missing feature |
fiix_upgrade | meta | Upgrade to Pro or Pro+ |
fiix_cancel_subscription | meta | Cancel the Pro subscription |
read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.
Pricing
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Pro (per user) | $9/mo or $90/yr (2 months free) | Unlimited* |
*Pro has a fair use limit of 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this server only. Subscribe with fiix_upgrade (it returns a Stripe Checkout link). Cancel any time with fiix_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running fiix_upgrade before then undoes the cancel. Or write to [email protected].
License
MIT — see LICENSE. Documentation only; the server is hosted.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.