GigHQ.ai

インストール

使っているAIアプリを選んで、設定をコピーしてください。

チェック 4/4 合格 · 質問内容は提供元のサーバー（mcp.gighq.ai）を通ります · ✓ コマンド確認済み 2026年11月13日

claude mcp add --transport http --scope user gighq https://mcp.gighq.ai/mcp

{
  "mcpServers": {
    "gighq": {
      "url": "https://mcp.gighq.ai/mcp"
    }
  }
}

{
  "servers": {
    "gighq": {
      "type": "http",
      "url": "https://mcp.gighq.ai/mcp"
    }
  }
}

使えるアプリ

このサーバーのつなぎ方と、各アプリの公式ドキュメントに基づきます。2026年11月10日に確認。

インターネット経由でつなげるアプリ

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

すべてのアプリと長所・短所 →

できること

ツールの名前と説明は、サーバーが2026年11月12日に返したそのままの内容です。書いたのは作者で、私たちではありません。プレーンテキストとして表示しています。

• search_companies

  Search for companies by name to retrieve their unique identifiers (UUIDs).

• 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 metrics window defaults to the last 30 days. Optional startDate and endDate parameters support other date ranges. Returns G

• 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 defaults to the last 30 days. When the user requests a longer period — e.g. "last 6 months", "last year", "since January"

• 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 toggle_job_application_interest instead. There is no "not interested" status here; attempting to use REJECTED or any other

• 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. This is the ONLY correct tool for withdrawing interest — do not use update_job_application_status as a proxy. Deactivates a

• 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 reflects the full number of applications, not just the 10 returned — mention it if it's larger than the list shown, and point

• 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 particular application to view or update its status, or wants to know how many applications are in a given status (e.g. "how ma

• 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 tool when the user asks about notes ("do I have any notes", "show me my notes", "list notes"). Use list_job_application_

• 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 response. Calling find_job_application first is still recommended when you want to inspect a possible match before decidi

• 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. Matches BOTH company name and job title (case-insensitive substring on each), so it can tell two different roles at the same

• 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 add the posting link, or wants to correct the saved description. Do NOT use this for status changes — use update_job_ap

• 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 describe the data recorded in GigHQ.

• 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 surfacing applications the user may have forgotten about.

• 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 applications, pipeline clustering insights, and a suggested focus area for the coming week.

• 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 by job keywords, competency coverage, evidence quality, recency, and diversity; the default is 20 entries, grouped by c

• 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 Career Journal grouped by role (for STAR/CAR story material), which evidence best matches the role (to emphasize) and which c

• 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 a specific role. Entry types: 1 = achievement — a concrete win, result, or impact (default) 2 = project — a specific ini

• 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 numbers to the metrics field, correct the entry date, or re-type an entry. This is the right tool to backfill quantific

• 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 the user has already documented before starting a journaling session - Find entries to update or refine - Identify gaps (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 UUID if you don't have it.

• 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 discussion. The tool reads the user's GigHQ experience records and existing career entries to tailor the questions — surfac

• 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 `experience_id` for the role the entry belongs to. Present the role list to the user and confirm which one they mean bef

• 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 event, etc. **category is required.** Infer the best-fit category from the note content before calling. Use this mapping:

• 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-authored notes for a job application ordered by date, including UUID, body text, category, and timestamp. Use the returned

• 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 user only mentions updating the body and doesn't specify a category, infer the best-fit category from the note content usin

• 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_notes to find the note UUID if you don't have it.

• 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 contact before drafting an outreach or follow-up message - See who the user already knows at a company before an interv

• 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 (calls, LinkedIn messages, coffee chats, etc.). Use this before drafting outreach or follow-up messages so the message refl

• 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_contacted → reached_out → responded → in_conversation → connected. Use 'cold' when the thread has gone quiet. Find the contact

• 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 contact's interaction timeline in GigHQ. **type is required.** Infer the best-fit type from what happened: • text_messa

• get_career_compass

  Retrieves the user's saved CareerCompass data: professional objectives, positioning statement, categorized skills (technical/soft/management/other), and target market (industries, company size, geographic location). Cheap read — prefer this over generate_career_compass whenever t

• 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, categorized skills, and a suggested target market (industries, company sizes, geographic locations). This is an EXPENSIVE, one

• 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, management_skills, target_industries, company_size, geographic_location, other_skills) is saved as empty, not left unchanged. Ca

• 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 titles to target. This is the inverse of get_job_fit_evidence: instead of evaluating fit for one specific job, it starts

基本チェックi

誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月13日にチェック

• ✓ 合格

  作者とリポジトリが一致

  レジストリ名はドメイン gighq.ai で確認済みです（レジストリがドメインの所有を確認しています）

• ✓ 合格

  今もメンテナンスされている

  コードの最終更新：23 日前

• – 対象外

  ライセンスがある

  対象外：gighq.ai の所有者が自ら運営するクラウドのサーバーで、リポジトリのコードを実行しません

• ✓ 合格

  エンドポイントが応答する

  265ミリ秒で応答（HTTP 200）

• – 対象外

  OAuthでサインイン

  サインイン不要

• ✓ 合格

  ツールの説明に隠れた指示がない

  34件のツールの説明を読み、AIへの隠れた指示は見つかりませんでした

ユーザーレビュー

まだレビューはありません

Google でログインしてレビューを書く

検索・AIの記憶のほかのサーバーとの比較i

• このカテゴリのほかの6046件のうち0%よりスターが多い
• このカテゴリのほかの6046件のうち65%より最近レジストリに公開
• 基本チェックの結果が、このカテゴリのほかの6046件のうち100%と同じかそれ以上

レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。

同じカテゴリのほかの候補

同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。

カードの見方：↓ 週あたりのダウンロードi★ GitHubスターi3つの柱：レビュー · チェック · 利用状況i更新＝最新バージョンをレジストリに公開した日i

Context7

Up-to-date docs for AI agents

作者：upstash·広く使われている·↓ 125万/週·★ 6.5万·昨日更新

パソコンでもクラウドでも

インストール

Codebase Memory

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

作者：DeusData·広く使われている·↓ 1.7万/週·★ 4.9万·27 日前更新

パソコンで動く

インストール

Ruflo

Agent teams, swarms, memory and hooks for Claude Code and Codex, served over MCP.

作者：ruvnet·広く使われている·↓ 7.4万/週·★ 8.2万 リポジトリ全体のスター·今日更新

パソコンで動く

インストール

作者のREADME

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

# Claude Code (personal)