MCP for AI assistants

Connect your AI assistant to your cloud

Give Claude, Cursor or another MCP-compatible assistant tools for servers, networks, databases and DNS. Its access is limited by the permissions of your token.

Connect

Three steps, then just ask

  1. 01

    Create a token

    In the dashboard under Team → API tokens. Limit it to the areas, projects or services your assistant should touch.

  2. 02

    Add the server

    Point your assistant at https://api.faastic.com/mcp, with the token as a bearer header.

  3. 03

    Ask in plain language

    Your assistant picks the tools. Anything destructive is marked, so a good client checks with you first.

MCP configuration json
{
  "mcpServers": {
    "faastic": {
      "type": "http",
      "url": "https://api.faastic.com/mcp",
      "headers": { "Authorization": "Bearer fst_…" }
    }
  }
}

Most MCP clients accept this shape. Your client's settings may name the fields slightly differently.

In practice

One sentence, three tool calls

You

“Show me my databases, create a read-only user for the reporting tool, and tell me when the last backup ran.”

What your assistant calls

  1. 1
    list_managed_databases

    Finds your databases.

  2. 2
    create_database_user

    Creates the user with the read-only role. The password comes back once.

  3. 3
    list_database_backups

    Reads the backup list, with times and sizes.

When your assistant wants to buy something, like a new server, the order needs a token with billing rights. If yours doesn't have them, nothing gets bought. That's on purpose.

Built on the API

The same rules as your scripts

  • More than 120 tools

    Servers, networks, firewalls, load balancers, databases, DNS, domains and orders, each one a real API endpoint.

  • Your token, your limits

    Tools run with the caller's token. Roles, validation and rate limits are exactly those of the REST API.

  • Spending needs billing rights

    Orders and payments need a token that includes billing.

  • Logged as you

    Every change appears in your activity log, next to the token that made it.

  • Destructive tools are flagged

    Tools that delete or overwrite data are marked, so clients can check with you first.

  • Nothing out of reach

    Anything without its own tool is still reachable through a generic call_api tool, with list_api_endpoints to find it.

Frequently asked questions

What is an MCP server?

MCP (Model Context Protocol) is an open standard that lets AI assistants use tools. The Faastic MCP server at https://api.faastic.com/mcp turns our REST API into more than 120 tools for servers, networks, firewalls, load balancers, databases, DNS, domains and orders.

Which AI assistants work with it?

Claude, Cursor and any other assistant or agent that speaks MCP. You add the server with an API token as a bearer header.

Can an AI assistant buy or delete things on my account?

Only what its token allows. Orders need a token with billing rights, nothing is built until the invoice is paid, and tools that delete or overwrite data are marked so the assistant's client can check with you first.

Can I see what my assistant changed?

Yes. Every change appears in your organization's activity log, next to the token that made it.

Ready to connect your assistant?

Create a token in your dashboard, choose its permissions and follow the setup above. You can revoke access whenever you need to.