> ## Documentation Index > Fetch the complete documentation index at: https://support.metaview.ai/llms.txt > Use this file to discover all available pages before exploring further. # Custom connectors > Connect your own MCP server to use external tools and data in Metaview Sourcing. Role briefs, hiring criteria and company research often live in other tools. Connecting those tools lets you ask Sourcing to use that information without copying it into each search. A custom connector connects an external tool to the [Sourcing agent](https://support.metaview.ai/sourcing/overview.md) using the Model Context Protocol (MCP). You supply the tool's MCP server URL and authentication details, then select the connector for your search. > [!NOTE] > > For Box, follow the dedicated [Box setup guide](https://support.metaview.ai/integrations/box.md). To use Metaview from an AI tool such as Claude or ChatGPT, see [MCP Integration Overview](https://support.metaview.ai/integrations/mcp-integration/mcp-overview.md). ## 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. Available tools and actions depend on the server and the connected account's permissions. Some servers provide read-only access; others also let the agent create or update information when you ask it to. Choose an account or API key with permissions appropriate for your intended use. ## Add a custom connector **1. Open connector settings** In Metaview, open **Settings > Integrations** and select `Manage connectors`, or [open connector settings directly](https://app.metaview.ai/?settings=mcp-connections). 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. Connect your account** Choose the **Authentication type** specified by the provider. > [tab] OAuth > > Select `OAuth`, then `Connect`. Sign in to the external tool and authorise access. You will return to Metaview when authorisation finishes. > > > [accordion] Advanced OAuth settings > > > > Some providers require you to register an OAuth app before connecting. 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`. > > > > Leave these fields blank when the server handles app registration for you. If Metaview asks for app credentials, follow the provider's instructions to obtain them. > [tab] API key > > Select `API key`, then `Add header`. Enter the header name and value exactly as the provider specifies. For example, a bearer token uses: > > | Header name | Value | > | - | - | > | `Authorization` | `Bearer your-token` | > > Replace `your-token` with your token. Add any other headers the provider requires, then select `Connect` to save the connector. For a server that requires no authentication, leave the headers empty. The connector appears in settings with a `Connected` status once setup is complete. ## Use a 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. Include document titles, folder names or company websites where relevant. For a connector that can search and read documents, try: ```text theme={null} Use the Hiring documents connector to find the "Head of Engineering" role brief. Summarise the must-have experience and ask me to confirm the criteria before searching for candidates. ``` The agent can use the tools exposed by the selected server. If it cannot find information or complete an action, check that the server offers the required tool and that the connected account has access. ## Access and workspace sharing Connectors are personal by default. Each person can set up their own connection. If you are a Metaview workspace admin, you can share your own connector. Open **Settings > Integrations > Manage connectors** and turn on `Share with workspace` for that connection. Workspace members can then select it in Sourcing. > [!WARNING] > > A shared connector uses the connected account's permissions. Workspace members can use its available tools with those permissions, including reading or changing information they may not have access to through their own accounts. Share only a connection whose data and actions are appropriate for your workspace. Turn off `Share with workspace` to make the connector personal again. The connection owner manages reconnection and disconnection. ## Troubleshooting | Problem | What to do | | - | - | | Connectors are missing from Integrations | Check that you are in the intended Metaview workspace. Contact [Metaview support](mailto:support@metaview.ai) if they are still missing. | | The server URL is rejected | Use the provider's public HTTPS MCP endpoint on port 443. Localhost, private-network addresses and URLs containing a username or password are not supported. | | Authorisation was cancelled or failed | Try connecting again. For OAuth, check whether the provider requires app credentials or administrator approval. For API keys, check the header names, values and token permissions. | | The connector is saved but the agent cannot use it | Check that it is selected in the Sourcing **Connectors** menu, then verify the server URL and credentials with the provider. | | A tool or document is missing | Check the server's available tools and the connected account's access. For a shared connector, ask its owner to check. | | The connection shows `Reconnect`, or a shared connection is unavailable | The owner should select `Reconnect` in connector settings and authorise again or enter updated API-key headers. | If the issue persists, contact [Metaview support](mailto:support@metaview.ai) with the connector name and a link to the affected search. Keep API keys, tokens and client secrets out of your message. ## Disconnect a connector Open **Settings > Integrations > Manage connectors** and select `Disconnect` on your connection. This stops further requests through that connector, including for workspace members using it as a shared connection. Information already returned in a search remains in that conversation. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.