PlugWiki

Aikido MCP Server: Security Scans for Claude, Cursor and Windsurf

OfficialLocal
Getnpm@aikidosec/mcp

Lets Claude, Cursor and Windsurf scan your code for security problems with Aikido and triage the results.

This is Aikido's own server for scanning code and managing findings from inside an AI coding tool. The assistant can scan changed files for code, secret and infrastructure problems, check dependency files, and list or triage issues from your Aikido account. You need an Aikido account, and you sign in through your browser the first time you use a tool. It can ignore, snooze and re-rate issues in Aikido, which hides findings from your team, so use it with care.

Good for

  • Developers who want security checks while an agent writes code
  • Security teams triaging Aikido issues from an AI app
  • Teams already on Aikido that want findings inside Cursor, VS Code or Windsurf

Works in

12 should work

Tap an app to see how to set it up and any known problems.

Install Aikido MCP

Claude Code

  1. 1

    Copy this prompt.

    Add the Aikido MCP server to Claude Code. Run this command:
    
    claude mcp add aikido -- npx -y @aikidosec/mcp
    
    Then check that it loaded and tell me if I need to sign in or restart.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Requires Node.js.

Built from the package data we hold. Not yet tested by us.

Tools

  • Scans files on disk for code, secret and infrastructure issues

    Runs Aikido's code, secrets and infrastructure scans on files you name. The server reads the files itself, so the assistant does not need to paste them. It is the preferred scan tool, and each path must be a file inside the folder you give.

    Try: “Scan the files I changed on this branch for security issues.”

    Runs code · aikido_scan_paths

  • Scans code that is not saved to a file yet

    Runs the same scans on code passed in as text, such as a snippet you pasted or a change not applied yet. It is meant only for code that is not on disk, and handles up to 50 files per call.

    Try: “Scan this snippet before I save it.”

    Runs code · aikido_full_scan

  • Checks dependency files for known vulnerabilities

    Scans manifests and lockfiles such as package.json, package-lock.json, requirements.txt or go.mod, passed as file paths, for open source dependency issues.

    Try: “Check my package.json and lockfile for vulnerable dependencies.”

    Runs code · aikido_oss_dependency_scan

  • Lists issues from your Aikido feed

    Fetches security issues from Aikido, with filters for repository, cloud, team, workspace, issue type, severity, labels, branch and SLA status.

    Try: “Show the critical open issues in the payments repo.”

    Network · aikido_issues_list

  • Lists the Aikido workspaces you can use

    Returns the workspaces the signed-in user can access, so the assistant can find the exact name before filtering issues.

    Try: “Which Aikido workspaces do I have?”

    Network · aikido_workspaces_list

  • Starts the browser sign-in to Aikido

    Returns a sign-in link to open in your browser, or confirms you are already signed in. It can switch accounts or regions.

    Try: “Sign me in to Aikido.”

    Network · aikido_login

  • Marks an issue as ignored, with a reason

    Ignores a security issue in your Aikido feed. You give the issue ID and a reason.

    Try: “Ignore issue 12345 because it is a test fixture.”

    Write · aikido_ignore_issue

  • Brings an ignored issue back

    Reverses an ignore on an issue, with a reason.

    Try: “Unignore issue 12345.”

    Write · aikido_unignore_issue

  • Hides an issue for a set time

    Snoozes an issue for 1 day, 1 week, 1 month, 3 months, 6 months or 1 year.

    Try: “Snooze issue 12345 for a month.”

    Write · aikido_snooze_issue

  • Ends a snooze early

    Unsnoozes an issue that was snoozed.

    Try: “Unsnooze issue 12345.”

    Write · aikido_unsnooze_issue

  • Changes an issue's severity

    Sets a new severity (critical, high, medium or low) on an issue, with a reason.

    Try: “Lower issue 12345 to low because it is only reachable in tests.”

    Write · aikido_adjust_issue_severity

Read from the source code

Permissions

medium risk · 4 things to watch

Medium risk

The assistant can read your code files, run scanners and change issue status in your Aikido account. Review any ignore, snooze or severity change before you approve it, because it hides or downgrades findings for your team.

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • It can hide or downgrade security findings

    Ignore, snooze and severity tools change issues in your Aikido account. Check each reason before approving, since teammates will see the change. npmjs.com

  • It reads the files you point it at

    Scan tools read the paths you name from your disk, and the server also calls Aikido's API for rules and issue details. Keep files you do not want scanned out of the paths you give it. npmjs.com

  • It downloads and runs scanner binaries on your machine

    On first use the package fetches scanner programs from Aikido's S3 bucket and from the GitHub releases of Checkov and opengrep, then runs them on the files you scan. It also bundles a secrets scanner. Allow those downloads only on a machine where that is acceptable. npmjs.com

  • Three extra scan tools are off by default

    Setting AIKIDO_MCP_ALL_TOOLS to true adds separate code, secrets and infrastructure scan tools. The default list already has combined scans. npmjs.com

Security advisories

No published security advisories as of Nov 1, 2026.

Technical details
Turning on read-onlyNo read-only mode is documented. The scan and list tools only read, but the ignore, snooze and severity tools change your Aikido account.
Talks toAikido API (EU, US, ME or AU region). aikido-local-scanner.s3.amazonaws.com and GitHub releases (scanner downloads). Scanner programs on your machine
Sign-in and keysSign in through a link in your browser the first time, or set a personal access token from Aikido Settings, Integrations, IDE, MCP in AIKIDO_API_KEY. The token wins over a cached sign-in.
Scopes
  • Aikido account sign-in, or a personal access token (AIKIDO_API_KEY)

Questions

Is the Aikido MCP server official?

Yes. It is published by Aikido, and the package maintainers are Aikido staff.

Do I need an Aikido account?

Yes. Sign up at app.aikido.dev. The first tool call gives sign-in links for each Aikido region, and you click the one that matches your account.

How do I use an API key instead of browser sign-in?

Create a personal access token under Settings, Integrations, IDE, MCP in Aikido and set it as AIKIDO_API_KEY in your MCP config. It takes precedence over a cached browser sign-in, and suits CI, containers and WSL.

Does my code leave my machine?

The scan tools run on your machine and read the files you name. The server also calls Aikido's API for sign-in, rules, issues and metadata, so check Aikido's documentation for exactly what it sends.

Can it be read-only?

No read-only switch is documented. Scans and lists only read, but ignore, snooze, unignore, unsnooze and severity changes write to Aikido.

Which tools does the package really have?

The package has 14 tools in its code. 11 are on by default, and setting AIKIDO_MCP_ALL_TOOLS to true adds three separate scan tools.

What license is it under?

AGPL, with a commercial license offered as an alternative. Read the LICENSE file in the package if you plan to use it in a commercial product.

Information

updated Nov 2, 2026

Publisher
Official
Package
@aikidosec/mcp
Registry
npm
Transport
stdio
Auth
OAuth
Version
1.0.33
License
AGPL or commercial

npm

Sources

Docs, issue trackers and discussions this page is built from. Issues, quotes and findings above link to their own source.

Show all 1
  1. www.npmjs.com · npmjs.com

Facts from the official MCP registry, GitHub, npm, PyPI and the Docker catalog. Updated Nov 2, 2026.