Metaview MCP connector
The Metaview connector lets Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent search interview transcripts, notes and sourcing reports in Metaview, with each person signed in as themselves and every request recorded.
- Connects over OAuth
- Free 14-day trial
- No credit card
Summarize what came up across Sarah Chen's interviews this week
Working in Metaview with Elaichi
-
Looked in Metaview
How to connect Metaview to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
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 Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
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. 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.
Metaview MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
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.
What teams do with Metaview through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Metaview is logged.
-
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”
What connecting Metaview gets you
5 screens from Elaichi, each doing one job for your Metaview account.
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, Cursor or Microsoft Copilot
The agent
Ask about any interview and get the answer.
Search Metaview transcripts, notes and sourcing reports in plain language from live records.
Copy the endpoint
AI apps
One endpoint for every client you use.
Claude, ChatGPT, Cursor and Microsoft Copilot reach Metaview through one governed endpoint, with no shared API key.
Toolboxes
Every team gets its own Metaview toolbox.
Recruiting, hiring managers and People each work from a toolbox scoped to them.
Shared connections
Share the connection, never the credential.
One person connects Metaview and teammates search interviews without seeing a login.
Audit log
Know who read which transcript, every time.
Every Metaview search lands in the audit log with who, when and what.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
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 Jake Morgan
Approve Deny -
Post the digest
Metaview
Queued
Workflows
Interview digests write themselves, you approve them.
A schedule fetches the week's Metaview interviews, drafts a digest and waits for approval.
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%
Collections and dashboards
Hiring numbers that refresh without being asked.
Interview volume, sourcing activity and a team breakdown pulled from Metaview on a schedule.
Why connect Metaview's MCP server through Elaichi
Metaview builds and runs this MCP server. Elaichi sits in front of it, so Metaview's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to Metaview's server directly, outside Elaichi, get none of this.
-
One address for every AI client
Claude, ChatGPT, Cursor and Microsoft Copilot reach Metaview's tools at the same Elaichi address as every other connected app. Nobody adds Metaview's server to each client one by one.
-
Each person signs in as themselves
Each person signs in to Elaichi as themselves. Members connect with their own Metaview sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.
-
Rules checked before a call leaves
Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches Metaview's server. By default, a tool Metaview does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.
-
One audit log for every app
Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.
-
Tool issues go to Metaview
Metaview builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Metaview team.
For IT and engineering
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 | Free for one person; $15 per user per month on Gold. | 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.
Questions, answered
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, Microsoft Copilot, 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 role 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 role to searching transcripts and reviewing reports in Metaview and nothing more. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT or any other client cannot run it, whatever the prompt says.
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, Microsoft Copilot 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, Microsoft Copilot, 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 of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot