Connect Claude Code

Claude Code connects to remote MCP servers over HTTP, so adding VitalWall takes one command.

1. Create a token

Go to API Tokens in your account and choose Generate New Token. Give it Read Walls and Write Items, and add Manage Walls if the agent should create walls or add domains. The token starts with vw_live_ and is shown once, so copy it before you close the dialog.

2. Add the server

Run this in your terminal with your token in place of the placeholder:

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

That adds it to the current project, for you only. Add --scope user to use it in every project:

claude mcp add --transport http --scope user vitalwall https://vitalwall.com/mcp \
  --header "Authorization: Bearer YOUR_VITALWALL_TOKEN"

Or share it with your team

To check the server into a repo, put it in .mcp.json at the project root. Claude Code fills in ${VITALWALL_TOKEN} from each person's environment, so no token is committed.

{
  "mcpServers": {
    "vitalwall": {
      "type": "http",
      "url": "https://vitalwall.com/mcp",
      "headers": {
        "Authorization": "Bearer ${VITALWALL_TOKEN}"
      }
    }
  }
}

Everyone then sets VITALWALL_TOKEN to their own token. Claude Code asks once before it uses a server from a project file.

3. Check it works

Run /mcp inside Claude Code. VitalWall should show as connected, with its tools listed. Then ask: “List my VitalWall walls.”

If it shows as failed, run claude mcp get vitalwall to see the saved address and header, and check the troubleshooting list.

Next steps

  • Examples: prompts for deploy notices, an agent activity wall and adding a visitor globe to a site.
  • Tool reference: every tool, its inputs and the scope it needs.
  • Troubleshooting: what each error means and how to fix it.

Other clients