- New to connectors? Connectors overview explains how they work and how connected data is accessed, stored and shared.
- Using Airtable, Atlassian, Box or Notion? Metaview has ready-made connectors for these, so you don’t need a custom one. See the Airtable, Atlassian, Box and Notion setup guides.
- Not the same as the Metaview MCP. Custom connectors bring your tools into Metaview. To use Metaview from an AI tool such as Claude or ChatGPT, see MCP Integration Overview.
Requirements
- A Metaview account with access to Sourcing.
- An MCP server reachable at a public HTTPS URL on the standard HTTPS port (443). Ask the tool’s provider for its MCP endpoint and setup instructions.
- Access to the external tool, plus the sign-in or API-key details its MCP server requires.
Review a connector before you connect it
With a custom connector, what the agent can read or change depends entirely on the server you connect, so only connect servers you trust. If your security or admin team wants to review one first, gather these details from whoever built or manages the MCP server:- The tools the server exposes, what each one does and the inputs it accepts.
- Example outputs for each tool, using dummy data.
- Whether any tool can return or accept candidate personal information.
- Whether any tool can create, change or delete records.
- The account or API key the connector will use, and what it can access.
Add a custom connector
1
Open connector settings
In Metaview, open Settings > Integrations and select
Manage custom connectors, or open connector settings directly. Select Add new connector.2
Enter the server details
Enter a Name you will recognise in Sourcing, such as
Hiring documents. In Server URL, enter the MCP endpoint supplied by the provider.3
Choose the authentication type
Select the Authentication type specified by the provider.
- OAuth
- API key
Select
OAuth, then Connect. Sign in to the external tool and authorise access. You will return to Metaview when authorisation finishes.Some providers require you to register an OAuth app first. If so, copy the Callback URL shown in Metaview into the provider’s app settings, then enter the Client ID and Client secret under Advanced OAuth settings. Otherwise, leave these fields blank.4
Check the connection
The connector appears in settings with a
Connected status once setup is complete.Use a custom connector in Sourcing
Open Sourcing and use the Connectors menu beside the message composer to select the connector for your search. Tell the agent which information to use and what you want to do with it. For a connector that can search and read documents, try:Share or disconnect
Your connector is personal by default. Workspace admins can share their own connector by selectingWorkspace on its Personal / Workspace control in Settings > Integrations > Manage custom connectors, or Personal to stop sharing. Workspace members then use it with the connected account’s permissions. Select Disconnect in the same place to stop further requests.
See Access and workspace sharing before you share a connector.
Troubleshooting
If the issue persists, contact Metaview support with the connector name and a link to the affected search. Keep API keys, tokens and client secrets out of your message.