Skip to main content
Glama

Remoet MCP server

あなたのAIエージェントを、エージェント向けに作られた求人プラットフォーム Remoet に接続します。公開求人カタログを検索し、実際に使っている技術スタックでテック企業を見つけ、働きたい企業にスターを付けると、その新しい求人があなたのフィードに届きます。また、開発者プロフィールの管理もすべて会話を通じて行えます。

このリポジトリは、ローカル stdio MCP サーバー(Node + TypeScript)と、MCP クライアントやディレクトリレジストリが必要とするメタデータを提供します。ローカルサーバーは Remoet の全ツールカタログ(ライブサーバーからスナップショット)を公開し、あなたの Bearer キーを使ってホスト型 MCP の https://api.remoet.dev/mcp に呼び出しを転送します。ホスト型サーバーはクローズドソースであり、実行の真実の源(source of truth)であり続けます。

ほとんどのユーザーはホスト型サーバーに直接接続します(下記のクイックインストールを参照)。ローカルパッケージは、stdio を好むクライアントや、実行可能なローカルサーバーを必要とするビルド/スキャンシステム向けです。

機能

求人カタログは公開されています。search_jobs は、スターを付ける前に、remoet.dev/jobs のオープンボード上のすべての企業のすべての役職を読み取ります。

スターはアクセスではなく、配信に関するものです。Remoet は、各企業の技術スタックを、現在募集している役職から導き出します。自己申告の採用リストは古くなりがちですが、それに頼るのではなく、エージェントは今日実際に使われている技術で企業をマッチングできます。合う企業にスターを付けると、その新しい求人があなたのフィードに届き、企業のフルスタックが解放されます。Remoet はまた、あなたのプロフィール、保存した求人、応募、週次ダイジェストを MCP 経由でファイルに保持します。

Remoet は求職者にとって無料です。有料プランもクレジットカードもありません。すべてのアカウントに同じ制限が適用され、get_account で自分の状況を確認できます。

完全なツールカタログは tools.md を参照してください。

Related MCP server: Shortlist MCP Server

対応クライアント

Claude Code、Claude Desktop、Claude Web、Cursor、VS Code、Windsurf、Codex、および MCP 互換の任意のクライアント。また、OpenClaw(ClawHub 経由)や Hermes Agent に agentskills.io スキルとしてインストールできます。クイックインストール を参照してください。

認証

2つのトランスポート、同じツール:

  • https://api.remoet.dev/mcp は、Bearer ヘッダー(Authorization: Bearer <key>)として API キーを期待します。CLI や常時稼働のエージェントに最適です。

  • https://api.remoet.dev/mcp/oauth は、PKCE と動的クライアント登録を備えた OAuth 2.1 を実行します。Claude Web や Desktop のカスタムコネクタなどのブラウザクライアントに最適です。

remoet.dev/onboarding でキーを生成してください。同じキーが MCP と REST API の両方で機能します。

クイックインストール

Claude Code

claude mcp add --transport http --scope user remoet https://api.remoet.dev/mcp --header "Authorization: Bearer YOUR_KEY"

その後、Claude Code を再起動(終了して再起動)して、新しいサーバーのツールが新しいセッションで読み込まれるようにします。

Cursor, VS Code, Windsurf

クライアントの MCP 設定に追加します(.mcp.json の JSON がテンプレートとして機能します):

{
  "mcpServers": {
    "remoet": {
      "type": "http",
      "url": "https://api.remoet.dev/mcp",
      "headers": { "Authorization": "Bearer YOUR_KEY" }
    }
  }
}

Claude Web / Desktop (custom connector)

https://api.remoet.dev/mcp/oauth を指すカスタムコネクタを追加し、ブラウザでのサインインを完了します。貼り付ける API キーはありません。

Remoet は agentskills.io スキルとしても提供されており、Hermes と OpenClaw にワンコマンドでインストールできます。

Hermes

