Metaview MCP connector
The Metaview connector lets Claude, ChatGPT, Cursor and the Elaichi Agent search interview transcripts, notes and sourcing reports in Metaview, with each person signed in as themselves and every request recorded.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Metaview to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Metaview once
-
Open Connections, choose Add connection, and pick Metaview.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Metaview. Metaview's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Metaview MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Metaview MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Metaview MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Metaview to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Metaview through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Recruiting
Catch up on a candidate before debrief
Ask for what came up across a candidate's interviews and get the themes pulled from the transcripts and notes in Metaview, not a memory of who said what.
-
Hiring managers
Check what the panel actually asked
See which questions each interviewer covered for a role so the next round fills the gaps instead of repeating them.
-
Talent sourcing
Review this week's sourcing activity
Pull outreach and pipeline numbers from Metaview reporting for a role and compare them with last week without opening a dashboard.
-
Interviewers
Find the moment a candidate explained a decision
Search a transcript for a specific topic, like how the candidate handled a missed deadline, and read that part of the conversation.
-
People
Spot inconsistent interviewing across teams
Look at how interviews run for the same role across different panels to see where structure, question coverage or depth drifts.
-
Leadership
Get a hiring update in plain language
Ask how a critical search is going and get interview volume, sourcing activity and recurring candidate feedback summarized from Metaview.
Try asking
- “Summarize what came up across Sarah Chen's interviews this week”
- “Which questions did the panel ask about leadership for the PM role?”
- “Show sourcing activity for the Backend Engineer search since Monday”
Compare
Elaichi vs Zapier MCP vs Composio for Metaview
All three can connect Metaview to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Metaview tools | Allow or restrict single Metaview tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Metaview call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
See it in Elaichi
What connecting Metaview gets you
5 screens from the product, each doing one job for your Metaview account.
The agent
Ask about any interview and get the answer.
Search Metaview transcripts, notes and sourcing reports in plain language from live records.
- interviews
- transcripts
- notes
- reports
Ask Elaichi to work across your apps.
Summarize what came up across Sarah Chen's interviews this week
Which questions did the panel ask about leadership for the PM role?
Show sourcing activity for the Backend Engineer search since Monday
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint for every client you use.
Claude, ChatGPT and Cursor reach Metaview through one governed endpoint, with no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Toolboxes
Every team gets its own Metaview toolbox.
Recruiting, hiring managers and People each work from a toolbox scoped to them.
- Recruiting
- Hiring managers
- Talent sourcing
- Interviewers
ElaichiToolboxesShared connections
Share the connection, never the credential.
One person connects Metaview and teammates search interviews without seeing a login.
- Recruiting
- Engineering hiring
- Sales hiring
- Sourcing
ElaichiConnectionsAudit log
Know who read which transcript, every time.
Every Metaview search lands in the audit log with who, when and what.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
Interview digests write themselves, you approve them.
A schedule fetches the week's Metaview interviews, drafts a digest and waits for approval.
Metaview digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch interviews
Metaview
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Metaview
Queued
Collections and dashboards
Hiring numbers that refresh without being asked.
Interview volume, sourcing activity and a team breakdown pulled from Metaview on a schedule.
Metaview health
Refreshed 4 minutes ago · every 15 minutes · from the interviews collection
Interviews
1,284 ↓ 12%
Transcripts
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Interviews created
Last 14 days
By team
Share of activity
Recruiting 34%
Engineering hiring 27%
Sales hiring 21%
Sourcing 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Metaview to Claude?
Connect Metaview in Elaichi first, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. The Metaview step is a standard sign-in screen: you log in with your Metaview account and approve access, and there is no client ID or secret to generate. Once that is done, Claude can search interview transcripts and notes in Metaview as you.
Does Metaview work with ChatGPT and Cursor as well as Claude?
Yes. Connect Metaview once in Elaichi and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any MCP client and the Elaichi Agent. You do not set Metaview up again for each one.
What can an AI agent actually do with my Metaview data?
It can search interview conversations, transcripts and notes in Metaview, pull out themes across a candidate's interviews, and review sourcing activity and reporting for a role. Short, concrete asks work best, such as the questions one interviewer asked about leadership, rather than long open-ended requests. What is available depends on what your account has set up in Metaview.
Does connecting Metaview give the AI every interview and every candidate?
No. The AI works inside the Metaview access of the person who signed in, so an interviewer who can only see their own interviews gets only those, and nobody gets more than Metaview already allows them. Elaichi can narrow that further for a team and never widens it.
Can I stop an agent from changing things in Metaview?
Yes. Restrictions in Elaichi apply per action, so you can limit a team to searching transcripts and reviewing reports in Metaview and nothing more. A restricted action is never shown to Claude, ChatGPT or any other client, so no prompt can reach it.
What happens to a Metaview connection when someone leaves?
Offboarding that person in Elaichi ends their Metaview access through every client at once. A shared Metaview connection keeps working for everyone else on the team. If you disconnect Metaview in Elaichi, it is removed from Claude, ChatGPT, Cursor and every other client in one step.
Does the Metaview MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Metaview is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Metaview?
Yes. Both let Claude, ChatGPT or Cursor use Metaview. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Metaview call.
How is Elaichi different from Composio for Metaview?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Metaview: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Metaview in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.