Talent Summoner

What the Talent Summoner MCP server does

The Talent Summoner MCP server connects an AI agent to a Talent Summoner account so the agent can assist with candidate sourcing and review. It supports a workflow that begins with defining the target candidate, continues through search and evaluation, and ends with shortlisting and outreach preparation.

An agent can draft an ideal candidate profile for a role, present it for review before searching, run searches, adjust criteria, and find additional candidates within the same sourcing session. It can also help review candidates, add them to a shortlist, request work-email lookups, and prepare outreach drafts.

The service is intended for hiring workflows where a person remains involved in decisions and outreach. The agent asks before unlocking a Role for a session, while outreach must be reviewed and confirmed on the Talent Summoner website before it is sent.

How it works

Talent Summoner provides a remote MCP endpoint at https://talentsummoner.com/api/mcp. The connection uses Streamable HTTP and supports OAuth 2.1 with PKCE or an API key supplied as a Bearer token. The repository also provides a companion skill containing workflow instructions for supported AI agents.

The standard setup path uses the @talent-summoner/setup package. It installs the MCP connection and skill for the agents selected during setup, then checks the connection. After restarting or reopening an agent, a user can ask it to show available Talent Summoner sourcing sessions.

Claude Code has an alternative plugin installation. That plugin connects to the same remote service and asks the user to sign in with a Talent Summoner account when a tool is first used. It does not run local code, hooks, or scripts.

Setup and configuration

Create an API key in Talent Summoner, then run npx @talent-summoner/setup from an interactive macOS or Linux terminal, Windows PowerShell session, or Windows Command Prompt. Node.js 22.20 or newer is required. During setup, choose the AI agents to configure and enter the key into the hidden terminal prompt. Keep the key out of agent chats, shell commands, and Git repositories.

For Claude Code, install the plugin with /plugin marketplace add talent-summoner/agent-skills followed by /plugin install talent-summoner@talent-summoner. Do not use the plugin and the npm setup together in Claude Code, because that can create duplicate tools and skills. For a manually configured connection, add the HTTP endpoint to the agent's MCP settings and authenticate with the API key as a Bearer token.

To install only the companion skill, use npx skills add talent-summoner/agent-skills -g after configuring the MCP connection separately. Re-run setup to replace a key or update the skill. To disconnect, revoke the key and remove the MCP entry and skill from the agent.

Tools and capabilities

The Talent Summoner MCP server exposes capabilities for:

• Drafting and revising an ideal candidate profile before a search begins.
• Searching for candidates and refining search criteria.
• Finding more candidates in an existing sourcing session.
• Reviewing candidates and building a shortlist.
• Requesting work-email lookups.
• Preparing outreach drafts for shortlisted candidates.
• Listing the account's Talent Summoner sourcing sessions.

The companion skill helps the agent follow the sourcing process, but it does not replace the MCP connection. Setup installs both unless the skill is installed separately.

Limitations and notes

The service does not begin sourcing or use a Role during setup. Role unlocking requires confirmation from the user. Outreach is not sent solely because an agent prepares a draft; the user must review and confirm it on the Talent Summoner website.

If tools do not appear after installation, restart the agent and check its MCP connection or workspace approval. A manually configured connection, the npm setup, and the Claude Code plugin are alternative connection methods rather than configurations to combine. Talent Summoner provides separate settings for connected apps and API-key revocation, which can be used to disconnect access.