Remote MCP

Use the remote MCP endpoint when your AI client supports adding an MCP server by URL.

https://api.talentsourcer.ai/mcp

When your MCP client connects, TalentSourcer AI uses OAuth with PKCE. You will be redirected to the TalentSourcer AI app, where you can:

1. sign in
2. choose the workspace to connect
3. review requested scopes
4. approve or deny access

After approval, the MCP client receives an OAuth access token. The token is scoped to your user, the selected workspace, and the requested permissions.

Device flow

Some agents connect MCP servers through OAuth device flow instead of an automatic browser redirect. For those agents, send a prompt like this:

Connect the TalentSourcer AI MCP at https://api.talentsourcer.ai/mcp. It supports OAuth device flow. Discovery is available at https://api.talentsourcer.ai/.well-known/oauth-protected-resource. Run the device flow and send me the authorization link like: Authorize here: https://next.talentsourcer.ai/device?code=XXXX-XXXX. Then poll the token endpoint until authorization completes.

When the agent replies with an authorization link, open it, sign in, choose the workspace, and approve access.

Metadata endpoints

Most MCP clients discover these automatically:

https://api.talentsourcer.ai/.well-known/oauth-protected-resource
https://api.talentsourcer.ai/.well-known/oauth-authorization-server

Device-flow capable clients can also use:

https://api.talentsourcer.ai/oauth/device_authorization
https://next.talentsourcer.ai/device

MCP tools

The remote MCP server currently exposes tools for:

• projects
• searches and candidate import
• briefings and requirement updates
• talent pool insights
• candidate checks
• shortlists
• draft campaigns and campaign analytics
• outreach task review and manual task state updates

If your MCP client asks for scopes, use the smallest set required for your workflow. For broad recruiting-agent workflows, request:

projects:read projects:write briefings:read briefings:write candidates:read candidates:write shortlists:read shortlists:write campaigns:read campaigns:write outreach_tasks:read outreach_tasks:write inbox:read ats:read ats:write offline_access

Troubleshooting

If MCP authorization opens the wrong workspace, use the workspace selector on the authorization page before approving.

If a command returns a permission error, reconnect with the missing scope.