TENEKS connector for Claude

Ask Claude about your calls

TENEKS is in Claude’s connector directory. Connect it once and ask about your recorded calls and meetings in any chat: what a customer said about pricing, which next steps were agreed, which objections keep coming back.

The connector is read-only. Claude can read your recordings, but it cannot change anything in TENEKS. Its access matches your account permissions.

Using ChatGPT, Codex or Grok? See all setup guides

In the connector directory

TENEKS-MCP

By TENEKSAI OÜ · Ask Claude what was said in your calls and meetings

  • Describe the connected workspace
  • Find accessible recordings
  • Read speaker-attributed transcripts
  • Ask questions across recordings

Requires a TENEKS account with processed recordings. Works on claude.ai, in Claude Desktop and in the mobile apps.

Connect in three steps

In the Claude apps there is nothing to copy. You sign in to TENEKS once and approve a consent screen, and Claude keeps the connection. Claude Code in the terminal uses a token instead.

From the connector directory

  1. 1
    Open the TENEKS listing in Claude, or search for TENEKS under Customize › Connectors, and click Connect.
  2. 2
    Claude sends you to TENEKS. Sign in and approve the consent screen.
  3. 3
    Back in Claude, ask a question about your calls. Claude picks the TENEKS tools it needs.
Open TENEKS in Claude

Each person connects individually and sees only what their own account can see. Connecting your account does not connect your colleagues. In a Claude Team or Enterprise organization, an owner may have to allow the connector first.

Claude Code

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

  1. 1
    Sign in to TENEKS and open Integrations in the profile menu, or go straight to /app/settings/integrations.
  2. 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. 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.

Or add it as a custom connector

If TENEKS does not show up in the directory for you, add the same server yourself. In Claude, open Customize › Connectors, click + Add and choose Add custom connector. Paste the server URL, click Connect, then sign in to TENEKS and approve. The tools and the access are the same.

https://api.teneks.ai/mcp

A remote MCP server over HTTP. Use this exact URL, with no trailing slash. Other MCP clients can find it in the official MCP Registry as ai.teneks/teneks.

What Claude can do once connected

Ask a question and Claude selects from four read-only tools. You do not need to call them by name.

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. The assistant 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 without 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 the assistant can read a two-hour call without truncating it.

ask_teneks

A grounded answer to a question across many recordings.

Answers questions about recurring objections, rep activity or changes across several recordings, using the calls as sources. 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 connector can and cannot reach

Review the access limits before you roll it out to your team.

Read-only

Every tool reads. The connector does not record audio, change recordings, send messages or write to a CRM. No recording, score, note or setting can be created, edited or deleted through it.

Scoped to you

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

Stops immediately

A connection or a token stops working at once if:

  • the account is deactivated
  • the workspace is disabled
  • the person is moved to another workspace

Every TENEKS plan can connect Claude from the directory, trials included. Your recordings are yours, and so is the choice of AI that reads them. Personal access tokens for Claude Code are not on every plan. If Integrations is missing from your profile menu, ask your workspace owner or see the plans.

If something looks wrong

TENEKS does not show up in Claude
In a Team or Enterprise organization, an owner decides which connectors members can use, so ask them to allow TENEKS. Otherwise, add it as a custom connector as shown above. The connection and the tools are the same.
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. Ask Claude to describe your TENEKS workspace first. It comes back with the exact call-type and rep names that work.
An answer is marked incomplete
The answer could not be fully grounded in the underlying recordings. Narrow the question to a shorter period or a single rep and ask again. For an exact quotation, ask for the transcript.
A connection that used to work has stopped
Check the three conditions above first. Moving to another workspace permanently invalidates the existing token. In the Claude apps, disconnect TENEKS under Customize › Connectors and connect again, which takes you through the sign-in once more. In Claude Code, delete the old token in TENEKS, create a new one and run the setup command again.
You lost the token
It cannot be shown again. Delete it and create another. Deletion 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?

Open the listing, sign in with your TENEKS account, and ask Claude about last week’s calls.