Workspace

Connect Claude Code

This setup recipe is for connecting Claude Code to Shape Beacon's remote MCP server. The server provides read-only aggregate analytics for the one verified domain selected when you create the connection. It does not install collection or grant access to another site.

Compatibility is unverified. Direct Claude Code compatibility has not been demonstrated in this environment, and this flow has not been validated by an independent customer.

Before you start

In Workspace, select your active verified domain, open Connect Agent, choose Claude Code, and select Create Connection. Access expires after 30 days unless revoked sooner. Install collection separately; a connection does not create behavioral evidence.

Keep the credential private

The credential is shown once. Do not put it in a prompt, source file, project configuration, URL, screenshot, or support message. It is separate from your browser-visible collection key. Your agent provider may process returned aggregate evidence under its own terms.

Load it into the shell

In the shell that will launch Claude Code, enter the value without echoing it or putting it in shell history:

read -r -s -p 'Shape Beacon Agent token: ' SHAPE_BEACON_AGENT_AUTH
printf '\n'
export SHAPE_BEACON_AGENT_AUTH

This lasts only for that shell and its child processes. Use a trusted local secret manager if you need longer storage. Do not run echo or env to inspect the value.

Configure a private user-scoped server

Run this command as written. It stores the environment variable reference, not your credential. The single quotes preserve the reference for Claude Code:

claude mcp add-json shape-beacon \
  '{"type":"http","url":"https://agent.shapebeacon.com/mcp","headers":{"Authorization":"Bearer ${SHAPE_BEACON_AGENT_AUTH}"}}' \
  --scope user
claude mcp get shape-beacon
claude mcp list

The production server offers seven tools: analytics_availability, summarize_period, inspect_cross_page, compare_periods, inspect_page, compare_page_periods, and rank_page_changes. Start a fresh Claude Code session from the shell where the variable is loaded and check /mcp for connection status. This setup has not been validated in Claude Code; the tool list does not establish client compatibility. Approve tool use according to your own host settings.

Try a first read

Ask Claude Code to use only the Shape Beacon MCP server, call analytics_availability, and report the exact hostname, available views, timezone and epoch. Then choose a completed local day shown in your dashboard and call summarize_period and inspect_cross_page. Read the returned dates, status, denominators and uncertainty. Availability does not prove recent collection.

Lost credential or disconnect

Shape Beacon cannot retrieve a credential after the one-time display. Return to your domain's Connect Agent panel to replace the connection, then update your local secret. A replaced credential may keep working for up to 24 hours. Use Disconnect in that panel to stop server access. Removing a client configuration alone does not revoke the grant. Remove it locally with claude mcp remove shape-beacon.