Connect Wellfound Reach to your AI assistant

Connect your AI assistant to Wellfound Reach to search for candidates, manage recruiting agents, shortlist candidates or mark them Not a fit, and work with company lists.

Quick start: ask your AI assistant

Share this article with your AI assistant and ask it to help set up the connection. Try this prompt:

Read https://help.wellfound.com/article/1221-connect-wellfound-reach-to-your-ai-assistant and help me connect my Wellfound Reach account.

If your assistant supports setting up MCP connections, it can use this guide to configure Reach. Complete any sign-in and approval steps it opens. If it cannot add the connection itself, follow the setup instructions below.

MCP access is free until October 1, 2026. You can connect without a paid Reach plan during this period.

Already connected Wellfound to your AI assistant?

Wellfound Reach uses a separate MCP server and authorization. A connection to wellfound.com does not connect your Wellfound Reach account. Follow these instructions to add another connection for reach.wellfound.com.

Before you connect

You need:

An active Wellfound Reach account and membership in an organization.
An AI assistant that supports remote Streamable HTTP MCP servers and browser-based OAuth.
Permission from your organization to use your chosen AI provider with recruiting and candidate data.

The connection acts with your existing Wellfound Reach permissions. For example, reviewers can read projects assigned to them but cannot manage recruiting agents.

Connect to Claude

Connect Wellfound Reach to Claude

The button opens Claude’s custom-connector form with the connector name and server URL prefilled. It does not authorize access automatically.

Sign in to Claude if prompted and review the connector details.
Continue through Claude’s confirmation steps.
When asked to authorize the connection, sign in to your account at reach.wellfound.com .
Confirm that the authorization page shows the correct Wellfound Reach organization and review the requested permissions.
Approve the connection, return to Claude, and enable Wellfound Reach for your conversation.

Claude Team and Enterprise

An Owner or Primary Owner may need to add the custom connector in Organization settings → Connectors before members can use it.

Once it has been added, each member must connect their own Wellfound Reach account. Adding a connector for the Claude organization does not give everyone access to your Wellfound Reach account.

Manual Claude setup

If the shortcut does not open the form, open Customize → Connectors in Claude and choose Add custom connector. Enter:

Name: Wellfound Reach
Server URL: https://reach.wellfound.com/mcp

Then complete the Wellfound Reach sign-in and authorization steps.

Connect to Codex

Desktop app

Open Settings → MCP servers and choose Add server.
Enter Wellfound Reach as the name.
Select Streamable HTTP.
Enter https://reach.wellfound.com/mcp as the server URL.
Save the server and restart the MCP connections when prompted.
Choose Authenticate beside the server if sign-in is required.
In your browser, sign in to reach.wellfound.com , verify the organization and requested permissions, and approve the connection.
Return to Codex and confirm that Wellfound Reach is enabled.

You can use /mcp in the composer to inspect your connected servers.

Command line

Run:

codex mcp add wellfound-reach --url https://reach.wellfound.com/mcp

Complete the browser sign-in that opens. If authentication is still required, run:

codex mcp login wellfound-reach

Restart your Codex session, then use /mcp to verify the connection.

MCP connections are configured separately on each Codex host. Connecting on your laptop does not automatically configure a different remote host.

Connect another compatible MCP client

Use these settings:

Setting	Value
Name	Wellfound Reach
Server URL	`https://reach.wellfound.com/mcp`
Transport	Streamable HTTP
Authentication	OAuth
Credentials	Automatic OAuth; no API key or copied access token is required

Your client must support remote MCP connections, OAuth, and dynamic client registration.

Opening the server URL directly in a browser may display 405 Method Not Allowed. This is expected because the URL is a tool endpoint, not a webpage. Add it through your assistant’s MCP or connector settings instead.

What your assistant can do

Depending on your Wellfound Reach role, project permissions, plan, and the permissions you approve, your assistant can:

Read projects, recruiting agents, search configurations, and search diagnostics.
Create recruiting agents and prepare search changes.
Preview candidate pools before saving search changes.
Start, stop, or continue searches.
Review candidate profiles and evaluation evidence.
Shortlist candidates or mark them Not a fit.
Read, create, and update company lists.

The connection does not expose candidate contact information, and none of these tools sends outreach.

