artemis-mcp-server

What is artemis-mcp-server?

artemis-mcp-server is a Model Context Protocol (MCP) server that provides an interface to the Artemis SAST (Static Application Security Testing) tool. It allows MCP clients to trigger SAST scans and receive results, designed for developers and security teams integrating automated code analysis into their toolchains.

How to use artemis-mcp-server?

Run the server with python3 -m artemis-mcp-server and optional flags: -r for a rule file path, -s for the server host (default shown as 127.0.0.1), and -p for the port (default 8088). A build.properties file must be placed in the project root directory to define java_home and build_cmd for scanner compilation. Connect an MCP client (e.g., Cline) using the SSE endpoint http://127.0.0.1:8088/sse.

Key features of artemis-mcp-server

• MCP server interface for Artemis SAST tool
• Configurable server host and port
• Supports a custom rule file path
• Verbose mode for debug output
• SSE transport with auto-approve for the scan command
• Requires a local build.properties configuration file

Use cases of artemis-mcp-server

• Trigger SAST scans from an MCP-enabled IDE or assistant
• Automate security analysis as part of a CI/CD pipeline
• Centralize SAST rule management by specifying rule files
• Integrate Artemis into development workflows without manual CLI usage

FAQ from artemis-mcp-server

What does artemis-mcp-server do?

It acts as an MCP server that lets clients invoke the Artemis SAST tool by sending a scan command over SSE, passing configuration like rule file and server address.

What runtime dependencies are required?

The scanner requires Java (jdk1.8.0_151 was shown in the example) and a build tool command (like mvn clean package), both defined in the build.properties file. The server itself runs with Python 3.

How do I configure the scanner’s build environment?

Create a build.properties file in the project root directory with java_home pointing to the JDK path and build_cmd specifying the build command (e.g., mvn clean package -X -DskipTests=true).

What transport does artemis-mcp-server use?

Server-sent events (SSE) on the endpoint http://127.0.0.1:8088/sse, as shown in the Cline configuration example.

How does auto-approve work in the Cline config?

The example Cline configuration sets "autoApprove": ["scan"], meaning the scan command will be executed without manual approval each time the client sends it.