> ## Documentation Index
> Fetch the complete documentation index at: https://docs.watchdog.no/llms.txt
> Use this file to discover all available pages before exploring further.

# Use Watchdog with AI

> Connect Claude Code, Codex, or ChatGPT to investigate invoices and agreements.

MCP connects your AI client to Watchdog. You can investigate invoices, compare agreement prices,
and find the cause of discrepancies. You decide whether the client can also make changes.

<Note>MCP works with Claude Code and Codex. ChatGPT is not supported yet.</Note>

## Choose a connection

Use this address for a connection that **can only read**:

```text theme={null}
https://mcp.watchdog.no/mcp/readonly
```

Use this address if you also want to **allow changes**:

```text theme={null}
https://mcp.watchdog.no/mcp
```

The address decides what the client can do. The address ending in `/readonly` never allows
changes, whatever you approve when you sign in.

Choose **Streamable HTTP** and **OAuth** in the connection settings. Sign in to Watchdog in your
browser, then check which application is asking for access and what it can do. You do not need
a personal API key. Never paste sign-in codes or access tokens into a conversation.

## What access are you giving?

When you sign in, you approve **Watchdog** access (`watchdog`): the client can use the Watchdog
data you have access to. What it can do with that data depends on the address:

| Address | What the AI client can do |
| - | - |
| Ending in `/readonly` | Search and read data |
| Ending in `/mcp` | Also change data, start imports, and run checks |

Access covers organizations you belong to now and any you join later. The client can never do
more than your role and the organization's security rules allow.

To allow changes later, switch the connection to the standard address.
Members, invitations and organization settings are managed in Watchdog, not through an AI client.
Confirming an action in a conversation does not give the client more rights in Watchdog.
Follow the setup guide for your client below.

## Choose an organization

Ask the client to list your organizations with their names and IDs. Choose which one to work
with. The client must use that ID in each request to Watchdog. The organization open in your
browser is not automatically selected in an external client.

For example:

> List my Watchdog organizations with their names and IDs. Compare open findings for Nordbygg AS
> and Sørbygg AS in September 2026. Keep the results separate and read all result pages before
> calculating totals. Do not change anything.

## Who receives your data?

Connecting an external AI client sends Watchdog's responses to that client's provider, under
your account or workspace terms. Use only clients your organization allows to receive this data.

The assistant inside Watchdog has separate conversations, each tied to the user and organization
that started it. An external connection does not give access to those conversations or change
the assistant's permissions.

## Disconnect

The AI client stores the credentials it needs to refresh the connection. Watchdog's MCP service
checks access on every request but does not store those credentials.

Log out or remove the connection in your AI client. Signing out of Watchdog in the browser
does not disconnect it. To ask Watchdog to cancel the access itself, email
[support@watchdog.no](mailto:support@watchdog.no); there is no account page for this yet.

Removed organization memberships and role changes also restrict connected clients once
Watchdog has received the update. This is not immediate. Revoked or expired sign-in credentials
are refused on the next request.

## Get started

* [Connect Claude Code](/guides/mcp/claude-code)
* [Connect Codex](/guides/mcp/codex)
* [Connect ChatGPT](/guides/mcp/chatgpt)
* [Try example tasks](/guides/mcp/working-with-watchdog)
* [Get connection help](/guides/mcp/troubleshooting)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.