Armis Appsec MCP Server

Contact the Armis AppSec team if you don't have credentials.

What you get

• scan_code — — Scan a code snippet for vulnerabilities
• scan_file — — Scan a file on disk
• scan_diff — — Scan git changes (staged, unstaged, or diff against a branch)
• approve_findings — — Approve findings after user consent (for shipping with known risks)
• debug_config — — Check scanner configuration status
• Commit gate — — Git pre-commit hook that blocks commits until code is scanned

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

What the assistant can call

Once Armis Appsec MCP is connected, these are the calls the assistant has available:

• Cursor — Run make setup CLIENT=cursor and copy the output to ~/.cursor/mcp.json (user-level) or .cursor/mcp.json (workspace-level)
• Cline — Add the MCP server via Cline's MCP settings panel. Then wire in the commit gate hook:

Configuration and credentials

You will need 3 environment variables: ARMIS_CLIENT_ID, ARMIS_CLIENT_SECRET, APPSEC_API_URL. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.

Choosing this one

Setup and compatibility

This listing has no verified copy-paste launch configuration. Use the project documentation to confirm the entry point, runtime and authentication before registering it in your MCP client. A package name or repository alone is not a runnable configuration.

More MCP options

Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.