MCP

What is MCP about?

MCP offers a server that bundles command‑line utilities to communicate with the Fluidattacks platform, exposing endpoints for common security‑related operations.

How to use MCP?

Add the server definition to your MCP configuration file, supply a valid API_TOKEN, and start the server with npx. The server can then be called from scripts or CI pipelines to perform actions such as retrieving vulnerabilities, managing assets, or triggering scans.

Key features of MCP

• Simple one‑line installation using npx.
• Environment‑based authentication with an API token.
• Pre‑packaged commands covering the majority of Fluidattacks API endpoints.
• Works cross‑platform as it runs on Node.js.

Use cases of MCP

• Automating security checks in CI/CD pipelines.
• Integrating Fluidattacks data into internal dashboards.
• Bulk remediation actions performed from scripts.
• Creating custom monitoring tools that query the API on demand.

FAQ from the MCP

Q: Which token format is required? A: A personal API token generated in the Fluidattacks console; see the setup documentation.

Q: Do I need to install Node.js manually? A: Yes, Node.js (v14+) must be available; npx will fetch the package automatically.

Q: Can I run multiple MCP servers simultaneously? A: Yes, define separate entries under mcpServers with unique names.

Q: Where is the full source code? A: The server code resides in the Fluidattacks GitLab repository under universe/interacts.

mcp

MCP server that provides tools for interacting with the Fluidattacks API.

• Complete documentation here
• MCP server code here

Configuration

If you don't know how to generate the API_TOKEN, please refer to the documentation

{
  "mcpServers": {
    "fluidattacks-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@fluidattacks/mcp"
      ],
      "env": {
        "API_TOKEN": "your_api_token_here"
      }
    }
  }
}