Setup

by AikidoSec02f018ad4da1No license14 starsListed Oct 7, 2026Updated Oct 7, 2026Repository updated 12 days ago

Configures the Aikido plugin by signing the user in through the MCP login tool and verifying the MCP server. Use when the user wants to set up or verify the Aikido plugin, after installing it, when aikido mcp tool call fails or is unavailable, or when the user wants to switch Aikido accounts or re-authenticate.

Instructions onlyDevOps & Cloud
AI-generated overview

Guides setup and sign-in for the Aikido security plugin via its MCP login tool, including Node.js checks.

What it does
This skill walks an agent through configuring the Aikido security plugin. It first checks the installed Node.js version and stops with guidance if Node.js is missing or below 18.19.0. It then calls the aikido-mcp:aikido_login tool to detect an existing session or obtain a sign-in URL, presents that URL to the user, and verifies the setup by calling the tool again. It also covers switching accounts or re-authenticating with a forced re-auth.
When to use it
Use it when a user wants to set up or verify the Aikido plugin, typically right after installing it. It also applies when an Aikido MCP tool call fails or is unavailable, or when the user wants to switch Aikido accounts or re-authenticate.
Requirements
Requires Node.js 18.19.0 or higher and the Aikido plugin with its aikido-mcp MCP server loaded in the agent environment. It relies on the aikido-mcp:aikido_login tool and a browser for the user to complete sign-in. No scripts are shipped; it is instructions only.

When helping the user configure the Aikido security plugin:

First: Verify Node.js version

Before doing anything else, run node --version to check the installed Node.js version.

  • If Node.js is not installed or the command fails, stop and tell the user that Node.js 18.19.0 or higher is required to run the Aikido MCP server, and direct them to https://nodejs.org to install it.
  • If the version is below 18.19.0, stop and tell the user that the Aikido MCP server requires Node.js 18.19.0 or higher, show the currently installed version, and direct them to https://nodejs.org to upgrade.
  • If the version is 18.19.0 or higher, proceed with the steps below.

If the user is asking to switch accounts or re-authenticate, call aikido-mcp:aikido_login with force_reauth: true and skip step 1 — the tool will always return a fresh sign-in URL. Continue from step 3 to walk the user through opening the URL and step 4 to verify.

Otherwise, follow the standard setup flow:

  1. Check the MCP server is reachable and the user is signed in by calling aikido-mcp:aikido_login with no arguments. The tool is idempotent — it returns "Already signed in" if a valid token is cached, otherwise it starts a new sign-in flow.
  2. If it reports the user is already signed in, confirm to the user that the Aikido plugin is configured and ready to use. Stop here.
  3. If it returns a sign-in URL, present it to the user verbatim — do not strip or modify the state, redirect_uri, or regionRedirect query parameters — and ask them to open it in a browser to complete sign-in. The URL automatically redirects the user to their account's region, so there is no need to pick a region. Only pass the optional region argument when the user explicitly names a region (e.g. EU / US / ME / AU), or when the automatic redirect sent them to the wrong one.
  4. Once the user reports they have completed the browser sign-in, verify the setup by calling aikido-mcp:aikido_login again.
  5. If the aikido_login call itself fails because the MCP server is unavailable, tell the user to ensure the Aikido plugin is installed and that Claude Code has loaded the aikido-mcp server, then retry.

Source and attribution

Source:AikidoSec/aikido-claude-plugininskills/setupat commit02f018a

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal