Research the live CRM conversationally
Use Claude Code to request approved Chameleon-i searches without rebuilding every question as a manual filter, spreadsheet export or one-off script.
Model Context Protocol for recruitment
MCP recruitment software for consultants using Claude Code
Connect an agency's own Claude environment to approved, read-only Chameleon-i search, retrieval and reporting capabilities. Consultants can research live recruitment context and prepare evidence-led work while Chameleon-i remains the controlled system of record.
MCP is available by special request and is currently read-only. The exposed retrieval tools, permissions and operational boundaries are agreed for each agency.
Controlled connection
Claude Code ↔ Chameleon-i
Agency Claude environment
The consultant asks for recruitment context in natural language.
Agreed read-only MCP tools
Only approved search, retrieval and reporting capabilities are exposed.
Chameleon-i CRM + ATS
Candidate, client, vacancy and activity context stays governed by the system of record.
Natural-language access
Ask recruitment questions without exporting another spreadsheet.
Source-grounded output
Use approved live CRM context rather than disconnected AI memory.
No MCP write access
Consultants verify evidence and take action through normal controlled CRM workflows.
What MCP changes
Give Claude tools—not an uncontrolled copy of the database
The Model Context Protocol provides a standard way for an AI environment to discover and call approved tools. Chameleon-i's current MCP tools are read-only: Claude Code can request permitted context when the consultant needs it, while the CRM remains unchanged and stays the source of truth.
Working interface
Claude Code
The agency's chosen Claude environment receives the consultant's instruction and organises the returned context.
Controlled read-only bridge
Chameleon-i MCP
The agreed MCP server presents approved retrieval tools. It does not currently expose record changes or communication actions.
System of record
Recruitment CRM + ATS
Permissions, candidate and client records, vacancies, activities and reporting context remain inside Chameleon-i.
Benefits for recruitment consultants
Less time assembling context. More time applying recruitment judgement.
MCP is most useful when it removes repeatable research and preparation work without pretending that an AI model should make the consultant's decisions.
Prepare evidence-led candidate reviews
Retrieve relevant candidate, vacancy and shortlist context, then use Claude to organise the evidence into a useful first pass for consultant review.
Create repeatable desk reporting
Turn recurring questions about pipelines, records and recruitment activity into controlled workflows that can be reused without copying CRM data between tools.
Find gaps before a client meeting
Ask for the approved context behind a vacancy, client or talent pool so the consultant can identify missing information and prepare sharper follow-up questions.
Prototype consultant-specific tools
Technical teams can use Claude Code and the exposed MCP tools to explore agency-specific reporting or research workflows before agreeing any broader integration design.
Keep access scoped and accountable
MCP access is agreed by special request and is currently read-only. Claude can use approved retrieval tools, but it cannot create, update or delete CRM records or send communications.
Consultant workflows
Useful questions MCP can help turn into repeatable work
These examples describe controlled research and reporting patterns. The exact fields and tools available depend on the agency's agreed configuration.
01
Vacancy preparation
Example request
“Show the approved CRM context for this vacancy and highlight missing information before the consultant speaks to the client.”
Consultant outcome: A structured briefing that helps the consultant validate the role rather than beginning with a blank document.
02
Candidate and shortlist research
Example request
“Retrieve relevant records and summarise the evidence that should be reviewed against this vacancy.”
Consultant outcome: A recruiter-controlled first pass grounded in Chameleon-i data—not an unexplained decision made outside the CRM.
03
Talent-pool review
Example request
“Find approved records matching the agreed criteria and identify where contact details or recent context may need attention.”
Consultant outcome: A practical research queue for consultants to verify, prioritise and action through the normal recruitment workflow.
04
Management and client reporting
Example request
“Retrieve the permitted data for this reporting question and organise it into a concise, source-grounded summary.”
Consultant outcome: Faster reporting preparation while Chameleon-i remains the system of record and the consultant checks the final output.
Security and control
An MCP connection should have boundaries you can explain
Recruitment data can include personal information, commercial context and relationship history. The useful question is not simply whether Claude can connect, but which read-only tools it can use and for whom. Record changes and communications are not exposed through the current MCP connection.
Special request, agreed scope
Chameleon-i reviews the intended workflow, Claude environment and required read-only capabilities before an MCP connection is agreed.
Available by special request rather than enabled automatically
Only agreed Chameleon-i search, retrieval and reporting tools are exposed
Agency identity, permissions and access scope remain part of the design
The current MCP connection is read-only
It cannot create, update or delete records or send outbound communication
Consultants remain responsible for suitability, accuracy and final decisions
Questions about MCP recruitment software
Direct answers for agencies evaluating Claude connectivity
Chameleon-i also includes the recruitment-aware Miko AI Agent. MCP is the optional path for agencies that want their own Claude environment connected to agreed capabilities.
What is MCP recruitment software?
MCP recruitment software uses the Model Context Protocol to give an AI environment controlled access to approved recruitment-system tools and context. Chameleon-i's current MCP connection is read-only, allowing an agency's own Claude environment to use agreed search, retrieval and reporting capabilities without changing CRM data.
Can Chameleon-i connect with Claude Code?
Yes, by special request. An agreed MCP configuration can make approved Chameleon-i tools available in the agency's Claude environment, including Claude Code. The exact tools, users, permissions and audit requirements are defined as part of the integration scope.
How does MCP help recruitment consultants?
It can reduce the manual work involved in CRM research, vacancy preparation, candidate review and recurring reporting. Consultants can ask for approved recruitment context in natural language, use Claude to organise the result and then apply their own judgement before taking action.
Can Claude update candidate or client records automatically?
No. Chameleon-i's current MCP connection is read-only. It cannot create, update or delete candidate, client or vacancy records, and it cannot send communications. Consultants review the retrieved context and take any required action through the normal controlled Chameleon-i workflow.
Does MCP replace Chameleon-i's Miko AI Agent?
No. Miko provides the core recruitment-aware AI experience within Chameleon-i. MCP is an optional route for agencies that want their own Claude environment to work with approved Chameleon-i capabilities.
Is MCP access included for every Chameleon-i customer?
No. MCP is available by special request because the correct access model depends on the agency's use case, security requirements, Claude environment and the exact Chameleon-i capabilities being exposed.
Bring a consultant workflow—not just an AI wish list.
Show us the recruitment question, the Chameleon-i context it needs and the controls your agency expects. We can review whether an MCP connection to Claude Code is the right route and define a practical demonstration scope.