Help: For agent builders

Connect an agent

An agent reaches funwatcher through the MCP connector at this address:

https://funwatcher.com/mcp

The connector is hosted with funwatcher. There is nothing to install: your MCP client connects to it over the internet and sends the agent's key with every request. This page shows how to get a key and what to enter in each client. If your agent makes HTTP calls instead of speaking MCP, see API overview.

Register the agent and copy its key

Only an owner of the account can register an agent.

  1. Select "Agents" in the top bar and select "Register an agent".
  2. Enter "Agent name" and "Vendor label".
  3. Select "Register and create key".
  4. On the page that says the agent is registered, select "Reveal" to see the key or "Copy" to copy it.
  5. Put the key into your client as described below, then select "Done, go to the agent".

In the examples below, replace YOUR_AGENT_KEY with the key.

Claude Code

Run this once in a terminal:

claude mcp add --transport http funwatcher https://funwatcher.com/mcp \
  --header "Authorization: Bearer YOUR_AGENT_KEY"

Check it with claude mcp list, or /mcp inside Claude Code: funwatcher shows as connected with three tools.

Claude (claude.ai and the desktop app)

Add funwatcher as a custom connector. A connector belongs to your Claude account, so one added on claude.ai is the same one the desktop app uses.

1. In Claude, open Customize, then Connectors. Select "+ Add", then "Add custom connector".

2. Enter the name funwatcher and this address as the remote MCP server URL, then select "Continue":

https://funwatcher.com/mcp

3. Under "Authentication" choose "No sign in". The agent key takes the place of a sign-in.

4. Under "Request headers" choose the header name authorization and enter this value, the word Bearer and a space included (Claude sends the value exactly as typed):

Bearer YOUR_AGENT_KEY

5. Select "Add", then start a new conversation. The three tools appear under the connector.

Things to know about the Claude apps:

Desktop app without "Request headers". The desktop app can start a small bridge program, mcp-remote, that sends the key for it. It needs Node.js 18 or later on the computer. In the desktop app open Settings, Developer, "Edit Config", add this to claude_desktop_config.json and restart the app completely:

{
  "mcpServers": {
    "funwatcher": {
      "command": "npx",
      "args": ["mcp-remote", "https://funwatcher.com/mcp", "--transport", "http-only", "--header", "Authorization:${AUTH_HEADER}"],
      "env": {
        "AUTH_HEADER": "Bearer YOUR_AGENT_KEY"
      }
    }
  }
}

Cursor, VS Code and other clients

Any MCP client that supports streamable HTTP with a custom header works. Give it the address and the header:

URL:    https://funwatcher.com/mcp
Header: Authorization: Bearer YOUR_AGENT_KEY

Most clients take them as JSON. Cursor (~/.cursor/mcp.json) and clients with the same format:

{
  "mcpServers": {
    "funwatcher": {
      "url": "https://funwatcher.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_AGENT_KEY"
      }
    }
  }
}

VS Code (.vscode/mcp.json) uses "servers" in place of "mcpServers" and adds "type": "http" to the entry. Keep a file that contains the key out of version control.

Check that the agent is connected

  1. Ask the agent to list its tools, or look at the connector in your client. It shows 3 tools: request_approval, report_result, check_policy.
  2. Have the agent propose an action, so that it calls request_approval.
  3. Select "Agents" in the top bar, select the agent's name and read "Last used" next to its key. "never" means no call has arrived.

If the client cannot connect or reports that authentication is needed, see Troubleshooting.

What connecting does and does not do

For what each tool takes and returns, see MCP tools.

Previous:
Next:

All help pages

Inbox

Rules

Teams

Ledger

Billing

Account and security

For agent builders

Troubleshooting