# Gighq MCP server

Source: https://glimind.com/server/mcp-registry%2Fai.gighq%2Fgighq
Registry id: `mcp-registry/ai.gighq/gighq`
Status: live (checked 2026-10-27T08:07:52.771Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 917
- Outages (90 days): 0

## Install

```json
{
  "mcpServers": {
    "gighq-mcp-server": {
      "type": "http",
      "url": "https://mcp.gighq.ai/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http gighq-mcp-server https://mcp.gighq.ai/mcp
```

## Tools (34)

- `add_career_entry`: Saves a new career journal entry to the user's GigHQ profile. Use this to document professional achievements, projects, skills acquired, or reflections tied to 
- `add_contact_interaction`: Logs a touchpoint with one of the user's job-search contacts — a call, a LinkedIn message, a coffee chat, a referral conversation, etc. The entry appears in the
- `add_job_application_note`: Adds a note to a job application's timeline. Use this to log any touchpoint or interaction — a call, a LinkedIn message, a referral conversation, a networking e
- `check_stale_applications`: Returns job applications that haven't had a status update in a configurable number of days, along with a suggested follow-up action for each. Useful for surfaci
- `create_job_application`: Creates a new job application entry in GigHQ, or reuses an existing active one for the same company+job if the backend finds one — check `alreadyExist` in the r
- `delete_career_entry`: Permanently deletes a career journal entry by UUID. This action cannot be undone — confirm with the user before calling. Use list_career_entries to find the UUI
- `delete_job_application_note`: Permanently deletes a note from a job application's timeline. This action cannot be undone — confirm with the user before calling. Use list_job_application_note
- `find_job_application`: Checks whether the user already has a saved job application for a SPECIFIC posting — call this before create_job_application to avoid creating a duplicate. Matc
- `generate_career_compass`: Runs GigHQ's CareerCompass AI pipeline against the user's resume data to generate 3 candidate professional objective statements, a positioning statement, catego
- `get_career_compass`: Retrieves the user's saved CareerCompass data: professional objectives, positioning statement, categorized skills (technical/soft/management/other), and target 
- `get_career_journal_prompts`: Returns a set of context-aware reflection questions to guide a career journaling session. Use this at the start of any journaling conversation to orient the dis
- `get_company_details`: Get detailed information about a company (applicants by status, Community Signal, H1B sponsorship status, employee count, website, etc.) using its UUID. The met
- `get_contact`: Returns full details for one of the user's job-search contacts: profile info, outreach status, linked job applications, and the complete interaction history (ca
- `get_job_application`: Fetches the full details of a single job application by its UUID — status history, correspondence dates, job description, and related metadata. Do NOT use this 
- `get_job_details`: Get detailed community metrics for a specific job listing (applicants by status, average days per status, Community Signal) using its UUID. The metrics window d
- `get_job_fit_evidence`: Retrieves a saved GigHQ job application, candidate profile data, and the most relevant Career Journal evidence for assessing role fit. Career evidence is ranked
- `get_recent_applications`: Retrieves a summary of the user's 10 most recent job applications, including status, company name, and correspondence dates. `totalCount` in the response reflec
- `list_career_entries`: Returns the user's career journal entries from GigHQ, newest first. Supports optional filtering by entry type and date range. Use this tool to: - Review what th
- `list_experiences`: Returns the user's work experience records with their integer IDs. Use this tool BEFORE calling `add_career_entry` or `update_career_entry` to find the correct 
- `list_job_application_notes`: Use this tool when the user asks about notes on a job application — "do I have any notes", "show me my notes", "what notes do I have", etc. Returns all user-aut
- `lookup_h1b_sponsorship`: Looks up a company by name and returns GigHQ's recorded H1B sponsorship and concurrent H1B flags. Returns unknown when a flag is unavailable. These results desc
- `prepare_for_interview`: Assembles everything needed to prepare for an interview on a saved GigHQ job application: the job and company context, the candidate's full profile, their Caree
- `recommend_target_roles`: Assembles the user's profile, experience, career journal evidence (with a broad competency rollup), and saved CareerCompass data (if any) for recommending role 
- `save_career_compass`: Persists CareerCompass data to the user's GigHQ profile. This REPLACES the full saved record — any array field you omit (technical_skills, soft_skills, manageme
- `search_companies`: Search for companies by name to retrieve their unique identifiers (UUIDs).
- `search_contacts`: Searches the user's job-search contacts in GigHQ — recruiters, hiring managers, referrals, and other people they are networking with. Use this tool to: - Find a
- `search_job_applications`: Search the user's job applications by company name, status, or both. Use this when the user asks about a specific company's application, wants to find a particu
- `toggle_job_application_interest`: Use this tool when the user says "not interested", "no longer interested", "withdraw interest", "I'm out", "remove from pipeline", or any equivalent phrase. Thi
- `update_career_entry`: Updates an existing career journal entry. Only the fields provided will be changed — all other fields remain as-is. Use this to refine descriptions, add missing
- `update_contact_status`: Updates a contact's outreach status in GigHQ. A status-change entry is automatically logged in the contact's interaction history. Status progression: not_contac
- `update_job_application`: Enriches or corrects an existing job application's saved posting details: source URL and/or job description. Use this when the user finds the JD later, wants to
- `update_job_application_note`: Updates the body or category of an existing job application note. Both body and category are required — the backend replaces the full note on update. If the use
- `update_job_application_status`: STOP — if the user says "not interested", "no longer interested", "withdraw interest", "remove from pipeline", or any equivalent: do NOT call this tool. Call to
- `weekly_job_search_summary`: Generates a weekly job search health summary. Aggregates up to 30 active applications and surfaces status distribution, conversion rates, longest-open applicati

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.