hermes skills tap add remoet-labs/agent-skills
hermes skills install remoet-labs/agent-skills/skills/remoet

OpenClaw

openclaw skills install remoet

最初に試すプロンプト

私は Rails、React、Postgres で働いています。Remoet でそのスタックを採用している企業はどれですか?

ローカルで実行(Node + Docker)

ローカルの stdio MCP サーバーを好む場合(またはビルド/スキャンシステムが必要とする場合)、同じパッケージを直接実行できます。

Node の場合:

npm install
npm run build
REMOET_API_KEY="<your-key>" node dist/index.js

サーバーは stdio 上で MCP を話します。REMOET_API_KEY に remoet.dev/onboarding の無料ティアのキーを設定してください。必要に応じて、REMOET_MCP_URL でアップストリームエンドポイントを上書きできます(デフォルトは https://api.remoet.dev/mcp)。

Docker の場合:

docker build -t remoet-mcp .
docker run --rm -i -e REMOET_API_KEY="<your-key>" remoet-mcp

コンテナのエントリポイントは stdio サーバーを実行します。MCP JSON-RPC フレームをコンテナにパイプします。ツール呼び出しは、あなたの Bearer キーでホスト型サーバーに転送されます。

公開されているツールカタログは data/tools.json にあり、ライブの tools/list から生成されます。ホスト型サーバーのツールサーフェスが変更されたら、いつでも更新してください:

REMOET_API_KEY="<your-key>" npm run snapshot:tools

スクリプトはスナップショットを書き換え、tools.md が同期されていないツールを報告します。

ライセンス

MIT。ラッパーはオープンソースです。それが指す Remoet バックエンドはホスト型サービスです。

Available Tools

48 tools
accept_offerAccept OfferA
Idempotent
Inspect

Accept a job offer. Only works when the application status is "offer_extended". Confirm with the user before accepting.

Inputs: applicationId (required).

add_application_noteAdd Application NoteAInspect

Add a private note to a job application. Notes are only visible to the user (not the company). Use this to help the user track thoughts, prep notes, follow-up reminders, or any context about the application. Max 1000 characters.

Inputs: applicationId (required), note (required).

apply_to_jobApply to JobAInspect

Apply to an internal job posting on behalf of the user. The job must be published and not expired. The user can only apply once per job — duplicate applications are rejected.

IMPORTANT: Before applying, confirm with the user that they want to apply. Review the job details (use get_starred_jobs or get_listing) and cross-reference against the user's profile. Flag any gaps between the job requirements and the user's skills — e.g. "This role asks for Go experience which isn't on your profile. Still want to apply?" This helps the user make informed decisions and avoids wasting applications. Do NOT apply to jobs without the user's explicit consent.

Only works for internal jobs (applicationType: "internal"). For external jobs, direct the user to the applicationUrl instead.

Inputs: jobId (required).

create_educationAdd EducationAInspect

Add an education entry to the user's profile. Before creating, always check existing education with get_education to avoid duplicates. If the source data is incomplete (e.g. missing dates, field of study, or institution URL), ask the user to fill in the gaps. Dates must be accurate — ask the user to confirm approximate dates if the source is vague. Do not fabricate or embellish information.

Inputs: institution (required), isCurrent (required), institutionUrl, studyLevel, +4 more.

create_linktreeCreate Link TreeAInspect

Create a link tree page — a shareable page with the user's links (social media, portfolio, GitHub, etc.). Link tree limits: Free 1, Pro 10, Max unlimited. The slug becomes the public URL. Slug rules: 5-20 characters, lowercase letters, numbers, and hyphens only, cannot start/end with a hyphen. Must be unique. Use the user's name or handle as a base for the slug. Pull links from the user's profile (get_profile) — githubUrl, linkedinUrl, twitterUrl, url, etc.

TIP: Suggest the user adds their link tree URL to their CV or job applications. Remoet tracks views and link clicks, so they can see if a recruiter has opened it.

Inputs: slug (required), title (required), description (required), links (required).

create_projectAdd ProjectAInspect

Add a project to the user's portfolio. Before creating, always check existing projects with get_projects to avoid duplicates. If the source data is incomplete (e.g. missing description, technologies, or dates), ask the user to fill in the gaps. Dates must be accurate — ask the user to confirm if unclear. Write clear, professional descriptions. Do not fabricate or embellish information.

PROJECT COACHING: Many users underestimate what counts as a project. Help them recognize work they might not think of: side projects, open-source contributions, hackathon entries, internal tools, scripts that saved time, blogs/tutorials, personal apps, browser extensions, Discord bots. Even small projects demonstrate initiative and practical skills. For junior/mid developers, projects are the #1 differentiator — two candidates with similar job histories are separated by their projects.

Inputs: title (required), shortDescription (required), technologies (required), isCurrent (required), +8 more.

create_work_experienceAdd Work ExperienceAInspect

Add a work experience entry to the user's profile. Before creating, always check existing entries with get_work_experience to avoid duplicates. If the source data is incomplete (e.g. missing dates, company name, or description), ask the user to fill in the gaps rather than guessing. Dates must be accurate — ask the user to confirm approximate dates if the source only says something like "2019" or "Summer 2020". Write clear, professional descriptions. Do not fabricate or embellish information.

DESCRIPTION QUALITY: Every job description should answer WHAT (built/designed/led what), HOW (which technologies, methodologies), IMPACT (users served, performance gains, revenue, uptime), and SCOPE (team size, user base). If the user gives a vague description like "Worked on the backend", ask follow-up questions: "What did you build specifically? What tech did you use? How many users or requests did it handle? What was the team size?" Push for measurable outcomes — numbers make descriptions 10x stronger.

TECHNOLOGIES: Always populate the technologies array — it feeds into job matching. If the description mentions technologies not in the array, ask to add them.

Inputs: title (required), companyName (required), companyUrl (required), startDate (required), +5 more.

delete_educationDelete EducationA
DestructiveIdempotent
Inspect

Remove an education entry from the user's profile. Use this to clean up duplicates, placeholder/test entries, or obviously incorrect data. Always confirm with the user before deleting entries that look like they could be real data.

Inputs: id (required).

delete_linktreeDelete Link TreeA
DestructiveIdempotent
Inspect

Delete a link tree page. Use get_linktrees to find the ID first. Confirm with the user before deleting.

Inputs: id (required).

delete_projectDelete ProjectA
DestructiveIdempotent
Inspect

Remove a project from the user's portfolio. Use this to clean up duplicates, placeholder/test entries, or obviously incorrect data. Always confirm with the user before deleting entries that look like they could be real data.

Inputs: id (required).

delete_work_experienceDelete Work ExperienceA
DestructiveIdempotent
Inspect

Remove a work experience entry from the user's profile. Use this to clean up duplicates, placeholder/test entries, or obviously incorrect data. Always confirm with the user before deleting entries that look like they could be real data.

Inputs: id (required).

get_applicationView ApplicationA
Read-only
Inspect

Get details of a specific job application by ID. Returns the application status, job info, company info, and timestamps.

Inputs: applicationId (required).

get_application_eventsView Application TimelineA
Read-only
Inspect

Get the timeline of events for a job application. Shows status changes, notes, messages sent, interview scheduling, and other milestones. Events are sorted chronologically (oldest first). Public events are visible to both parties; private events (like notes) are only visible to the user.

Inputs: applicationId (required).

get_application_messagesView Application MessagesA
Read-only
Inspect

Get the message thread for a job application. Shows all messages between the user and the company, sorted newest first. Paginated.

Inputs: applicationId (required), page, limit.

get_applicationsView ApplicationsA
Read-only
Inspect

Get the user's job applications. Returns a paginated list with status, job title, company name, and timestamps. Use this to help the user track their application pipeline. Filter by status to focus on active applications, pending offers, etc.

Inputs: status, page, limit.

get_appsBrowse AppsA
Read-only
Inspect

List approved apps built on the Remoet platform. These are community and official apps that extend Remoet's functionality. Each app has a repo URL for deployment and a demo URL to try it out. Use this to help users discover tools that complement their Remoet workflow — e.g. portfolio sites, CV generators, job trackers, etc. You can filter by category or tag.

Inputs: category, tag.

get_digestView DigestA
Read-only
Inspect

Get a specific digest by ID. Returns the full digest content — a markdown-formatted summary of jobs found from the user's starred companies during that period. Each job entry includes the title, application URL, salary, remote policy, experience level, and tech stack. Note: Free tier digests are 1 week behind the current scrape — the jobs shown may no longer be open. For real-time jobs, use get_starred_jobs instead.

Inputs: id (required).

get_digestsView DigestsA
Read-only
Inspect

Get the user's job digests — weekly email summaries of new jobs from their starred companies. Returns the 20 most recent digests. For weekly email summaries only. Always use get_starred_jobs for real-time job searching — digests are delayed (free tier is 1 week behind the current scrape) and less interactive. Only use this tool if the user specifically asks about their digests or email summaries.

Inputs: no named parameters.

get_educationView EducationA
Read-only
Inspect

Get the user's education history (each entry returns its ID for update/delete). Education matters most when a user has limited work history — for senior candidates it's a tiebreaker. Flag: empty education (ask about degrees, bootcamps, notable certifications, MOOCs), entries without dates, entries without field of study. Offer to fix each via create_education.

Inputs: no named parameters.

get_linktreeView Link TreeA
Read-only
Inspect

Get a specific link tree page by its public slug. Returns the page content plus engagement data (views, clicks per link) — useful if the user asks "has anyone looked at my link tree?". Use get_linktrees first if you need the slug.

Inputs: slug (required).

get_linktreesView Link TreesA
Read-only
Inspect

Get all the user's link tree pages (each returns its ID and slug). Link trees are shareable single-page URLs the user can put on a CV, email signature, or job application — Remoet tracks views and clicks per link, so recruiter engagement is measurable. If the user has none, suggest creating one via create_linktree pulling their social links from the profile.

Inputs: no named parameters.

get_listingView Company DetailsA
Read-only
Inspect

Get detailed information about a specific company listing by its slug. Use this to review a company before deciding whether to star it. Returns the company's full description, tech stack, perks, job count, and URLs. Pair with get_star_count to check budget before starring.

Inputs: slug (required).

get_profileView ProfileA
Read-only
Inspect

Get the user's full Remoet profile. IMPORTANT: Always call this first before making any changes.

PROFILE GAP ANALYSIS: After fetching, run a full evaluation and proactively surface findings ranked by impact. Offer to fix each issue on the spot. Be encouraging, not critical — "Your profile has a solid foundation, here are a few things that could make it stand out."

CHECK 1 — SUMMARY & DISCOVERABILITY (highest impact):

  • Summary empty or weak? Under 100 chars, no tech stack mentioned, no years of experience, or no differentiator = needs rewriting. See update_profile for guidance. This is the first thing companies read.

  • Call get_visibility. If NONE, suggest STARRED — creates a two-way match where starred companies can discover the user.

  • Check get_starred_listings. Zero stars = empty job feed. Help them find and star companies matching their tech stack.

  • Cross-reference starred companies' tech stacks against the user's skills. Flag mismatches that add noise.

CHECK 2 — PROJECTS (what makes them special?):

  • Zero projects = #1 gap for junior/mid developers. Projects differentiate candidates with similar job histories. Ask about side projects, open source, personal apps, hackathons, scripts, blogs.

  • Projects without URLs or descriptions are barely better than no projects.

CHECK 3 — WORK HISTORY (can they do this?):

  • Zero jobs = critical gap. Walk user through adding experience or importing from CV.

  • Jobs without descriptions = missed opportunity. Each role should explain what was built, what tech was used, and what impact it had.

  • Descriptions without measurable impact? Push for specifics: users served, performance gains, revenue impact, team size. "Built React frontend" → "Built React frontend serving 50K monthly users, reducing load time by 40%."

  • Technologies array empty on jobs with tech in the description? Ask to add them — they feed into job matching.

  • Remote experience not highlighted? If they've worked remotely, ensure isRemote: true — remote hiring managers look for proof.

CHECK 4 — BASICS (will they even look?):

  • Avatar missing? Profiles without photos get less engagement.

  • Location vague? "Europe" is too broad. Companies need timezone and jurisdiction. "Lund, Sweden" is specific.

  • GitHub/LinkedIn missing? Table stakes for developers.

CHECK 5 — EDUCATION:

  • Empty education? Ask about degrees, bootcamps, certifications, notable courses.

If the user shares a CV, resume, or website, populate their entire profile (update_profile, create_work_experience, create_project, create_education), then search and star matching companies, and finally surface relevant jobs — all in one go.

Inputs: no named parameters.

get_projectsView ProjectsA
Read-only
Inspect

Get the user's projects and portfolio items (each entry returns its ID for update/delete). For junior/mid developers, projects are the #1 differentiator — two candidates with similar job histories are separated by what they built. Flag: zero projects (massive gap, ask about side work, OSS, hackathons, scripts, blogs), projects without URLs, projects without technology arrays. Offer to fix each via update_project or create_project.

Inputs: no named parameters.

get_saved_jobsView Saved JobsA
Read-only
Inspect

Get the user's saved jobs list. This is the user's job search memory — shows all jobs they've bookmarked across sessions, with notes and job details. Includes both AI-extracted jobs and internal partner jobs (see jobType field). IMPORTANT: Always call this before get_starred_jobs when helping with job search — it shows the user's existing pipeline so you can avoid re-recommending jobs they've already saved or dismissed. Paginated, newest saves first. Each saved job includes isActive and deactivatedAt fields. If isActive is false, the job is no longer appearing on the company's careers page — this usually means it was filled or expired, but could also be a temporary scraper issue (there is a grace period before deactivation). If job is null, the listing was deleted entirely. Suggest the user check the company's careers page directly if a saved job they care about gets deactivated.

Inputs: page, pageSize.

get_star_countView Star BudgetA
Read-only
Inspect

Get your star and unstar budget status. Starring is free but capped at maxActiveStars. Unstarring consumes from a per-period unstar budget to prevent unlimited cycling. Returns: currentStars (active stars), maxActiveStars (cap for your plan), starSlotsRemaining (how many more you can star), unstarBudgetUsed (unstars this period), unstarBudgetLimit (max unstars per period, or "unlimited"), unstarBudgetRemaining (unstars left, or "unlimited"), resetsAt (when the unstar budget resets), and plan (your subscription tier). Help the user make every star count — choose companies carefully.

Inputs: no named parameters.

get_starred_jobsView Job FeedA
Read-only
Inspect

Get job postings from your starred companies. This is the user's main job feed — if the user has no stars, this returns nothing. Quality depends on starring the RIGHT companies (ones whose tech stack matches the user's skills). If results are empty or poor, check get_starred_listings and suggest better stars. Starring is free so they can star more companies to improve their feed. Supports filtering by search query, location, tech stack, remote policy, experience level, and minimum salary. Results are paginated. Use save_job to bookmark good matches so the user doesn't lose them.

