Server

Server address

https://changedetection.yermateranas.burma-family.fr/mcp/v1

MCP access token

Access tokens

Add a token for each assistant on the Access tokens sub-tab. It is shown once, when it is created.

Treat it like a password. It does not expire, and anyone who has it can use these tools and read what they return. Never paste it into a file you commit or share.

Most assistants below can read it from an environment variable, so it stays out of their config files. Set it once, for example in ~/.bashrc or ~/.zshrc:

export CDIO_MCP_TOKEN=YOUR_MCP_TOKEN

Claude Code

Run this in a terminal, then start a new Claude Code session and ask, for example, "Which of my monitors have errors?"

claude mcp add --transport http changedetection https://changedetection.yermateranas.burma-family.fr/mcp/v1 --header "Authorization: Bearer $CDIO_MCP_TOKEN"

To remove it again: claude mcp remove changedetection

By default (--scope local) Claude Code saves this in ~/.claude.json, only for you and only in the current project. Add --scope user to have it in all your projects.

--scope project writes .mcp.json into the project, which is usually committed. Use this form there instead, it saves a reference to the environment variable, not the token:

claude mcp add --transport http --scope project changedetection https://changedetection.yermateranas.burma-family.fr/mcp/v1 --header 'Authorization: Bearer ${CDIO_MCP_TOKEN}'

Cursor ~/.cursor/mcp.json

{"mcpServers": {"changedetection": {"url": "https://changedetection.yermateranas.burma-family.fr/mcp/v1", "headers": {"Authorization": "Bearer ${env:CDIO_MCP_TOKEN}"}}}}

VS Code / GitHub Copilot .vscode/mcp.json

VS Code asks for the token once and stores it securely, so this file is safe to commit.

{"inputs": [{"type": "promptString", "id": "cdio-mcp-token", "description": "changedetection.io MCP access token", "password": true}], "servers": {"changedetection": {"type": "http", "url": "https://changedetection.yermateranas.burma-family.fr/mcp/v1", "headers": {"Authorization": "Bearer ${input:cdio-mcp-token}"}}}}

OpenAI Codex ~/.codex/config.toml

[mcp_servers.changedetection]
url = "https://changedetection.yermateranas.burma-family.fr/mcp/v1"
bearer_token_env_var = "CDIO_MCP_TOKEN"

OpenCode opencode.json

{"mcp": {"changedetection": {"type": "remote", "url": "https://changedetection.yermateranas.burma-family.fr/mcp/v1", "oauth": false, "headers": {"Authorization": "Bearer {env:CDIO_MCP_TOKEN}"}}}}

Gemini CLI ~/.gemini/settings.json

Uses httpUrl, not url (url means the older SSE transport).

{"mcpServers": {"changedetection": {"httpUrl": "https://changedetection.yermateranas.burma-family.fr/mcp/v1", "headers": {"Authorization": "Bearer YOUR_MCP_TOKEN"}}}}

This file contains the token: keep it in your own settings, not in anything you commit or share.

GitHub Copilot CLI ~/.copilot/mcp-config.json

copilot mcp add --transport http --header "Authorization: Bearer $CDIO_MCP_TOKEN" changedetection https://changedetection.yermateranas.burma-family.fr/mcp/v1

This file contains the token: keep it in your own settings, not in anything you commit or share.

Zed settings.json

{"context_servers": {"changedetection": {"url": "https://changedetection.yermateranas.burma-family.fr/mcp/v1", "headers": {"Authorization": "Bearer YOUR_MCP_TOKEN"}}}}

This file contains the token: keep it in your own settings, not in anything you commit or share.

Claude Desktop claude_desktop_config.json

Through the mcp-remote bridge (needs Node.js), since Claude Desktop connectors only support sign-in, not an access token.

{"mcpServers": {"changedetection": {"command": "npx", "args": ["-y", "mcp-remote", "https://changedetection.yermateranas.burma-family.fr/mcp/v1", "--header", "Authorization:${MCP_AUTH}"], "env": {"MCP_AUTH": "Bearer YOUR_MCP_TOKEN"}}}}

This file contains the token: keep it in your own settings, not in anything you commit or share.

Any other assistant (Windsurf, Devin and others)

Most assistants can run a local command: the same mcp-remote bridge (needs Node.js), in the format of that assistant's MCP settings.

{"command": "npx", "args": ["-y", "mcp-remote", "https://changedetection.yermateranas.burma-family.fr/mcp/v1", "--header", "Authorization:${MCP_AUTH}"], "env": {"MCP_AUTH": "Bearer YOUR_MCP_TOKEN"}}

This file contains the token: keep it in your own settings, not in anything you commit or share.

One for each assistant, each with its own permissions. Revoking one disconnects only that assistant.

To make only one assistant read-only, use this address for it instead:

OAuth connections

ChatGPT and claude.ai in the browser connect with sign-in (OAuth) instead of an access token: you log in here and choose what the assistant may do.

Claude (claude.ai)

1. Open Customize > Connectors on claude.ai.
2. Click the add button, then "Add custom connector".
3. Give it a name, for example changedetection.io, and paste this as the remote MCP server URL: https://changedetection.yermateranas.burma-family.fr/mcp/v1
4. Leave the sign-in setting as Claude detects it, then click Add.
5. Click Connect: you come here to log in, choose what Claude may do and click Allow, then you are sent back to Claude.

On Team and Enterprise plans an Owner adds it under Organization settings > Connectors, then each member clicks Connect. Claude help: custom connectors

ChatGPT (OpenAI)

1. In ChatGPT, open Settings > Apps & Connectors > Advanced settings and switch on Developer mode. On some accounts it is under Settings > Security.
2. Back in Apps & Connectors, click Create (or "Add custom connector").
3. Give it a name, paste this as the MCP server URL and choose OAuth as the authentication: https://changedetection.yermateranas.burma-family.fr/mcp/v1
4. Confirm and click Create: you come here to log in, choose what ChatGPT may do and click Allow.
5. In a chat, click +, choose Developer mode and pick the connector.

Custom connectors need a paid ChatGPT plan; on Business and Enterprise plans an admin may need to allow them first.

Signed in