Metaview

Query interview transcripts, AI notes and recruiting data.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Metaview connector does

The Metaview MCP server connects an AI-notetaker workspace for job interviews to Claude, ChatGPT and any MCP-compatible agent. It reads interview transcripts, AI-generated notes, conversation metadata and sourcing records, and it writes reports, AI fields and candidate sequence enrolments. Anthropic's directory lists 16 tools; Metaview's own workflow documentation names 19 more.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Metaview tools (16)

  • get_user_context
  • search_conversations
  • group_conversations
  • get_chart_data
  • list_fields
  • list_field_values
  • create_ai_field
  • create_report
  • search_reports
  • get_enrichment_status
  • list_sequences
  • manage_sequence
  • list_sequence_candidates
  • manage_candidate_sequence
  • find_candidate_in_sequences
  • list_send_on_behalf_permissions

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • The consent screen has nothing to narrow. The server's RFC 9728 descriptor returned scopes_supported as an empty array on 2026-08-21, and its authorization server advertises only email, offline_access, openid and profile. There is no read-only grant, so authorising the connector authorises everything the account can already do.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter detail, readOnlyHint or destructiveHint is published here. The read/write split above is derived from tool names and Metaview's prose.
  • The directory listing is incomplete. 19 tool names appear in Metaview's documentation and not in Anthropic's listing, including the ATS write. Assume the surface is larger than the 16.
  • Not every session has a transcript. Metaview states the bot can join a call and produce nothing — too short, ended early, or a processing failure — and those sessions still appear in search results. Its fix is to filter explicitly to conversations that have a transcript.
  • Unclassified calls default to "Job Interview", which skews any analysis in a workspace that records mixed conversation types.
  • Volume is expensive. Metaview puts one hour of transcript at roughly 10,000–15,000 tokens and recommends full transcripts only for 1–5 conversations, summaries for 5–20, and structured AI fields beyond 20.
  • Candidate identity is unreliable by name. Where no name is on record, Metaview falls back to displaying an email address or phone number as the participant's display name.
  • Some capability is plan-gated. Metaview documents Reports as a premium feature, sourcing enrichment as credit-metered and non-refundable, and MCP access as controllable per workspace and separately for non-admins.
  • Automatic scorecard posting is not an MCP tool. Metaview's scorecard autofill and automatic ATS submission are Metaview app settings, not part of the MCP surface. We found no MCP tool in either source that creates or submits a scorecard.

Frequently asked questions

What data does the Metaview MCP server expose to an AI assistant?

Job-interview content. Metaview's MCP documentation lists conversation transcripts, AI-generated Notes, conversation metadata such as role, stage and interviewer, and Sourcing data including searches, surfaced candidates and candidate feedback. Its workflow guide adds scorecards and structured fields. Transcripts are recordings of named candidates answering questions, so third-party speech enters the model's context.

Can the Metaview connector write anything into my ATS?

Not among the 16 tools Anthropic lists, but yes among the tools Metaview documents. Its Sourcing Copilot workflow names post_sourcing_candidates_to_ats, describing it as capped at 50 candidates per call, roughly two minutes asynchronous, and irreversible from Metaview, with the agent's reasoning posted as a profile note. That tool is absent from the directory listing.

Can the connector send email to a candidate?

Indirectly, and this is the most consequential thing on the surface. manage_candidate_sequence adds a candidate to a Sequence, and Metaview documents Sequences as automated multi-step outreach sent from your own connected Gmail or Outlook mailbox. The tool name reads as bookkeeping; the effect is real email to a real person from your address.

Does Metaview train AI models on interview transcripts?

No. Metaview's privacy and security overview states plainly that it does not use customer data for AI model training, and that it uses existing pre-trained models from LLM partners to deliver its services. It describes itself as a data processor that does not own the personal data it processes, with customers retaining ownership.

Do candidates know an interview is being recorded?

That is the customer's responsibility, and Metaview publishes guidance rather than enforcing it. It recommends notifying participants in advance, explaining the purpose, and offering an opt-out, and it offers a managed notice form that records responses. Metaview states it does not provide any option to hide the notetaker from participants in a meeting.

What OAuth permissions does the Metaview MCP server request?

None that narrow anything. Reading the server's own RFC 9728 descriptor on 2026-08-21 returned scopes_supported as an empty array, and its authorization server advertises only email, offline_access, openid and profile — identity claims, not application permissions. The consent screen therefore offers no way to grant reading without also granting the writes.

Who in my workspace can connect Metaview to Claude, and what can they see?

Any member an admin permits, and each sees only their own permitted data. Metaview documents two workspace toggles: one enabling the MCP integration at all, one enabling it for non-admins. Access mirrors existing Metaview permissions, so an admin reaches every conversation in the workspace while a member reaches only their own and those shared with them.

Why did the connector label an internal meeting as a job interview?

Because unclassified calls default to that type. Metaview's MCP guide states that when a conversation's type has not been set, the MCP defaults it to Job Interview, so portfolio reviews, exploratory chats and internal syncs can be miscounted. Its suggested fix is to group results by call type and flag classifications that may be unreliable.

Sources

More Productivity connectors

  • 6sense

    Ask an AI agent about 6sense account insights, buying signals and keyword trends.

  • Adobe Workfront

    Find, create, update and delete Workfront work items from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Metaview to work.

Connect Metaview once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio