RChilli MCP Hub
Server Details
RChilli MCP Hub is a production-grade MCP server that exposes RChilli's full HR data intelligence platform as 17 AI-callable tools across 4 categories.
Built on 15+ years of HR data intelligence, it is trusted by ATS vendors, HR technology platforms, staffing agencies, and enterprise recruiting teams worldwide. Every tool is read-only and returns a consistent, structured JSON response — no raw exceptions, no inconsistent formats.
Key Features Zero boilerplate — One endpoint, one OAuth login, 17 tools ready to use OAuth 2.1 + PKCE — No API keys to copy or paste; fully automatic auth flow 200+ resume fields — Name, contact, skills, experience, education, certifications, and taxonomy-enriched job profiles ONet / ESCO taxonomy — 10,000+ curated skills and job profiles with canonical mappings Explainable matching — Field-level evidence for every candidate-to-job score Bias redaction — PII and bias field removal for fair-hiring workflows Document conversion — PDF, DOCX, RTF, HTML — convert in any direction Auto-injected credentials — userkey and subuserid injected from token; never pass them manually Consistent response envelope — Every tool returns { success, data, meta } with trace ID and latency
Use Cases Resume screening — Parse and structure resumes for AI-powered shortlisting Job description analysis — Extract required skills, experience range, and qualifications from any JD Candidate-to-job matching — One-to-one fit scoring with field-level evidence, no indexing required Talent pool search — Keyword search across your indexed resume database Skill gap analysis — Identify what a candidate is missing for a specific role Bias-free hiring — Redact names, photos, gender, and age before sharing with hiring managers Taxonomy enrichment — Look up and autocomplete 10,000+ standardized skills and job titles Document standardization — Convert and reformat candidate documents into consistent templates
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.6/5 across 17 of 17 tools scored.
Most tools have clearly distinct purposes (e.g., autocomplete vs. lookup, parse vs. extract). However, there is potential confusion between search_indexed_documents and find_matches_in_index (both involve indexed searches), and between convert_document_format and reformat_resume_with_template (both output formatted documents). A few tools like extract_contact_info and extract_named_entities could also be ambiguous to new users.
All tools follow a consistent verb_noun snake_case pattern (e.g., autocomplete_job_profile, parse_resume, redact_resume). Verbs are descriptive and nouns clearly indicate the resource or action. No mixing of conventions or cryptic abbreviations.
With 17 tools, the set covers a comprehensive range of HR/resume-related functionality (parsing, matching, taxonomy, formatting, redaction, geocoding) without being overly large or sparse. Each tool serves a specific and justifiable purpose.
The tool surface covers core HR workflows: parsing, matching, taxonomy lookup, and document transformation. However, it lacks an explicit tool for building or populating an index (required by find_matches_in_index and search_indexed_documents), and there are no tools for managing user accounts or bulk operations, which could cause dead ends for agents.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!