Skip to content
Open Finlay

Integrations

Finlay MCP

Add Finlay as an MCP connector so Claude, ChatGPT or an IDE client can read your jobs, candidates and candidate conversations, and add candidates to a job.

Connect Finlay to the AI assistant you already use, and ask it about your hiring there: “how is the backend role going”, “tell me about Maya”, “what did Maya say” or “what needs me”. The assistant can also add people it found to a job; otherwise it only reads from Finlay.

In your assistant, add a custom connector (also called a remote MCP server) with this URL:

https://mcp.finlay.ai/mcp
  • Claude: add it as a custom connector. In Claude Code, run claude mcp add --transport http finlay https://mcp.finlay.ai/mcp.
  • ChatGPT: add it as a connector in developer mode.
  • Other MCP clients: add it as a remote server over Streamable HTTP with OAuth sign-in.

Your assistant opens Finlay in the browser. Sign in if asked, check the app, the site you’ll return to and what the app can do, and select Allow access. Only connect apps you trust. The request is valid for 10 minutes; if it expires, start the connection again from your assistant.

Finlay recognizes well-known assistants, such as Claude and ChatGPT, by the site they return you to, and shows their name and logo. For any other app, Finlay can’t verify the name that the app gives itself. The page then names the site instead, for example “An app at connector.example.com wants to connect”, and shows a warning. Allow access only if you added that connector yourself and you trust that site.

Cursor isn’t supported yet: it signs in through a cursor:// link, which Finlay doesn’t accept.

The assistant sees what your role in Finlay lets you see, and nothing more:

  • your jobs and how each one is going
  • candidates on your jobs and their briefs
  • your message threads with candidates
  • what is waiting on you

It can’t send messages, move candidates or change jobs. The one exception is adding candidates.

When your assistant finds people, for example through a web search, GitHub or a list someone sent you, it can add them to one of your jobs by their LinkedIn profile. Most assistants ask you to confirm before they add anyone.

Assistants connected before adding candidates was available can only view. Integrations shows each assistant as View or View and add candidates. To let one add candidates, disconnect it there and connect it again from the assistant.

  • Up to 50 people per request; the assistant splits a longer list.
  • Each needs a first name, last name, current company and LinkedIn profile URL or handle. Finlay identifies people only by the LinkedIn profile. The name and company only label the result.
  • Finlay looks each profile up, assesses it against the job like a candidate it sourced, and adds it to the job’s pipeline. This runs in the background; ask your assistant how the upload went to see each person’s outcome: added, already on the job, not found, over your allowance, or failed.
  • The job must be published or on hold. Closed, filled and draft jobs don’t take candidates.
  • Each person new to your workspace uses one sourced candidate from your allowance. People not found or already on the job don’t. When the allowance is used up, the request is refused. See Plans and limits.
  • Added candidates start as new. If you ask your assistant to shortlist them, they move to the shortlist. When the job’s automated outreach is on, Finlay then messages them from your connected LinkedIn account, within the same daily outreach limit as sourced candidates. See Automated outreach.

A connection stays signed in until one of these happens; then the assistant asks you to connect again:

  • you sign out of Finlay
  • your role or your workspaces change
  • it goes unused for 30 days

To disconnect one assistant only, open Integrations in Finlay and choose Disconnect next to it under Finlay MCP. Connected assistants are listed there with the date you connected them.