WebAnatomy
Reference

Authentication

How the Web Anatomy MCP authenticates, and where to keep your token.

The MCP authenticates with a bearer token over streamable HTTP.

  1. After your access is approved, generate the token once in the MCP dashboard.
  2. The install snippet for your IDE reads it from the Authorization: Bearer <token> header (or from WEBANATOMY_MCP_TOKEN, depending on the client).

Store the token in an ignored local config, such as an env var or $HOME/.webanatomy/webanatomy_mcp_token. Use the user-level (global) config for your IDE so the token is never committed. If a token is pasted into shell history, chat logs, or a tracked file by mistake, revoke it in the dashboard and generate a new one.

The endpoint is:

https://mcp.webanatomy.ai/mcp

What the server can return

It returns public-safe benchmark sections, filters, and selected section or page details. It does not return raw scores, marker coordinates, service-role access, or internal database fields.

On this page