arkoMCP SETUP
Connect ARKO
to your agent.
Connect ARKO’s tools to your coding agent, sign in once, and bring an independent check into the conversation.
1. Choose your coding client.
Before connecting, have your coding client, an ARKO account and Node.js LTS ready.
Check the prerequisitesClient installation, Node.js and your ARKO account.+
Before you connect.
Install Claude Code.
For Claude Code, follow the official installation instructions, then open a new terminal and check the installation.
claude --version
For an editor-based agent, install your chosen editor and enable its agent chat before connecting ARKO.
You need an ARKO account, your chosen coding client and a current Node.js LTS release. Node supplies npx, which starts the ARKO MCP package.
node -v
The client launches ARKO when it needs the server. You do not need to leave a separate ARKO terminal process running.
Claude Code
From the project folder, register ARKO with Claude Code:
claude mcp add arko -- npx -y arko-mcp
Check the server registration:
claude mcp list
Open or restart Claude Code after adding the server. Use its /mcp panel for connection status.
Cursor
Create or open .cursor/mcp.json in your project. A personal configuration across projects lives at ~/.cursor/mcp.json.
{
"mcpServers": {
"arko": {
"command": "npx",
"args": [
"-y",
"arko-mcp"
]
}
}
}Save the file, then reconnect MCP or reload the editor if needed.
VS Code
Create or open .vscode/mcp.json in your project. VS Code uses the top-level servers key.
{
"servers": {
"arko": {
"command": "npx",
"args": [
"-y",
"arko-mcp"
]
}
}
}Open the Command Palette and choose MCP: List Servers to start ARKO and inspect its output. Enable its tools in your agent chat when needed.
Kiro
Create or open .kiro/settings/mcp.json in your workspace, or use Kiro: Open workspace MCP config (JSON).
{
"mcpServers": {
"arko": {
"command": "npx",
"args": [
"-y",
"arko-mcp"
],
"disabled": false
}
}
}Save the file to reconnect. Choose any tool approval settings in Kiro according to your own workflow.
Other client
Choose a local stdio MCP server. Use your client’s own configuration format with these settings.
Command: npx Arguments: -y arko-mcp
Each client has its own configuration format. Use the official documentation for your selected client.
2. Sign in to ARKO.
Run the login command in your terminal, then complete the browser sign-in. Use your work email for your organisation account.
npx -y arko-mcp login
Check the account you are using:
npx -y arko-mcp whoami
3. Run your first ARKO check.
Open a project you own, then give your agent a specific request:
Use ARKO to review this project’s source code and dependency manifests. Explain the findings and identify the most important issue to fix first. Do not publish changes.
Source-code risks are checked with arko_scan_code. Dependency manifests are checked with arko_scan_project. Let the agent report what it submitted and what completed.
Try the interactive project guideTroubleshooting.
node or npx is not found.
node -v.ARKO is connected, but its tools fail to authenticate.
npx -y arko-mcp login, complete the browser sign-in, then use npx -y arko-mcp whoami to confirm your account.The server is missing from my client.
servers; Cursor and Kiro use mcpServers. Reconnect or reload after saving.I am signed in with the wrong account.
npx -y arko-mcp logout, then log in with the intended account. Check whoami before scanning.The server works in one project only.
A scan has not finished or a gate failed.
AFTER YOUR FIRST CHECK
Advanced setup.
Repository gatesPrepare the configuration and inspect its behaviour.+
Optional: prepare a repository gate.
After you understand the manual workflow, the package can prepare repository configuration and agent instructions. Preview the proposed changes first:
npx -y arko-mcp init --with-gate --dry-run
To apply the setup:
npx -y arko-mcp init --with-gate
A changed-files gate can be invoked from the terminal:
npx -y arko-mcp gate --changed
For enterprise CI rollout and policy choices, talk to ARKO.
Terminal and CICarry checks into your delivery workflow.+
Terminal and CI: carry the check into delivery.
Start with a local gate and inspect its output. In CI, agree the failure behaviour, submitted files and required-check policy before applying it across repositories.
npx -y arko-mcp gate --help
A repository’s branch protection or merge rules must require the check if you want a failed result to block merging. Keep source checks, dependency checks and artefact checks distinct in the recorded result.
Explore checks across the delivery pathRemediation toolsFind, fix and recheck with the complete validation scope.+
Use the rest of the remediation loop.
Ask your agent to explain the finding, propose the change and use the available ARKO remediation tools. Review changes before accepting or publishing them.
arko_scan_code- Check supplied source code.
arko_scan_project- Check dependency manifests.
arko_fix_all- Request a prioritised remediation plan; review it before applying changes.
arko_validate_fix- Check whether changes resolve findings. Submit the complete file scope covering existing findings.
arko_raise_fix_pr- When explicitly requested, propose an AutoFix pull request for a finding in a GitHub-connected repository.
Review the ARKO findings and propose the relevant fixes. Apply only the changes we agree, run the project’s normal checks and recheck with ARKO. Preserve the complete file scope when validating existing findings. Summarise what was fixed, what remains and what was not checked. Do not create or publish a pull request without my instruction.
For a reviewed repository change, supported pull-request tooling can carry the proposed fix to the normal review workflow. Repository permissions and your team’s merge policy still apply.
Official references.
Guidance checked against published package and client documentation on 12 September 2026.