SEARCH STRATEGY: For job recommendations, run multiple searches and merge results: first a broad search (no filters) to see what's available, then targeted searches by the user's top 1-2 technologies. This ensures comprehensive coverage — a single filtered query can miss good roles. The techStack filter uses AND logic — specifying ["React", "TypeScript", "Node.js"] only returns jobs matching ALL three, so start with 1-2 core technologies, not the user's entire stack. If results are sparse, drop filters one at a time. Use searchQuery for role-based searches ("senior engineer", "frontend", "platform") and techStack for technology-based filtering.

Inputs: searchQuery, locationQuery, techStack, remotePolicy, +6 more.

get_starred_listingsView Starred CompaniesA
Read-only
Inspect

Get the list of companies the user has already starred. Returns a summary per company — use get_listing with the slug for full details. Use this to audit their current stars — if any starred company's tech stack doesn't overlap with the user's skills, suggest unstarring it (but warn that unstarring consumes unstar budget).

STAR QUALITY AUDIT: Cross-reference the user's profile technologies against each starred company's tech stack. Flag companies with zero overlap — e.g. a React/Node developer starring a company that only uses Go and Rust. Suggest companies they should star but haven't — search for companies matching their tech stack and compare against current stars. A curated star list is the foundation of a useful job feed.

Inputs: no named parameters.

