Connect Thirdwatch MCP to Claude

Thirdwatch gives your assistant research tools for supported business directories, job boards, reviews and property sources. Connecting a server makes those tools available; it does not run a search or buy credits by itself.

Add the remote connector

1. In your individual Claude workspace, open Customize → Connectors → + Add → Add custom connector. Organization owners manage connector availability through Organization settings → Connectors.
2. Name it Thirdwatch and enter https://mcp.thirdwatch.dev/mcp as the remote server URL.
3. Choose Register automatically for OAuth client registration, connect and follow Thirdwatch's authorization screen. Sign in to the account whose credits you want to use and review the requested access.
4. Start a chat with Thirdwatch enabled. Ask Claude to inspect its available tools before making a paid request.

An organization's connector controls may require an administrator. If the option is missing, check your workspace policy and Claude's current custom connector documentation. Thirdwatch can be connected as a custom server; this guide does not claim a marketplace listing.

Start with a free check

Try this prompt:

Use Thirdwatch's get_account_info to check my available credits. Then use estimate_cost for search_businesses, query coffee shops in Austin, country US. Show me the preview before running a search.

get_account_info and estimate_cost are free tools. The preview describes the intended tool's credit cost, not a promise that any source will return results. Geography and selected sources affect coverage. Your assistant should show the returned preview rather than repeat a number from an old tutorial.

After reviewing the preview, try a bounded request:

Use search_businesses with query coffee shops, location Austin, country US and max_results 5. Show names, addresses, websites and source links. Leave unavailable fields blank and include warnings.

This is an example input, not a recorded result. Source availability changes. Read the response's metadata and warnings before relying on the answer; a polished summary is not evidence that every source succeeded.

Keep the account and billing clear

Thirdwatch MCP uses your Thirdwatch account and credits. A paid source call can consume credits. Buying or running a standalone Actor in Apify uses separate Apify billing; an Apify account is not required for this connection flow. See current Thirdwatch pricing and your billing dashboard.

Do not paste an API key into a chat message. OAuth authorization avoids putting a long-lived key in the conversation. Disconnect Thirdwatch in your assistant's connector settings when you no longer want it available.

If connection or the first call fails

Check that the URL ends in /mcp, not /register. Confirm that you finished authorization with the intended Thirdwatch account. If tools connect but a paid request fails, check the account balance and the response warnings. A successful connection and a successful research call are separate checks.

For an actionable support report, send the client name, approximate time and tool name through Thirdwatch support. Do not include API keys, authorization codes or access tokens.

Next, follow the company research workflow or the hiring research guide.