TENEKS connector for Claude

Ask Claude about your calls

Connecting TENEKS to Claude lets you ask about your recorded calls in plain language — what a prospect actually said, which objections keep coming back, how a rep is doing this month — without leaving the conversation you are already in.

The connector is read-only. Claude can read your recordings; it cannot change anything in TENEKS. It sees exactly what you see when you log in — no more.

Server URL

https://api.teneks.ai/mcp

A remote MCP server over HTTP. Use this exact URL, with no trailing slash.

Two ways to connect

They are genuinely different. In Claude apps you sign in to TENEKS and approve a consent screen; in Claude Code you paste a token you mint yourself. Pick the one that matches where you use Claude.

claude.ai, Desktop and mobile

1
In Claude, open Customize › Connectors and choose Add custom connector.
2
Paste the server URL https://api.teneks.ai/mcp and add it.
3
Click Connect. Claude sends you to TENEKS to sign in.
4
Approve the consent screen. Claude returns connected, and the four tools below become available.

Each person authorises individually and sees only their own calls. Connecting your account does not connect your colleagues, and does not widen what you can read.

Claude Code

The terminal has no browser to send you to, so it uses a personal access token instead.

1
Sign in to TENEKS and open Connect to Claude in the profile menu — or go straight to /app/settings/api-tokens.
2
Create a token and copy it. It is shown exactly once and cannot be retrieved again — if you lose it, delete it and create another.
3
Run this in your terminal, with your token in place of <token>:

claude mcp add --transport http teneks https://api.teneks.ai/mcp --header "Authorization: Bearer <token>"

Requires Claude Code installed on the machine you run this on.

What Claude can do once connected

Four tools. Every one of them reads; none of them writes. You do not call them by name — you ask a question, and Claude picks.

describe_workspace

Whose recordings are visible, and what the filters accept.

Reports whose recordings this connection can read, how many there are, the date range they cover, and the exact call-type and rep names that the other tools accept as filters. Claude calls this first, because guessing a label is the most common reason a query comes back empty when data exists.

list_conversations

Recordings newest first, with filters. Metadata only.

Lists recordings newest first, filterable by call type, rep and date range. It returns metadata only — no transcript text. A filter that matches nothing in the workspace is reported back rather than silently returning an empty list, so a misspelled name never looks like an absence of calls.

get_transcript

What was said on one recording, as speaker-attributed turns.

Returns what was said on a single recording as speaker-attributed turns, using TENEKS’s own speaker attribution where it has identified who was talking. Long calls are paged, so Claude can read a two-hour call without truncating it.

ask_teneks

A grounded answer to a question across many recordings.

Answers a question across many recordings at once — recurring objections, how a rep is doing, what changed month over month — grounded in the underlying calls. It can come back marked incomplete, which means the answer could not be fully grounded and should not be repeated as fact.

Things to ask

“What objections came up most in my calls last month?”
“Summarise my three most recent discovery calls.”
“What did the customer actually say about pricing on Tuesday’s call?”
“Which of my calls this quarter scored worst, and why?”

What the connection can and cannot reach

The part worth reading before you connect, or before you let your team.

Read-only

Every tool reads. Nothing Claude does through this connector modifies TENEKS — no recording, score, note or setting can be created, edited or deleted.

Scoped to you

Access is scoped to exactly what that user can already see in the web app. A rep reaches their own calls; a manager reaches their team’s. Connecting Claude grants nothing the account did not already have.

Stops immediately

A token or an approved grant stops working at once if:

the account is deactivated
the workspace is disabled
the person is moved to another workspace
the plan loses Claude access

Some plans do not include Claude access. If the “Connect to Claude” page is not in your profile menu, your plan is one of them — ask your workspace owner, or see the plans.

If something looks wrong

A question about a specific rep or call type comes back about everything: Filters match your workspace’s own labels exactly, and a filter that matches nothing is reported rather than quietly returning an empty list — so the answer is broader than the question you asked. Ask Claude to describe the workspace first; it will come back with the exact call-type and rep names that work.
An answer is marked incomplete: That means the answer could not be fully grounded in the underlying recordings. Treat it as a lead, not a finding — narrow the question to a shorter period or a single rep and ask again.
A connection that used to work has stopped: Check the four conditions above first — a workspace move in particular ends a token permanently while everything about it still looks healthy. In Claude Code, delete the old token in TENEKS, create a new one, and run the setup command again. In the Claude apps, remove the connector and connect again.
You lost the token: It cannot be shown again. Delete it and create another — deleting takes effect immediately, so it is also the right move if a token has ended up somewhere it should not be.

Already a TENEKS customer?

Everything you need is in the app. Sign in, open Connect to Claude from the profile menu, and you are two minutes from asking Claude about last week’s calls.