Add Kempian to your AI agent
Kempian runs a remote MCP server. Connect Claude or any MCP client that supports remote servers with OAuth, and your agent can work with your own Kempian workspace.
Connector address
https://connector.kempian.ai/mcp
Your workspace shows the same address, with a copy button, in Kempian under the Claude connection page.
What your agent can do
The connector offers five tools and nothing else.
search_candidates
Access: read, write or full · 3 credits
Search the talent pool for candidates whose evidence matches a job. Returns skills, experience and contact details. It returns no match score and no numeric rank, and every record is flagged for human review.
create_requisition
Access: write or full · 1 credit
Open a job order in Kempian from a title, with optional client, location, required skills, salary range and headcount. Returns the requisition ID used by the other tools.
get_matches
Access: read, write or full · 1 credit
Retrieve the matched candidates for a requisition. An optional minimum can set people aside, and the response says how many were set aside.
trigger_outreach
Access: read, write or full · 0 credits
Returns the link to Kempian’s outreach board for a set of candidates. It does not queue or send anything. A recruiter stages, reviews and approves outreach inside Kempian.
get_pool_stats
Access: read, write or full · 0 credits
Talent pool statistics: total candidates indexed, the domain breakdown and availability signals.
Credits are metered per workspace against your plan.
Set up in Claude
- 1
In Kempian, sign in with a role that can manage API access and open the Claude connection page. Copy your connector address.
- 2
In Claude, open Settings, then Connectors, then Add custom connector.
- 3
Paste the address and continue.
- 4
Claude sends you back to Kempian to sign in and approve the connection. Choose the access level you want to grant: read, write or full.
- 5
Back in Claude, enable the Kempian tools in a chat. You can disconnect at any time from the same page in Kempian, and the page lists what each connection did.
Set up in another MCP client
Any client that supports remote MCP servers over Streamable HTTP with OAuth can connect.
- Server URL
- https://connector.kempian.ai/mcp
- Transport
- Streamable HTTP, JSON-RPC 2.0, one POST endpoint
- Authorization
- OAuth 2.1, authorization code with PKCE (S256)
- Client registration
- Dynamic client registration (RFC 7591) at /register
- Discovery
- /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server on connector.kempian.ai
- Scopes
- read, write, full
A request without a token gets a 401 with a WWW-Authenticate header that points to the discovery document, so a compliant client starts the sign-in on its own. The consent step happens in your browser in Kempian. Clients that cannot run an OAuth sign-in against a remote server cannot connect to this server.
Who can connect, and how
- The person who connects signs in to Kempian and approves access for their own workspace. The token is tied to that workspace, so the agent works with that workspace’s records and what it is allowed to see there.
- Connecting and disconnecting needs a role with permission to manage API access. Each connection and each tool call is recorded in your workspace.
- Direct REST callers can use an API key instead of OAuth, sent in an X-Kempian-Key header. API access is on the Scale and Enterprise plans. Contact sales for the integration guide.
Humans stay in the loop
The connector never sends outreach. Candidates are shown on their evidence with no score, and the recruiter decides. Your agent can prepare the work, and a person approves anything that reaches a candidate.
Need help connecting?
Tell us which client you use and we will confirm it works with your workspace.
Talk to us