Connect your client

Connect in three steps

1. Create a key

   On the Developers page, create an API key — read, unless you want the assistant to be able to change things. Export it where your client can read it:

   export VIDRYS_API_KEY="vidrys_sk_…"

2. Add the server to your client

   Use the configuration for your client below. The server URL is the same everywhere: https://api.vidrys.com/mcp.

3. Ask it something

   “Using Vidrys, list my projects, then show this week’s visibility for the first one.” The assistant should call list_projects and then get_visibility_overview.

Client configuration

claude mcp add --transport http vidrys https://api.vidrys.com/mcp --header "Authorization: Bearer $VIDRYS_API_KEY"

[mcp_servers.vidrys]
url = "https://api.vidrys.com/mcp"
bearer_token_env_var = "VIDRYS_API_KEY"

{
  "mcpServers": {
    "vidrys": {
      "url": "https://api.vidrys.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:VIDRYS_API_KEY}"
      }
    }
  }
}

https://api.vidrys.com/mcp

curl --request POST \
  --url "https://api.vidrys.com/mcp" \
  --header "Authorization: Bearer $VIDRYS_API_KEY" \
  --header "Content-Type: application/json" \
  --header "Accept: application/json, text/event-stream" \
  --data '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Check it works

Ask the assistant to list the Vidrys tools. You should see list_projects, get_visibility_overview, list_gapsand the rest. Then ask a real question — “which questions are we losing on ChatGPT?” — and check the answer names your own competitors.

If it doesn’t connect

• 401, or the client keeps asking you to sign in. The key is missing, revoked, or the member who created it has left. Check the header reaches the server: in a shell, echo $VIDRYS_API_KEY should print a vidrys_sk_ value.
• Every tool answers “plan_required”.The key is genuine but the plan doesn’t include API access — it starts at Grow. The connection stays up so the assistant can tell you that, rather than looping.
• “write_not_allowed” on a write tool. The key is read-only, or the plan is Grow. Writes need a read-and-write key on Scale or Custom.
• 421 Misdirected Request. The server only answers on its own hostname, as protection against DNS rebinding. Point the client at https://api.vidrys.com/mcp directly rather than through a proxy that rewrites Host.
• Tools appear but every call 404s. The assistant is guessing project ids. Tell it to call list_projects first.