Spec-Driven IntelliMatch / iSuite MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SPECS_DIR | No | Override specs directory (default: ./specs) | |
| LOG_BASE_DIR | No | Root directory for log file access (if using file logs) | |
| ISUITE_UI_URL | No | iSuite web app URL (if using UI tools) | |
| ISUITE_API_URL | Yes | iSuite REST API base URL (required) | |
| ISUITE_DB_HOST | No | SQL Server host (if using DB tools) | |
| ISUITE_DB_NAME | No | Database name (if using DB tools) | |
| ISUITE_DB_USER | No | DB username (if using DB tools) | |
| ISUITE_UI_USER | No | Automation user (if using UI tools) | |
| ISUITE_PASSWORD | Yes | iSuite API password (required) | |
| ISUITE_USERNAME | Yes | iSuite API username (required) | |
| CONNECTIONS_FILE | No | Override connections config path (default: ./config/connections.yaml) | |
| ISUITE_DB_PASSWORD | No | DB password (if using DB tools) | |
| ISUITE_UI_PASSWORD | No | Automation password (if using UI tools) | |
| INTELLIMATCH_UI_URL | No | IntelliMatch web app URL (if using UI tools) | |
| INTELLIMATCH_API_URL | Yes | IntelliMatch REST API base URL (required) | |
| INTELLIMATCH_DB_HOST | No | PostgreSQL host (if using DB tools) | |
| INTELLIMATCH_DB_NAME | No | Database name (if using DB tools) | |
| INTELLIMATCH_DB_USER | No | DB username (if using DB tools) | |
| INTELLIMATCH_UI_USER | No | Automation user (if using UI tools) | |
| INTELLIMATCH_LOGS_URL | No | Log API base URL (if using log tools) | |
| INTELLIMATCH_API_TOKEN | Yes | Bearer token for IntelliMatch API (required) | |
| INTELLIMATCH_LOGS_TOKEN | No | Log API token (if using log tools) | |
| INTELLIMATCH_DB_PASSWORD | No | DB password (if using DB tools) | |
| INTELLIMATCH_UI_PASSWORD | No | Automation password (if using UI tools) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| im_search_candidatesB | Search IntelliMatch candidate profiles by name, skills, location, or status. Returns a list of matching candidates with profile summaries. |
| im_get_candidateA | Get full profile details for a specific IntelliMatch candidate including work history, skills, certifications, and match scores. |
| im_get_candidate_dbA | Query IntelliMatch database directly for candidate records. Use for bulk queries, custom filters, or when API limits are insufficient. |
| im_match_jobs_for_candidateB | Run IntelliMatch's AI matching engine to find the best-fit job openings for a given candidate. Returns ranked jobs with match scores and reasoning. |
| im_get_pipeline_statusA | Get the current recruitment pipeline status for a candidate — which stage they are in (applied, screening, interview, offer, placed, rejected). |
| im_search_jobsB | Search IntelliMatch job requisitions by title, department, location, or status. Returns open positions with requirement summaries. |
| im_get_jobA | Get full details of an IntelliMatch job requisition including requirements, compensation range, hiring manager, and open headcount. |
| im_match_candidates_for_jobA | Find the best-fit candidates for a specific job opening using IntelliMatch's AI matching engine. Returns ranked candidates with match scores. |
| im_get_match_scoreB | Calculate the match score between a specific candidate and job. Returns a score (0–1) with a breakdown of matching criteria. |
| im_get_open_jobs_dbB | Query IntelliMatch database for all open job requisitions with headcount and age. Useful for dashboards and bulk analysis. |
| im_get_matching_reportC | Generate an IntelliMatch summary report for a date range: total matches, average scores, placement rates, and top-performing job families. |
| im_get_placement_metricsA | Get placement metrics from the IntelliMatch database — total placements, time-to-fill, and breakdown by department for a given period. |
| im_get_application_logsA | Fetch recent IntelliMatch application logs for debugging — errors, matching engine events, or API call traces. |
| im_screenshot_dashboardA | Take a screenshot of the IntelliMatch dashboard or a specific page for visual verification and sharing. |
| is_search_claimsC | Search iSuite insurance claims by claim number, policy number, claimant name, or status. Returns claims with current status and amounts. |
| is_get_claimA | Get full claim details from iSuite including incident description, adjuster notes, documents, payments, and status history. |
| is_submit_claimB | Submit a new insurance claim in iSuite. Returns the assigned claim number and initial status. |
| is_get_claims_summary_dbC | Get a summary of iSuite claims from the SQL Server database — counts by status, total liability, and average settlement amounts for analysis. |
| is_add_claim_noteB | Add an adjuster note or status update to an existing iSuite claim. |
| is_search_policiesB | Search iSuite insurance policies by policyholder name, policy number, product type, or status. Returns matching policies with key details. |
| is_get_policyB | Get complete policy details from iSuite including coverage, premiums, beneficiaries, endorsements, and renewal dates. |
| is_get_policy_dbA | Query the iSuite SQL Server database directly for policy records. Use for bulk analysis, custom reporting, or complex filters. |
| is_renew_policyA | Initiate a policy renewal in iSuite. Returns the renewal quote and any changes to coverage or premium. |
| is_get_workflowA | Get the current status and history of an iSuite workflow instance — underwriting approvals, claim processing chains, or compliance reviews. |
| is_list_my_workflowsA | List iSuite workflows assigned to a user or team, filtered by status and workflow type. Shows pending actions and due dates. |
| is_advance_workflowB | Advance an iSuite workflow to the next step — approve, reject, or send back for revision. Provide a decision and optional comments. |
| is_get_workflow_logsA | Fetch workflow processing logs from iSuite for debugging stalled or failed workflow instances. |
| is_screenshot_workflowB | Take a screenshot of an iSuite workflow in the browser UI for visual review or documentation purposes. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/navin2031992/mcpspecdrivenintellimatch'
If you have feedback or need assistance with the MCP directory API, please join our Discord server