Connect a coding agent

Every agent needs the same two values. Only the place where you put them is different.

Value	Setting
Endpoint	`https://aquila.attaxr.com/mcp` (Streamable HTTP)
Header	`Authorization: Bearer aqmcp_YOUR_KEY`

Select your agent below. Each guide starts with the key, so you can follow one tab from start to end.

Claude Code
OpenCode
Cursor
Codex

Claude Code adds remote MCP servers with the claude mcp add command.

Copy your MCP authorization key

Sign in to the Aquila dashboard.
Open the user menu (your avatar, top right) and select Settings.
Select MCP Server. The direct link is aquila.attaxr.com/dashboard/settings?section=mcp-server.
In the Authorization key row, click Reveal. Then click Copy.

The key starts with aqmcp_. Anyone with the key can run recon as you. Keep it private.If Reveal is not available, Aquila stores your key as a hash only. Click Rotate key to get a key that you can copy. Rotation stops the old key immediately.

Add the Aquila server

Run this command in a terminal. Replace aqmcp_YOUR_KEY with your key.

claude mcp add --transport http --scope user aquila https://aquila.attaxr.com/mcp --header "Authorization: Bearer aqmcp_YOUR_KEY"

--scope user makes Aquila available in all your projects. Claude Code stores the entry in ~/.claude.json, which only you can read.

Check the connection

claude mcp list

The Aquila line must show Connected:

aquila: https://aquila.attaxr.com/mcp (HTTP) - ✔ Connected

In a Claude Code session, type /mcp to see the server and its tools.

Use the tools

Ask Claude Code for recon work in plain language. For example: “Use the aquila list_scans tool to show my five newest scans.”

To give every teammate the server through the repository, add a .mcp.json file to the project root. The file reads each person’s key from the AQUILA_MCP_KEY environment variable, so no key goes into git.

.mcp.json

{
  "mcpServers": {
    "aquila": {
      "type": "http",
      "url": "https://aquila.attaxr.com/mcp",
      "headers": {
        "Authorization": "Bearer ${AQUILA_MCP_KEY}"
      }
    }
  }
}

Put the key in the AQUILA_MCP_KEY environment variable. The agent reads the key from this variable, so the key never goes into a config file.

# Add this line to ~/.zshrc or ~/.bashrc so that new terminals keep it.
export AQUILA_MCP_KEY="aqmcp_YOUR_KEY"

setx AQUILA_MCP_KEY "aqmcp_YOUR_KEY"
# setx applies to new terminals only. Open a new terminal before you continue.

Claude Code asks each person to approve a project server one time. Until then, claude mcp list shows the server as Pending approval. Start claude in the project and approve the server.

OpenCode reads remote MCP servers from the mcp block of its opencode.json config.

Copy your MCP authorization key

Sign in to the Aquila dashboard.
Open the user menu (your avatar, top right) and select Settings.
Select MCP Server. The direct link is aquila.attaxr.com/dashboard/settings?section=mcp-server.
In the Authorization key row, click Reveal. Then click Copy.

Store the key in an environment variable

Put the key in the AQUILA_MCP_KEY environment variable. The agent reads the key from this variable, so the key never goes into a config file.

# Add this line to ~/.zshrc or ~/.bashrc so that new terminals keep it.
export AQUILA_MCP_KEY="aqmcp_YOUR_KEY"

setx AQUILA_MCP_KEY "aqmcp_YOUR_KEY"
# setx applies to new terminals only. Open a new terminal before you continue.

Add the Aquila server to your config

Open the global config at ~/.config/opencode/opencode.json. On Windows, the file is %USERPROFILE%\.config\opencode\opencode.json. Create the file if it does not exist. To use Aquila in one project only, put the same block in opencode.json at the project root.

opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "aquila": {
      "type": "remote",
      "url": "https://aquila.attaxr.com/mcp",
      "oauth": false,
      "headers": {
        "Authorization": "Bearer {env:AQUILA_MCP_KEY}"
      }
    }
  }
}

"oauth": false is necessary. Without it, OpenCode tries to start an OAuth sign-in. Aquila uses a key, not OAuth.If your file already has an mcp block, add only the aquila entry to it.

Check the connection

opencode mcp list

The Aquila line must show connected:

✓ aquila connected
    https://aquila.attaxr.com/mcp

Use the tools

Start opencode and ask for recon work in plain language. For example: “Use the aquila search_leads tool to find leads on example.com.”

Cursor reads MCP servers from an mcp.json file.

Copy your MCP authorization key

Sign in to the Aquila dashboard.
Open the user menu (your avatar, top right) and select Settings.
Select MCP Server. The direct link is aquila.attaxr.com/dashboard/settings?section=mcp-server.
In the Authorization key row, click Reveal. Then click Copy.

Open your global MCP config

Open ~/.cursor/mcp.json in Cursor. On Windows, the file is %USERPROFILE%\.cursor\mcp.json. Create the file if it does not exist.The global file applies to all your projects. It is not part of a repository, so the key stays on your computer.

Add the Aquila server

