MCP server

Connect MCP clients to your Listel meetings.

Listel captures your in-person sales conversations with the Listel wearable or the Apple Watch app, then turns them into recaps, action items and CRM notes. The Listel MCP server lets an AI assistant that supports the Model Context Protocol (MCP) read that work for you. Ask your assistant to summarize yesterday's site visit, list what is still open with a customer, or draft a follow-up email.

The server only sees what you allow, and it never sends anything on your behalf.

What you need

A Listel account with access to API tokens.
A Listel API token. You create it in the Listel web app.
An AI assistant or app that can connect to a remote MCP server over Streamable HTTP and send a request header.

Connection details

Setting	Value
Server URL	`https://mcp.listel.ai/mcp`
Transport	Streamable HTTP
Sign-in method	API token sent as a header
Header name	`Authorization`
Header value	`Bearer lst_...` (the word Bearer, a space, then your token)

Connect your assistant

Claude (claude.ai and Claude Desktop)

Claude adds remote servers as custom connectors. Sending a token in a request header is a beta feature that only some Claude organizations have today. If you do not see a Request headers section, your organization does not have it yet.

Open Connectors

In Claude, open Customize, then Connectors.

Add a custom connector

Select + Add, then Add custom connector.

Enter the server details

Enter the name Listel and the server URL above. Select Continue.

Set authentication

Under Authentication, choose No sign in.

Add the Authorization header

Under Request headers, add a header named Authorization with the value Bearer followed by your token (for example, Bearer lst_abc123...).

Finish

Select Add.

Note:

On Claude Team and Enterprise plans, an Owner adds connectors under Organization settings, then Connectors, and everyone who uses that connector shares the same header. A Listel token acts as the person who created it, so a shared token would show that person's meetings to the whole team. Each person should use their own token.

ChatGPT

ChatGPT can add custom MCP servers that use OAuth sign-in or no sign-in. It cannot send an API token in a header, so it cannot connect to the Listel MCP server today.

Grok Bot

See Connect Grok Bot for the quick setup steps.

Any other MCP client

If your client takes a JSON configuration, add this entry and replace lst_... with your token:

{
  "mcpServers": {
    "listel": {
      "type": "http",
      "url": "https://mcp.listel.ai/mcp",
      "headers": {
        "Authorization": "Bearer lst_..."
      }
    }
  }
}

Restart the client after you save the file.

Check the connection

Ask your assistant: "Call whoami on Listel." It should reply with your name, your organization and the token's scopes. If it does, you are ready.

What you can ask

Your assistant picks the right Listel tool for you. Here are a few ideas to start with.

Try asking	Listel tool it uses	Preset needed
"What meetings did I record this week?"	`list_sessions`	Recap only
"Summarize my meeting with the hospital purchasing team and list the decisions."	`get_recap`	Recap only
"What action items are still open from Tuesday's site visit?"	`get_action_items`	Recap only
"Draft a follow-up email from my last meeting."	`draft_follow_up`	Recap only
"Who is on my calendar tomorrow, and have I met any of them before?"	`list_upcoming_events`, `find_person`	Recap + people
"Show me the exact words the customer used about pricing."	`get_transcript`	Full

Other tools: get_recap_pdf gets a meeting's recap as a PDF (never the transcript), and get_session_contacts lists the people linked to a meeting (Recap + people or Full).

Tools

An assistant only sees the tools its token allows.

Tool	What it does	Recap only	Recap + people	Full
`whoami`	Shows who the token belongs to and its scopes	Yes	Yes	Yes
`list_sessions`	Lists your recorded sessions, newest first	Yes	Yes	Yes
`get_recap`	Gets one session's summary, decisions, action items and people	Yes	Yes	Yes
`get_action_items`	Gets only the action items and decisions	Yes	Yes	Yes
`get_recap_pdf`	Gets the recap PDF, never including the transcript	Yes	Yes	Yes
`draft_follow_up`	Drafts a follow-up email. Nothing is sent	Yes	Yes	Yes
`list_upcoming_events`	Lists upcoming calendar events with attendees		Yes	Yes
`get_session_contacts`	Lists the people linked to one session		Yes	Yes
`find_person`	Checks whether you've met someone, and what's still open		Yes	Yes
`get_transcript`	Gets the verbatim transcript, in pages			Yes

Reading `find_person` results

Prefer an email address. A name-only search needs a full name.

Field	Value	Meaning
`status`	`found`	At least one matching person
	`none`	No match in the sessions searched
	`ambiguous`	The name matched people with different emails
	`self`	The search was for you
`match`	`email`	Matched on email
	`name`	Matched on name only, so it's likely but not certain
`attendance`	`spoke`	They spoke in the meeting
	`tagged`	They were tagged during the meeting
	`invited`	They were invited, which doesn't prove they attended
	`met`	Found through your contacts, such as at a networking event

Privacy and permissions

Your data stays yours. Your company owns its Listel data. Listel never sells it and never uses it to train AI models.

A token can only reach your own data. It acts as you and sees nothing you could not see in Listel.

You choose what the assistant sees. Each token has a preset that sets its scopes:

Preset	What the assistant can read
Recap only (recommended)	Meeting list, summaries, decisions, action items and recap PDFs, plus follow-up drafts. Never transcripts or contact details.
Recap + people	Everything in Recap only, plus contact details (`contacts:read`) and your upcoming calendar.
Full	Everything above, plus verbatim transcripts (`transcript:read`) and CRM sync. Use it only for tools you fully trust.

You can also pick Custom and choose scopes one by one. An assistant only sees the tools its token allows.

Follow-up drafts are never sent automatically. draft_follow_up writes a draft for you to review. Nothing leaves Listel until you send it yourself from your own email.

You can turn access off at any time. Go to Settings, then API tokens, and select Revoke. Anything using that token stops working right away.

Keep tokens safe. Treat a token like a password. Use a separate token for each assistant, and choose the shortest expiry that works for you.

Troubleshooting

What you see	What to do
Token is invalid, expired or revoked	Create a new token and update your client
Missing scope	Create a token with a preset that includes that tool
Token placeholder "not expanded"	Your client sent the variable name instead of the token. Paste the full token after the word Bearer, or check how it reads environment variables
A tool isn't listed	The token's preset doesn't include it
An error asks you to slow down	Each token allows about 120 requests per minute. Wait a moment and try again

Questions? Contact team@listel.ai.