get_subscriptionView SubscriptionA
Read-only
Inspect

Get the user's current subscription plan, all plan limits, and today's usage. Call this when a limit is hit to show the user where they stand and what upgrading would unlock. Returns plan tier, star caps, unstar budget, daily request limits, job data delay status, link tree cap, and today's MCP/API request counts.

Inputs: no named parameters.

get_usageView UsageA
Read-only
Inspect

Get the user's current usage against every budget the platform enforces: active star count vs star cap, unstars used this month vs monthly unstar budget, MCP requests made today vs daily MCP cap, REST API requests made today vs daily REST cap. Each budget includes a "resetsAt" ISO timestamp so you can tell the user exactly when the counter clears.

Calling this tool is free: it does not count against the daily MCP cap or the API key's request count, so check eagerly. Call it when the user asks "how close am I to my limit?" or "when does X reset?", or before firing 3+ write tools in a row (star_listing, update_profile, apply_to_job, etc.) so you can pace yourself. A limit value of "unlimited" means no cap for that budget.

Inputs: no named parameters.

get_visibilityView VisibilityA
Read-only
Inspect

Get the user's current profile visibility setting. Three states: NONE (hidden — this is the default for new accounts), STARRED (visible only to starred companies — the recommended setting), ALL (visible to every company on Remoet). If the user is at NONE and has starred companies, flag it: they're cutting off a key benefit of the platform (being discovered by companies they already like). Offer to switch to STARRED via update_visibility.

