MCP Spider private beta

Installing in Claude Code

One command, then a first question that proves the whole path.

Claude Code is the terminal client. It takes an access token in a header, which is why the previous article exists. You will need the token you copied there, and you will need it before you run the command below, because the command contains it.

Run One Command

Copy this, replace YOUR_TOKEN with your access token, and run it in a terminal.

claude mcp add --transport http mcp-spider-follow-up-boss \
  https://app.axelrivera.dev/mcp/follow_up_boss \
  --header "Authorization: Bearer YOUR_TOKEN"

The word Bearer is part of the header value, not a placeholder. What replaces YOUR_TOKEN is the token itself, with nothing added and no quotes of its own.

Check That It Worked

Run claude mcp list. The server should be listed as connected. That check is worth doing before you ask anything, because a client that failed to connect does not announce it in conversation, it simply has no tools.

A First Question Worth Asking

Start Claude Code and ask "what tools do you have for my CRM?" to see the catalog. Then ask "who am I connected to?" That second question calls one tool, reaches Follow Up Boss, and names the account it found, which proves the token, the connection and the key in a single round trip. If it answers with your account name, everything on this path is working.

When It Says Failed

Almost always the token. A token that was truncated while being copied, a token that has been revoked, or a header missing the word Bearer all produce the same unhelpful result. Mint a fresh token, use the copy button, and run the command again with the new value.

When Something Goes Wrong covers the failures worth recognizing and what each one actually means.