Build recruiting workflows with your agent

Once connected, your agent can experiment with sourcing approaches and combine Reach with the other tools it can access. Use these recipes as starting points, replacing the role, organization, project, and requirements with your own.

Experiment with searches

Ask your agent to test several approaches, inspect the candidates each returns, and use the results to refine its next attempt. It can preview candidate pools before saving changes to an existing search.

Use these requirements for [role] in [project]: [requirements]. Test several sourcing approaches in Reach, review sample candidates and evaluation evidence, and refine the approaches based on what you find. Keep the must-haves fixed. Compare the most promising searches and explain the tradeoffs before saving changes.

Build a daily shortlist

Your assistant must support scheduled tasks that can use connected tools. Set up the task in your assistant, specify the time and timezone, and confirm the Reach connection is available where the task runs. Scheduling is managed by your assistant.

Every weekday at [time and timezone], review new candidates for [role] in [project] at [organization]. Check them against [requirements], add the strongest matches to my Reach shortlist, and summarize the evidence and gaps. Skip candidates already shortlisted or marked Not a fit.

Refine searches using new ATS feedback

Connect your ATS to the assistant separately and confirm it can read the relevant role and interview feedback. The Reach MCP connection does not automatically give your assistant access to your ATS. You can also use hiring notes from other connected tools.

Before the next sourcing run for [role], review new interview notes and hiring manager feedback in my connected ATS. Use that feedback to refine the Reach searches, keep our must-haves fixed, and summarize what changed and why. If the feedback conflicts with the requirements, ask me to clarify.

You can combine these steps into one recurring task: review new feedback, experiment with searches, then review and shortlist candidates.

Some actions run in the background. Your assistant should wait for the operation to finish instead of submitting the same request repeatedly.

Useful starter prompts

Replace the organization, project, and role details before using these prompts:

“Use these hiring requirements to suggest three different candidate searches: [requirements]. Explain what each search prioritizes and preview the candidate pools.”
“Try different titles, skills, and company backgrounds for [role]. Keep these must-haves: [requirements]. Compare the candidates each search finds.”
“The results for [agent] are too [broad/narrow]. Use these examples of good and poor matches: [feedback]. Try revised searches and recommend the best one.”
“Review the candidates for [agent] against these requirements: [requirements]. Show me the strongest matches and explain why they fit.”
“Shortlist [candidate names or IDs] for [project]. Summarize how each meets these requirements: [requirements].”

Disconnect Wellfound Reach

Remove or disable Wellfound Reach from your assistant’s connector or MCP settings.

For Codex CLI, run:

codex mcp logout wellfound-reach
codex mcp remove wellfound-reach

Disconnecting the existing wellfound.com connector does not disconnect Wellfound Reach, and disconnecting Wellfound Reach does not remove the wellfound.com connection.

Troubleshooting

What you see	What to check
The MCP URL shows 405 in a browser	Add the URL through your assistant’s remote MCP settings instead of opening it as a webpage.
Wellfound is connected, but no Reach tools appear	Add `https://reach.wellfound.com/mcp` as a separate server. The `wellfound.com` connection does not include Wellfound Reach.
You are asked to upgrade your plan	MCP access is free until October 1, 2026. If you are asked to upgrade while connecting during this period, confirm the Reach account and organization, then contact Wellfound Support if the prompt persists.
No organization or projects appear	Confirm that you signed in to the correct Wellfound Reach account and that you have access to the expected organization and projects.
No tools appear after connecting	Enable the server for the current conversation, then refresh or restart the AI client.
The client requests an API key or local command	Confirm that you selected remote Streamable HTTP with automatic OAuth.
A change is taking a long time	Ask the assistant to check the existing operation’s status instead of submitting the action again.
You see a sign-in or authorization loop	Remove the connection, add it again, and verify the account and organization shown on the authorization page.
A scheduled sourcing task does not run	Confirm that your assistant supports scheduled tasks with connected tools and that the Reach connection is available in the environment where the task runs. The schedule is managed by your assistant.
Your assistant cannot read ATS feedback	Connect your ATS to the assistant separately and confirm it can read the relevant role and feedback. Connecting Reach does not automatically grant the assistant access to your ATS.