Inputs: no named parameters.

get_work_experienceView Work ExperienceA
Read-only
Inspect

Get the user's work experience / job history (each entry returns its ID for update/delete). Use this to ground anything you say about the user's background. After fetching: flag duplicates, placeholder data, missing descriptions, missing technologies arrays, or missing measurable impact. Each weakness is something you can fix on the next turn — surface them ranked by impact and offer to fix.

Inputs: no named parameters.

reject_offerReject OfferA
DestructiveIdempotent
Inspect

Reject a job offer. Only works when the application status is "offer_extended". Confirm with the user before rejecting.

Inputs: applicationId (required).

save_jobSave JobAInspect

Save a job to the user's list for later. Supports both AI-extracted jobs (from get_starred_jobs) and internal partner jobs. This gives the agent memory across sessions — saved jobs persist so the user doesn't lose track of interesting roles. Optionally attach a note (e.g. "Great fit for React skills", "Follow up next week"). Each job can only be saved once.

Inputs: jobId (required), jobType, note.

search_listingsSearch CompaniesA
Read-only
Inspect

Search for companies on Remoet. Only companies are returned (not freelance platforms or job boards). Returns a summary for each company — use get_listing with the slug to see full details (description, perks, URLs).

CRITICAL: Only star companies whose tech stack OVERLAPS with the user's skills. A JavaScript developer should NOT star a company that only uses Go, Rust, or Java. Stars are the user's noise filter — irrelevant stars pollute their job feed with jobs they can't apply to. Every star must make sense for THIS user.

