Skip to main content
Metaview supports the Model Context Protocol (MCP), an open standard for connecting AI tools to data sources. With our MCP, you can connect AI-powered tools like Claude Desktop, Claude Code, Cursor, Windsurf, and other MCP-compatible clients to your Metaview workspace. The AI client will query your sessions, pull summaries, and give you a structured answer. Metaview is an official connector in Claude. This is the easiest way to get started — no configuration files or API keys required.
  1. Open Claude and go to Settings > Connectors
  2. Search for Metaview in the connector catalogue
  3. Click Connect and sign in with your Metaview account
That’s it. Claude now has access to your Metaview interview data, summaries, and reports.
This works with Claude.ai (web), Claude Desktop, and Claude mobile apps — anywhere Claude supports connectors.
Most MCP-compatible clients support OAuth authentication. This is the simplest way to connect — no API key needed. 1. Add the Metaview MCP server URL to your client Add the following to your MCP client configuration: 
{
  "metaview": {
    "type": "http",
    "url": "https://mcp.metaview.ai/mcp"
  }
}
For example, in Claude Desktop, add this to your claude_desktop_config.json under the "mcpServers" key. In Cursor, add it to your MCP settings. Refer to your client’s documentation for the exact location of MCP server configuration. 2. Sign in with your Metaview account When your MCP client connects, it will open a browser window prompting you to sign in with your Metaview account. Once authenticated, your client can access your Metaview data. 3. Start using Metaview data in your AI tools Once connected, your AI tool can access your Metaview interview data, summaries, and reports through the MCP integration.

​
Using an API key

If your MCP client does not support OAuth, you can authenticate using an API key instead 1. Navigate to the MCP integration settings in the Metaview app You can navigate to the MCP settings directly with this link, or navigate through the Integrations page. Toggle on “Use API Key instead of OAuth?” to access the API key management section. 2. Generate a new API key Click the Generate API Key button. Give your key a descriptive name (e.g. “Claude Desktop” or “Cursor”) so you can identify it later. Copy the generated key immediately - you won’t be able to see the full key again. 3. Configure your MCP client Setup varies depending on which MCP client you are using. Follow the instructions for your client below.
If you use Claude, the easiest way to connect is via the official Metaview connector — see Connect with Claude above. The instructions below are for manual setup with an API key.
Claude Desktop does not yet support the HTTP transport format for MCP servers, so you will need to use the mcp-remote bridge via Node.js.Prerequisites: Download and install Node.js if you don’t already have it.
  1. Open Claude Desktop and go to Settings > Developer > Edit Config.
  2. Paste the following into the configuration file, replacing YOUR_API_KEY with the key you copied in step 2:
{
  "mcpServers": {
    "metaview": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.metaview.ai/mcp",
        "--header",
        "Authorization: Bearer YOUR_API_KEY"
      ]
    }
  }
}
  1. Quit Claude Desktop completely and reopen it.
4. Start using Metaview data in your AI tools Once connected, your AI tool can access your Metaview interview data, summaries, and reports through the MCP integration.

​
Managing API keys

You can create multiple API keys, one for each tool or client you want to connect. Each key is named so you can easily identify which tool it belongs to. To revoke access for a specific tool, delete the corresponding API key from the MCP settings page. This immediately prevents that tool from accessing your Metaview data.

​
Security

  • OAuth sign-in uses your existing Metaview account credentials — no extra secrets to manage
  • API keys are scoped to your personal Metaview account
  • Both methods can only access data you have permission to view
  • You can revoke any API key at any time

​
Help and troubleshooting

If you have any issues connecting your MCP client to Metaview, please reach out to us.

​
FAQs

We offer MCP as an optional way for you to access and work with your Metaview data using AI tools like Claude. MCP is an emerging standard that allows AI tools to securely connect to external systems, so if you choose to connect a tool, it gives you a new way to access and interact with your Metaview data.You can already access your data in Metaview through your browser, our MCP simply provides an additional way to work with that same data through your AI tools, such as asking questions, searching, or reporting.
Our MCP enables deeper analysis across your Metaview data. Examples include:
  • Searching across past conversations to find specific topics or responses
  • Reviewing your conversation activity, including interview volume by role or over time
  • Pulling together key points from recent conversations to prepare for a debrief
MCP provides access to your data stored in Metaview, including:
  • Conversation transcripts
  • AI-generated outputs such as AI Notes
  • Metadata associated with your conversations (e.g. role, stage, interviewer)
Access via MCP follows the same permissions as your Metaview account. Users can only access data they already have permission to view in Metaview.
This is best suited for:
  • Recruiting leaders and operations teams
  • Power users who want deeper insights across interviews
  • Teams using AI tools like Claude for analysis
No engineering experience is required, but familiarity with prompting AI tools is helpful.
Yes. MCP is designed to provide secure, permissioned access to your data.
  • Access follows your existing Metaview permissions—users can only access data they already have access to
  • Data is only retrieved when you explicitly request it
  • You control what queries are run and what data is shared with connected tools
As a best practice, many customers check with their legal or data protection teams before enabling the MCP integration, as it allows external tools to access their Metaview data.Our MCP does not introduce any new types of data processing—it simply provides a new way to access and use your existing interview data in Metaview, similar to connecting another integration via API. For teams already using approved AI tools with enterprise settings, this is typically a straightforward third-party integration review.When you use our MCP, you choose which external tools to connect (for example, Claude). Any data sent to those tools is processed by them as a separate third party, and you’re responsible for how they’re used. We provide workspace-level controls so admins can manage and restrict access to MCP if needed. See Workspace Settings for more details.