Skip to content
1Namecard

Connect

Let an assistant work your leads.Twelve tools, no delete.

A Model Context Protocol server over HTTP, using the same tokens and limits as the API, with read-only tokens for a safe start.

Start freeSee pricing
An assistant asking for hot leads nobody has touchedSample data

Assistant

Connected over MCP

Scopes: read, write

Which hot leads from DataWorks haven’t been contacted yet?

Used 1Namecard: list_leadsNeeds the read scope
{
  "stage": ["new"],
  "band": "hot",
  "from": "2027-04-20",
  "to": "2027-04-21",
  "sort": "score"
}

Two hot leads are still in New:

  • Mia Fischer, Harbourline Freight, score 75
  • Jonas Keller, Orchard Cold Chain, score 68

Want me to assign them?

Move Mia to Contacted and give me a short link for her badge.

Used 1Namecard: update_lead_stageNeeds the write scope
{
  "id": "6f1c3a52-...",
  "stage": "contacted"
}
Used 1Namecard: create_redirectNeeds the write scope
{
  "key": "dw27-mia",
  "target": "https://kestrel.1namecard.com/dana-reyes",
  "note": "Badge link for Mia Fischer"
}

Done. Mia Fischer is now Contacted, and her first contact time is recorded.

Her badge link: kestrel.1namecard.com/dw27-mia

In short

The 1Namecard MCP server gives an AI assistant access to your leads. It is a Model Context Protocol endpoint at /api/mcp with twelve tools to list and read cards, short links and leads, read the funnel, move a lead's stage, assign an owner, add a note and create a short link. It uses the same tokens and limits as the REST API, and it has no delete tools.

Last updated

What it does.

  • Speak MCP over HTTP.

    The endpoint is /api/mcp. It is stateless Streamable HTTP: every request answers JSON, with no session to keep. Any client that supports MCP over HTTP with a custom header can connect.

  • Share the API's tokens and limits.

    One token from the API page works for REST and MCP. The limit is 600 requests per 10 minutes per token. A list returns at most 200 rows.

  • Offer twelve tools.

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

  • Find the leads that need a call.

    list_leads takes the admin's filters: stage, owner, card, band, quick filters such as untouched for 48 hours, dates and sort. "Which hot leads has nobody touched" is one call.

  • Summarise the funnel.

    funnel returns views, saves, leads, meetings, qualified and won for 7, 30 or 90 days, the event or a custom range, grouped by rep, placement or card.

  • Make small, reversible changes.

    An assistant can move a lead to any stage, set its owner, add an internal note and create or edit a short link. Changes are logged under the person who made the token.

  • Leave out delete tools, on purpose.

    No tool removes a card, lead or short link. Removal stays in the admin. A read-only token can read, and gets forbidden from the write tools.

12

tools for an assistant to use

600

requests per 10 minutes, shared with the REST API

0

delete tools, on purpose

How it works in three steps.

  1. Step 01

    Create a token.

    Open API and choose read only to begin. Add write later if you want the assistant to change records.

  2. Step 02

    Add the server to your MCP client.

    Use the address shown on the API page, which ends in /api/mcp, the transport streamable HTTP and the header Authorization: Bearer <token>.

  3. Step 03

    Ask a question.

    Try "which hot leads has nobody touched" or "summarise the funnel by rep for the current event".

The call behind the answerSample data
GET /api/v1/leads?stage=new&band=hot&limit=2
Authorization: Bearer nwc_...
{ "data": [
    { "id": "6f1c3a52-...", "name": "Mia Fischer",
      "stage": "new", "score": 75, "band": "hot",
      "placement": "dw27-badge", "consent": true }
  ],
  "page": 1, "limit": 2, "total": 9, "pages": 5 }

Sample request and response. Tokens are read-only or read and write, shown once and revocable.

Who it is for.

  • Sales leaders

    You want the funnel by rep in plain words.

    1Namecard for sales teams

  • Reps

    You ask for hot leads you have not called, then log the call.

  • Builders of internal assistants

    You wire leads into an assistant your company runs.

Limits by plan.

  • Included: Every plan has the MCP server.
  • Included: Each token may make 600 requests per 10 minutes, shared with the REST API.
Compare plans in detail

What it does not do yet.

  • Not included: The server only answers requests, so nothing is pushed to the assistant. For push, use signed webhooks.
  • Not included: Every HTTP request counts toward the 600, not every tool call.
  • Not included: It is tested through the official MCP SDK. Clients differ, so try a read-only token first.
  • Not included: A token acts as an admin: the assistant can read every lead in the organisation.

What AI assistant access to leads looks like.

  • "List the hot leads nobody has touched." The assistant calls list_leads with stage new and band hot.
  • "Summarise the funnel by rep for the show." It calls funnel with the event range grouped by rep.
  • "I called Mia Fischer and she wants a quote." It adds a note and moves the stage.
  • "Make a short link called ice-door for Dana's card." It calls create_redirect.

Review what an assistant writes. It can misread a question or a lead, so start read-only and add write access once you trust the answers. Changes appear in the activity log.

Treat lead data as personal data.

The server tells the assistant that lead data is personal data. You decide who holds a token. Whatever an assistant reads goes to the model behind your client, so check that the provider's terms fit your data protection duties before you connect real leads.

The Model Context Protocol is open, and the server does not depend on one assistant. Scripts reach the same data through the REST API.

Questions about this feature.

What is an MCP server?

The Model Context Protocol is an open protocol that lets an AI assistant call tools in another system. Ours exposes twelve tools for cards, short links, leads and the funnel.

Which assistants can connect?

Any client that supports MCP over HTTP and lets you set an Authorization header. We do not list partner products.

Can an assistant delete my leads?

No. There are no delete tools by design. Removing a lead or all data for one e-mail address is done in the admin.

Is it safe to give an assistant a token?

Start with a read-only token, held only by people allowed to see leads. Lead data is personal data. You can revoke a token at once on the API page.

Does the MCP server cost extra?

No. Every plan has every feature, including the API and the MCP server.

Keep reading

All features

Try it on your next show.

Start freeTalk to us