Best approach: 1) Read the user's profile to understand their tech stack and experience, 2) Search listings filtering by the user's actual technologies, 3) Review results and only star companies where the tech stack genuinely matches.

SEARCH LOGIC: Relevance scoring ranks results by: exact name match (+10), name starts with query (+5), name contains query (+2), and each tech stack match (+20 per matching technology). Text search also matches description and about fields. Technologies are auto-normalized (e.g. "ts" → "TypeScript", "react" → "React"). Combine searchQuery and techStack for best results.

If the user's interests aren't clear from their profile, ask them what kind of companies they're looking for.

Inputs: searchQuery, techStack, sortBy, page, +1 more.

send_application_messageSend Application MessageAInspect

Send a message to the company on a job application. Messages are visible to both the user and the company. Use this for follow-ups, questions about the role, or any communication with the hiring team. Max 1000 characters.

IMPORTANT: Do NOT write or draft messages for the user. Ask the user to write their own message — it should be in their voice, not yours. You can remind them to keep it concise and specific, but the words must be theirs. Once they give you the message text, confirm they're happy with it before sending.

Inputs: applicationId (required), content (required).

star_listingStar CompanyAInspect

Star/save a company listing. Starring subscribes you to their job postings — starred company jobs appear in get_starred_jobs. IMPORTANT: Only company-type listings can be starred. Starring is FREE — it does not consume budget. However, there is a limit on how many active stars you can have at once (based on your plan). Call get_star_count to check remaining star slots. CRITICAL: Only star companies where the user's tech stack genuinely overlaps with the company's tech stack. A React/Node developer should NOT star a company that only uses Go or Java. Irrelevant stars pollute the job feed with noise. Every star must be a deliberate, high-quality match.

