Connect AI tools (MCP)

FortWatch has an MCP server, so AI tools such as Claude, ChatGPT, Cursor, Claude Code and VS Code can work with your FortWatch workspace: ask about your assets and issues, run scans, and update issues and scan schedules. The AI tool acts as you, with your role, and only with the access you allow when you connect it.

The address to give your AI tool:

https://mcp.fortwatch.ai/mcp

When you connect, the AI tool sends you to FortWatch: sign in if asked, check what it asks for and select Allow. If you have two-factor authentication on, FortWatch asks for a code from your authenticator app.

The page's headline is where the AI tool comes from, such as claude.ai, or "An app on this computer" for a tool on your own computer, with the name it gives itself below. Allow it only if you started the connection yourself and that is the tool you are connecting.

Claude

In Claude (claude.ai or the desktop app), open Settings → Connectors, add a custom connector named FortWatch with the address above, then select Connect and allow it in FortWatch.

ChatGPT

In ChatGPT's settings, turn on developer mode and add an app (a connector) with the address above. ChatGPT sends you to FortWatch to allow it.

Cursor

Add FortWatch to ~/.cursor/mcp.json (or to a project's .cursor/mcp.json):

{ "mcpServers": { "fortwatch": { "url": "https://mcp.fortwatch.ai/mcp" } } }

Cursor then shows that FortWatch needs a login: select it and allow it in FortWatch. Cursor receives the sign-in on port 8787 of your computer: if FortWatch says the return address is not one this app registered, another program is using that port. Close it and connect again.

Claude Code

claude mcp add --transport http fortwatch https://mcp.fortwatch.ai/mcp

Then run /mcp in Claude Code and choose FortWatch to sign in. An owner or admin can use an API key instead of signing in (see Authentication):

claude mcp add --transport http fortwatch https://mcp.fortwatch.ai/mcp --header "Authorization: Bearer $FORTWATCH_API_KEY"

VS Code

Add FortWatch to .vscode/mcp.json:

{ "servers": { "fortwatch": { "type": "http", "url": "https://mcp.fortwatch.ai/mcp" } } }

What an AI tool can do

• Read your projects, assets, scans, scan schedules, issues, findings and the security overview.
• Run a scan, update, assign or dismiss an issue, and create or change a scan schedule: every role but viewer. A viewer's AI tool can only read.
• Delete things, change the team, or change settings: never. Do those in FortWatch.
• Your plan's limits apply, as they do in FortWatch.

Risky actions need your confirmation

Dismissing an issue, marking it resolved, and pausing a scan schedule or making it scan less often never happen straight away. The AI tool gets a link instead: open it, check what it will do and select Confirm in FortWatch within 15 minutes. Nothing changes until you do, and only you can confirm it.

What FortWatch sends to AI tools

Scan results can contain text written by the websites FortWatch scans, and an AI tool can be misled by such text. So FortWatch sends AI tools its own words and plain facts: names, severities, statuses, hosts, CVEs, remediation advice, and a link to each issue in FortWatch. Descriptions and raw evidence (page titles, server banners, header values, DNS records) stay in FortWatch. If your AI tool can also browse the web or send email, connect it only if you trust it with your list of issues.

Disconnecting

Profile → Connected AI tools lists the AI tools you connected; Disconnect stops one at once. Owners and admins see every connected AI tool of the workspace in Settings → API access → Connected apps. Everything an AI tool changes is in the audit log under its name.

Limits and troubleshooting

• Each connection can make 120 reads and 60 changes a minute; past that, the tool is told to wait.
• AI tools read the list of tools when they connect: after FortWatch adds or changes tools, reconnect or reload the AI tool.
• If the AI tool asks you to sign in again, its connection stopped (it was disconnected, or you left the workspace): connect it again.
• "This connection was not given … access": connect it again and allow that access.
• If your workspace requires two-factor authentication, set it up on your Profile page first.

The tools