Paste this config. Replace aqmcp_YOUR_KEY with your key.

~/.cursor/mcp.json

{
  "mcpServers": {
    "aquila": {
      "url": "https://aquila.attaxr.com/mcp",
      "headers": {
        "Authorization": "Bearer aqmcp_YOUR_KEY"
      }
    }
  }
}

If your file already has an mcpServers block, add only the aquila entry to it. Save the file.

Check the connection

Open Customize in the Cursor sidebar and find aquila in the MCP server list. Make sure the server is on. When Cursor connects, the entry lists the Aquila tools.If no tools show, turn the server off and on again, or restart Cursor.

Use the tools

In Agent chat, ask for recon work in plain language. For example: “Use the aquila search_vulnerabilities tool to list my critical findings.” Cursor asks you to approve each tool call before it runs.

Use a project config instead

To share the server through a repository, put the config in .cursor/mcp.json at the project root. Do not put a key in a file that goes into git. Read the key from an environment variable:

.cursor/mcp.json

{
  "mcpServers": {
    "aquila": {
      "url": "https://aquila.attaxr.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:AQUILA_MCP_KEY}"
      }
    }
  }
}

Put the key in the AQUILA_MCP_KEY environment variable. The agent reads the key from this variable, so the key never goes into a config file.

# Add this line to ~/.zshrc or ~/.bashrc so that new terminals keep it.
export AQUILA_MCP_KEY="aqmcp_YOUR_KEY"

setx AQUILA_MCP_KEY "aqmcp_YOUR_KEY"
# setx applies to new terminals only. Open a new terminal before you continue.

Cursor reads the variable from the environment that started Cursor. If you start Cursor from the Dock or the Start menu, it can miss a variable that you set in a terminal profile. If the server does not connect, start Cursor from a terminal, or use the global file with the key.

Codex adds remote MCP servers with the codex mcp add command. Codex reads the key from an environment variable.

Copy your MCP authorization key

Sign in to the Aquila dashboard.
Open the user menu (your avatar, top right) and select Settings.
Select MCP Server. The direct link is aquila.attaxr.com/dashboard/settings?section=mcp-server.
In the Authorization key row, click Reveal. Then click Copy.

Store the key in an environment variable

Put the key in the AQUILA_MCP_KEY environment variable. The agent reads the key from this variable, so the key never goes into a config file.

# Add this line to ~/.zshrc or ~/.bashrc so that new terminals keep it.
export AQUILA_MCP_KEY="aqmcp_YOUR_KEY"

setx AQUILA_MCP_KEY "aqmcp_YOUR_KEY"
# setx applies to new terminals only. Open a new terminal before you continue.

Add the Aquila server

Run this command in a terminal:

codex mcp add aquila --url https://aquila.attaxr.com/mcp --bearer-token-env-var AQUILA_MCP_KEY

The command writes this entry to ~/.codex/config.toml. You can also add the entry to the file yourself:

~/.codex/config.toml

[mcp_servers.aquila]
url = "https://aquila.attaxr.com/mcp"
bearer_token_env_var = "AQUILA_MCP_KEY"

Codex sends the variable’s value as Authorization: Bearer <value>.

Check the connection

codex mcp list

The Aquila row must show enabled and Bearer token:

Name    Url                            Bearer Token Env Var  Status   Auth
aquila  https://aquila.attaxr.com/mcp  AQUILA_MCP_KEY        enabled  Bearer token

This list shows the config only. To see that the key works, start codex and type /mcp. The Aquila server must list its tools.

Use the tools

Ask Codex for recon work in plain language. For example: “Use the aquila list_scans tool to show my five newest scans.”

Troubleshooting

Symptom	Cause	Fix
`401` or `no bearer token`	The request has no `Authorization` header. Usually the environment variable is not set in the terminal that started the agent.	Run `echo $AQUILA_MCP_KEY` (PowerShell: `$env:AQUILA_MCP_KEY`) in that terminal. If it is empty, set it again and restart the agent.
`401` after the setup worked before	Somebody rotated the key. The old key stopped at that moment.	Copy the new key from Settings → MCP Server. Update your config or variable.
The agent opens a browser for an OAuth sign-in	The agent tried OAuth discovery. Aquila uses keys only.	In OpenCode, set `"oauth": false`. In other agents, make sure the `Authorization` header is present.
OpenCode shows `SSE error: Non-200 status code (401)`	Same as the first row. OpenCode can try SSE after the first attempt fails, and then it reports the SSE error.	Check the key and the variable.
The server connects but shows no tools	The agent may not reload its tool list after a config change.	Restart the agent session. In Cursor, turn the server off and on.

Every tool call runs as you. Aquila stays inside the approved scope of your scans and rejects targets outside that scope. See the MCP overview for the full tool surface.

Start here

MCP server setup

Platform

Surface monitoring

Settings surfaces

Reference

API reference

API endpoints

Connect a coding agent

Use a project config instead

Troubleshooting

​Share the server with your team

​Use a project config instead

​Troubleshooting

Share the server with your team

Use a project config instead

Troubleshooting