Inputs: listingId (required).

unsave_jobRemove Saved JobA
DestructiveIdempotent
Inspect

Remove a job from the user's saved list. Use get_saved_jobs first to find the saved job ID. Confirm with the user before removing.

Inputs: savedJobId (required).

unstar_listingUnstar CompanyA
DestructiveIdempotent
Inspect

Remove a star from a company listing. WARNING: Unstarring consumes from your unstar budget (per billing period). This prevents unlimited cycling of stars. Call get_star_count first to check your remaining unstar budget. Only unstar if the company is truly not relevant.

Inputs: listingId (required).

update_educationUpdate EducationA
Idempotent
Inspect

Update an existing education entry. Only provide the fields you want to change — omitted fields are left as-is. Use get_education first to find the ID. Prefer this over delete + recreate — it preserves the entry ID.

Inputs: id (required), institution, institutionUrl, studyLevel, +5 more.

update_profileUpdate ProfileA
Idempotent
Inspect

Update the user's Remoet profile. Only provide the fields you want to change — omitted fields are left as-is. Pass null to clear a field. Always read the current profile first with get_profile. If the source data (CV, website, etc.) is missing information for a field, ask the user rather than guessing or leaving it blank. Write professional, clean descriptions — never copy placeholder text like "lorem ipsum".

SUMMARY WRITING GUIDE: The summary is the most important field — it's the first thing companies read. A strong summary follows this pattern: [Role] with [X years] experience in [core tech stack]. [One differentiator or achievement]. Example: "Senior Full-Stack Developer with 8 years of experience in React, Node.js, and AWS. Built and scaled a SaaS platform serving 200K users." Keep it under 500 characters — enough for a second differentiator sentence if needed. Avoid generic fluff like "passionate developer" or "team player" — be specific and quantifiable.

Inputs: slug, email, name, avatarUrl, +9 more.

update_projectUpdate ProjectA
Idempotent
Inspect

