FibaCloud MCP
Bring cloud context into your AI workflow. FibaCloud MCP lets compatible AI applications read selected service, invoice and product category information through Model Context Protocol, with permissions you approve.
For developers and growing teams, the workflow is practical: ask about your cloud account in a compatible tool, review the returned information and keep control over access.
The beta provides three read-only tools through an OAuth connection with your primary FibaCloud account. Access is limited to the remaining duration of the current API access authorization, with a beta maximum of 3 hours; it may expire sooner. Reconnect through your application after expiry. Contact accounts and sign-in flows requiring an API MFA challenge are not supported in this beta.
What is Model Context Protocol?
Model Context Protocol (MCP) is an open protocol for connecting AI applications to external data and tools. An MCP server describes the tools it offers, their inputs and the information they return. A compatible application can then request a tool when the user needs that information.
FibaCloud MCP connects that model to your cloud account. The workflow is your AI application → FibaCloud MCP → the FibaCloud API. MCP provides the tool interface; the API remains the source of account data. The integration returns selected information for your application to use within the approved permissions.
Three tools in the beta
The beta tool set is read-only. Each connection is limited by its approved permissions.
| Tool | Permission | Information returned |
|---|---|---|
list_services | services:read | Service identifiers, names and available status information within the permitted service set. |
list_invoices | billing:read | Account invoice summaries, including available dates, totals, currencies and statuses. |
list_product_categories | catalog:read | Product category identifiers and names. |
Billing access applies to the account. The permitted service set does not restrict invoice summaries to those services. A connection that only needs service or category information should not request billing:read.
These tools do not create or delete servers, change DNS records, place orders or pay invoices. DNS zone reading is not included in this beta. The category tool lists categories; it does not provide a pricing calculator. Reported service statuses are not a live application health test.
Questions you could ask
After connecting, try questions such as:
- Service overview: “List the services I have allowed this connection to read and summarize their reported statuses.”
- Billing review: “Show the invoice summaries returned for my account, with their due dates and currencies.”
- Product discovery: “Which product categories does FibaCloud return?”
These are usage examples, not live responses. Results depend on the account, granted permissions and data returned by the API. For complete account reviews, all relevant result pages must be retrieved; a single page may contain only part of a list.
Your account and connection permissions
Start the OAuth connection from your AI application. It opens a FibaCloud sign-in page in your browser. Sign in with your existing primary FibaCloud account, review the requested permissions and approve access. You do not need a second FibaCloud account for MCP.
Check the application name and return address on the consent screen. The application supplies its own name; it is not a FibaCloud verification badge. The AI application receives a separate MCP credential rather than your account password or API token.
This beta supports primary accounts only. Contact accounts and API sign-ins that require an additional MFA challenge cannot complete the connection. Use the cloud panel or an integration supported by the current API documentation for those workflows.
Access duration and removal
Connection access lasts only for the remaining duration of its API access authorization, capped at 3 hours in the beta. It may end sooner if that authorization expires earlier. The beta does not retain or use an API refresh token to extend this duration. When access expires, reconnect from your AI application and complete browser sign-in and permission approval again.
Open My connections, sign in and choose Revoke access for a connection to stop further MCP access immediately. Revoking access does not erase information already returned to the AI application.
Tool results are supplied to the AI application you choose. Review that application's data handling before granting access, especially to billing information. Never paste your account password or API token into a chat prompt.
MCP or the REST API?
| Your task | Appropriate starting point |
|---|---|
| Build a backend, script or application with explicit API requests. | Use the FibaCloud REST API. |
| Read selected account data through a compatible AI application's tools. | Connect to the FibaCloud MCP read-only beta using the steps below. |
| Create resources, change configuration or perform other operations outside the three read-only tools. | Use the cloud panel or an operation supported by the current API documentation. |
MCP complements the REST API. It exposes a selected tool set for AI workflows rather than every operation available in the API.
Connect a compatible client
The HTTPS endpoint is https://mcp.fibacloud.com/mcp. Enter this address in your application's remote MCP server settings; it is a protocol endpoint, not a browser sign-in page.
The client must support Streamable HTTP, browser-based OAuth authorization and PKCE S256. Public OAuth Dynamic Client Registration (DCR, RFC 7591) is available. A DCR-capable client registers its own metadata and callback address; you do not need to obtain a client ID manually. The callback used during authorization must exactly match the registered address.
- Add a remote MCP server in your AI application and enter
https://mcp.fibacloud.com/mcpas its URL. - Start the application's OAuth connection flow. Sign in on the FibaCloud browser page using your primary account.
- Review the application, return address and requested permissions, then approve access and return to your application.
- Refresh the application's tool list and use the tools covered by your approved permissions. When the connection expires, repeat the sign-in flow.
Setup screens differ between clients. Support for MCP alone does not establish compatibility with this remote OAuth flow; check the client's transport, authorization and registration features. No API token or account password belongs in the server URL or a chat prompt.
Continue with FibaCloud
- API reference: review the current API and start an integration.
- Instance documentation: understand compute services and their operation.
- Domains and DNS: learn how DNS zones and records are managed.
- Getting started: find the platform setup guides.