Phonotheca

Ask Claude about your interviews

Phonotheca runs a remote MCP server, so Claude and other MCP clients can search your transcripts, browse your projects, and quote passages with their speaker and timestamp attached. Read-only, over one revocable token.

What the connection can do

  • Search every transcript in every project at once, the same full-text search as the workspace.
  • Read a speaker-labelled transcript with timestamps, paged for long interviews.
  • Browse projects and interviews, with duration, language, and status.
  • Every returned passage carries its speaker, interview, project, and timestamp, so a quote arrives with its citation.

The connection is read-only. It cannot upload audio, start transcription, edit a transcript, or delete anything, so a connected assistant can never spend your hours or change your corpus.

Get a token

Create an API token in Settings. The token is shown once, and you can revoke it there at any time. The endpoint is:

https://phonotheca.com/api/mcp

Connect from Claude Code

One command, with your token in the header:

claude mcp add --transport http phonotheca \
  https://phonotheca.com/api/mcp \
  --header "Authorization: Bearer YOUR_TOKEN"

Then ask across your corpus in plain language. “Find every passage where a participant talks about pricing” runs the search and returns quotes with citations.

Connect from the Claude API

Pass the server in mcp_servers with the token as the authorization token:

"mcp_servers": [{
  "type": "url",
  "url": "https://phonotheca.com/api/mcp",
  "name": "phonotheca",
  "authorization_token": "YOUR_TOKEN"
}]

Other MCP clients work the same way. The server speaks streamable HTTP, stateless, with bearer authentication.

Tools

  • search_transcripts — full-text search with optional project filter, returns cited passages.
  • list_projects — the workspace's projects with interview counts.
  • list_interviews — a project's interviews with duration, language, and status.
  • get_transcript — a speaker-labelled transcript with timestamps, paged.

Data handling

Requests hit the same EU-resident application and database as the workspace, and nothing about the connection changes where your data lives or who processes it. Transcript text returned to an MCP client goes to whatever assistant you connected, under that assistant's terms, which is the same trade as pasting a transcript into a chat, made explicit. Revoking the token ends access immediately.