Update an existing project. Only provide the fields you want to change — omitted fields are left as-is. Use get_projects first to find the ID. Prefer this over delete + recreate — it preserves the entry ID.

Inputs: id (required), title, shortDescription, description, +9 more.

update_saved_job_noteUpdate Saved Job NoteA
Idempotent
Inspect

Update the note on a saved job. Use this to add context, track application status, or record follow-up reminders. Pass null to clear the note.

Inputs: savedJobId (required), note (required).

update_visibilityUpdate VisibilityA
Idempotent
Inspect

Update who can see the user's profile in company candidate lists. There are 3 levels:

  • NONE — Profile is hidden from all companies. Maximum privacy.

  • STARRED — Profile is visible ONLY to companies the user has starred. This is the recommended setting and the default — it means companies you've chosen to follow can discover you as a candidate, but no one else can.

  • ALL — Profile is visible to every company on Remoet. Maximum exposure, but less privacy.

Always explain the trade-offs to the user before changing this. STARRED is the sweet spot for most users — it creates a two-way match (you follow them, they can find you).

Inputs: visibility (required).

update_work_experienceUpdate Work ExperienceA
Idempotent
Inspect

Update an existing work experience entry. Only provide the fields you want to change — omitted fields are left as-is. Use get_work_experience first to find the ID. Prefer this over delete + recreate — it preserves the entry ID.

Inputs: id (required), title, companyName, companyUrl, +6 more.

withdraw_applicationWithdraw ApplicationA
DestructiveIdempotent
Inspect

Withdraw a job application. This is irreversible for applications that have been accepted or rejected. Confirm with the user before withdrawing.

Inputs: applicationId (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 48 tools

    Disambiguation5/5

    Each tool targets a distinct action and entity. For example, create/update/delete operations for education, work experience, and projects are clearly separated. Application lifecycle tools (apply, withdraw, accept, reject) have distinct purposes. Even close pairs like get_digest vs get_starred_jobs are clearly differentiated by descriptions (one-week-old summaries vs real-time).

    Naming Consistency5/5

    All tools follow a consistent verb_noun snake_case pattern (e.g., create_work_experience, get_starred_jobs, accept_offer). No mixing of camelCase or other conventions. The naming is predictable and systematic, making it easy for an agent to infer functionality.

    Tool Count2/5

    With 48 tools, the surface is quite large for a single server. While many tools are necessary for full CRUD coverage across multiple entities, the count exceeds the typical well-scoped range (3-15) and even the 'heavy' range (16-25). Some tools could be consolidated (e.g., get_digest and get_digests). The number risks overwhelming an agent.

    Completeness4/5

    The tool set covers profile management (education, work, projects, links), job applications, job search and saving, company interactions, and account/subscription management. Minor gaps exist: no direct CV/resume upload tool, no user account deletion, and limited messaging. However, core workflows are well-supported, and agents can accomplish most tasks without workarounds.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      JobPilot is a next-generation career assistant powered by AI Agents and the Model Context Protocol (MCP). It acts as your personal recruiter, tirelessly searching for jobs on platforms like LinkedIn, optimizing your resume for specific job descriptions (JD), and even automating the application process. Designed for the age of AI, JobPilot exposes a full MCP server, allowing you to connect it with
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables users to search for jobs, prefill applications using AI, and automate submissions across major platforms like Lever and Ashby directly from Claude or Cursor. It provides a full suite of tools for managing job queues, profile data, and resumes within a chat interface.
      37
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to interact with email accounts via the Himalaya CLI, supporting features like message reading, folder management, and controlled email sending. It prioritizes security with graduated permission modes and the exclusion of destructive operations like permanent deletion.
      10
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Lets AI agents search, filter, and apply to salary-transparent tech jobs across nine job boards in eight countries, filtering by pay, remote work, tech stack, and location while tracking applications to avoid duplicates. It returns JSON-first results so an agent can drive job discovery and application end-to-end from the terminal or chat.
      -