Connect an MCP client.

Connect the client.

1. 01
   Step 1.

   Open API and press Create token, as in Create an API token. For an assistant that should only look, tick read and leave write unticked.

   API
2. 02
   Step 2.

   In your MCP client, add a remote server. Use the address https://app.1namecard.com/api/mcp and the transport streamable HTTP.

3. 03
   Step 3.

   Add a header named Authorization with the value Bearer followed by a space and your token.

4. 04
   Step 4.

   In Claude Code this is one claude mcp add command with --transport http, the address and a --header option. The Use it panel on the API page shows the command, labelled Claude Code (MCP). Check the result with claude mcp list.

5. 05
   Step 5.

   Ask the assistant something that only reads, such as the newest hot leads. If it answers with your data, the connection works.

6. 06
   Step 6.

   When you stop using the client, press Revoke next to the token on the API page.

The twelve tools.

• Read: list_cards, get_card, list_redirects, list_leads, get_lead, stats_summary and funnel.
• Write: create_redirect, update_redirect, update_lead_stage, assign_lead and add_lead_note.

A redirect is a short link. A read-only token can list and read, and the write tools answer with a forbidden error. They stay in the tool list, so the assistant can see them and fail politely. There are no delete tools on purpose: removing records stays in the admin, where a person decides.

How it behaves.

The MCP server uses the same tokens, scopes and limit as the REST API: 600 requests per 10 minutes per token, REST and MCP together, and the set-up messages count too. A missing, wrong or revoked token gets a 401, and a token over the limit gets a 429. Actions taken with a write token appear in Activity under the person who created the token.