What is the main functional difference between Hirly and Remoet MCP?

Hirly is categorized under Workplace & Productivity and uses an install path we have not confirmed yet. Remoet MCP belongs to Workplace & Productivity and uses a remote HTTP/SSE transport. Pick Hirly for workplace & productivity work and Remoet MCP for workplace & productivity.

How do I install Hirly or Remoet MCP in Claude Desktop, Cursor, or Windsurf?

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Hirly has no confirmed install command yet — follow its own setup instructions.

Are Hirly and Remoet MCP free to use, or do they require API keys?

Hirly is listed as freemium — a free tier with paid plans. Auth: oauth 2.0. Remoet MCP is listed as freemium — a free tier with paid plans. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Can I run both Hirly and Remoet MCP at the same time in my AI client?

Yes. MCP clients support multiple servers: add hirly and remoet-labs-remoet-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Hirly has a quality signal of 48/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Remoet MCP has 60/100 (Good) with 1 views, 0 installs and 2 GitHub stars.

Hirly vs Remoet MCP — MCP Server Comparison

Hirly vs Remoet MCP — MCP Server Comparison | AllMCPs

Feature & specification comparison

Rows where the two servers differ are marked.

Spec	H Hirly	Remoet MCP
Category	Workplace & Productivity	Workplace & Productivity
Quality signal	48/100 · Fair	60/100 · Good
Install command	Not confirmed yet	Confirmed
Transport	—	Remote HTTP/SSE
Auth	OAuth 2.0	API key required
Pricing	Freemium	Freemium
Required env vars	None listed	`REMOET_API_KEY`
Verified owner	Community listing	Community listing
GitHub stars	0	2
Directory activity	0 views 0 installs 0 upvotes	1 views 0 installs 0 upvotes
Tools	9	24
Full listing	View Hirly	View Remoet MCP

Tools & capabilities

Hirly tools 9

get_matchesLists the next jobs hirly matched to your resume that you have not acted on yet, best first.
get_jobGives your assistant one job's full posting, how your resume meets its requirements, and the hiring contact when hirly can find one.
save_resumeSaves a resume your assistant tailored as a new version in your hirly account. Your main resume changes only if you ask.
record_applicationMarks a job as applied in hirly — after you confirm you sent it — with the resume version you used.
get_profileShows your plan, whether your profile is set up, and a short summary of your main resume.
get_pending_questionsLists the applications that are paused because the employer's form asked something only you can answer, with the questions.
answer_questionsSends the answers you give in the chat, so hirly can finish the application. Only if you allowed applying.
submit_applicationStarts hirly applying to one job for you, after you confirm that job in the chat. Only if you allowed applying.
get_application_statusSays where an application stands: queued, applying, waiting for your answers, applied, or stopped and why.

Remoet MCP tools 24

get_profileThe user's complete Remoet profile in one call: profile core (summary, links, location, avatar), workExperience, projects, and education (each section entry carries an id for update/delete) plus the current visibility setting. The ids it returns are the ones the save_* and delete_profile_item tools take. What the fields affect: the summary is the first thing companies read; the technologies arrays on work entries and projects feed job matching, so an empty array drops that entry out of matching; visibility NONE hides the user from every company's candidate list, STARRED shows them to the companies they have starred, ALL to every company.
update_profileUpdate the user's Remoet profile core and/or their visibility. Only provide the fields you want to change. Omitted fields are left as-is; pass null to clear a field. If the source data (CV, website, etc.) is missing a field, ask the user rather than guessing. Never copy placeholder text like "lorem ipsum". VISIBILITY: pass visibility to control who can see the profile in company candidate lists: NONE (hidden), STARRED (only companies the user has starred, the recommended two-way match), or ALL (every company). Explain the trade-off before changing it. SUMMARY WRITING GUIDE: the summary is the most important field, the first thing companies read. 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." Under 500 characters. Avoid generic fluff like "passionate developer". Be specific and quantifiable.
save_work_experienceAdd or update a work experience entry (upsert). Omit id to create a new entry (title and startDate are required); pass an id (from get_profile) to update an existing one, changing only the fields you send. Every description should cover WHAT was built, HOW (technologies), IMPACT (users served, performance gains, revenue, uptime), and SCOPE (team size, scale). Push for measurable outcomes ("Built React frontend" -> "...serving 50K users, 40% faster"). The technologies array feeds job matching. Saving without an id always creates a new entry. Saved entries appear on the user's public profile, so they should describe real experience. Ask the user to confirm vague dates or fill real gaps.
save_projectAdd or update a portfolio project (upsert). Omit id to create (title and shortDescription are required); pass an id (from get_profile) to update, changing only the fields you send. Projects are the #1 differentiator for junior/mid developers. Help the user recognize work they might not think of: side projects, open-source contributions, hackathon entries, internal tools, time-saving scripts, blogs, personal apps. Saving without an id always creates a new entry. Saved entries appear on the user's public profile, so they should describe real work.
save_educationAdd or update an education entry (upsert). Omit id to create (institution is required); pass an id (from get_profile) to update, changing only the fields you send. Ask about degrees, bootcamps, and notable certifications. Confirm approximate dates with the user rather than guessing; don't fabricate. Saving without an id always creates a new entry.
delete_profile_itemDelete a profile item: a work experience entry, a project, or an education entry (set type accordingly). Use this to clean up duplicates, placeholder/test entries, or clearly wrong data. Ids come from get_profile. Always confirm with the user before deleting anything that could be real.
search_listingsWorks without a Remoet account, except starred: true. Search companies on Remoet, or list the user's starred companies (starred: true). Returns a summary per result. Full detail (description, perks, URLs) is on get_listing, by slug. Job boards and aggregators are excluded; talent networks that post direct roles (e.g. Toptal) appear as companies. CRITICAL, star quality: only star companies whose tech stack OVERLAPS the user's skills (a JavaScript dev should not star a Go/Rust-only shop). Stars are the user's job-feed noise filter, so an irrelevant star pollutes their feed with jobs they can't use. Judge overlap by each result's matchedTechStack: the technologies from your techStack filter that the company actually uses, checked against its FULL stack (not the capped preview), so do NOT skip a company just because the visible preview omits the user's skills. An empty matchedTechStack means the result matched on text, not tags. techStackCount is the company's true tag total; the full stack unlocks on starring. techStack matches AT LEAST ONE filtered technology by default; set techStackMatch:"all" to require every one. starred: true limits results to the user's starred companies; combined with techStack it returns matchedTechStack per starred company, which shows any star with zero overlap. Example: search_listings({ searchQuery: "payments", techStack: ["TypeScript", "React"], experienceLevel: ["mid"] }).
get_listingWorks without a Remoet account. 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, perks, job count, and URLs. NOTE: the tech stack is a small preview unless the company is starred. Starring unlocks the full stack (techStackCount shows the true total, e.g. a 3-tag preview of 147). Pass checkTechStack with the user's technologies to verify overlap against the FULL stack. Matched ones come back in matchedTechStack and lead the preview, same contract as search_listings. The star budget is reported by get_account.
star_listingStar/save a company listing. Starring subscribes you to their job postings. Starred company jobs appear in get_starred_jobs. Starring also unlocks the company's FULL tech stack (unstarred listings only show a small preview). Starring is FREE. It does not consume budget. However, there is a limit on how many active stars you can have at once. Remaining star slots are reported by get_account. 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. A company returned by a techStack-filtered search_listings call confirms the technologies in its matchedTechStack field (the filter checks the full stack, including the part hidden from the preview), so judge overlap by matchedTechStack, not the visible preview.
unstar_listingRemove a star from a company listing. WARNING: Unstarring consumes from your unstar budget (per 30-day period), EXCEPT when the user is over their star cap (then trimming back to the limit is free). This prevents unlimited cycling of stars. The remaining unstar budget is reported by get_account. Only unstar if the company is truly not relevant. Do NOT mass-unstar to get a user under their cap unless they explicitly ask. If they are over cap, surface the choice and let them decide which to keep.
search_jobsWorks without a Remoet account. Search Remoet's PUBLIC job catalogue: every role on the open board at remoet.dev/jobs, across all companies, not just the ones the user has starred. No star is needed and none is consumed. Use this to answer "what is out there" for any technology, title or company; use get_starred_jobs instead for the user's own curated feed. Each result carries the role's public Remoet URL, which is a real page anyone can open, plus applyUrl (the employer's own posting, where an application actually happens) and companySlug (the same slug get_listing takes, for company detail). Roles that Remoet is not permitted to publish never appear here. Duplicate postings of one role at a company are collapsed into a single result, so totalCount is the number of distinct roles, not raw postings. duplicateCount is how many postings collapsed into it; boards usually duplicate a role per location, but nothing guarantees that, so do NOT report it as a number of locations. firstSeenAt is when Remoet first saw the role, not when the employer posted it, and lastVerifiedAt is the last time Remoet confirmed it was still open. Filters are searchQuery (title, Remoet summary and tech stack), techStack (ANY of the given technologies, or EVERY one under techStackMatch: "all", which is how you express a must-have stack), companySlug, location, remotePolicy, experienceLevel and salaryMin. A salaryMin floor drops every role Remoet holds no numeric salary for, which is roughly 45% of the board, so use it when salary is a hard requirement and leave it off otherwise. location matches the canonical places Remoet stores per role rather than the free-text location string, so a country also finds roles that name only one of its cities; searchQuery does NOT read location, so filter by place with location and not by typing the place into searchQuery. When a search returns nothing, the hint says which filter emptied it and how many roles dropping that one filter would return, so act on the hint rather than guessing at which filter to relax. Results are newest-first unless you ask otherwise: sortBy takes "newest" or "salary", with sortOrder asc or desc. Start broad and narrow: a single heavily filtered query misses good roles. Results can be bookmarked with save_job. Example: search_jobs({ searchQuery: "platform engineer", techStack: ["Go", "Kubernetes"], location: ["Berlin"], remotePolicy: ["remote"] }).
get_starred_jobsGet job postings from the user's starred companies. This is the user's own curated feed. If the user has no stars, this returns nothing. In that case, use search_jobs instead: it reads the public catalogue. Supports filtering by search query, location, tech stack, remote policy, experience level, and minimum salary. Results are paginated. Same-title postings from one company are grouped into a single row: postingCount and postingLocations show how many raw postings it represents and where (boards often post one role per location). Results can be bookmarked with save_job. A single filtered query can miss good roles; an unfiltered call returns the whole feed, paginated. The techStack filter uses OR logic: specifying ["React", "TypeScript", "Node.js"] returns jobs matching AT LEAST ONE of them (technologies are auto-normalized and matched across spelling variants), so filter by the technologies that genuinely matter and judge each job's fit from its own techStack field. Use searchQuery for role-based searches ("senior engineer", "frontend", "platform") and techStack for technology-based filtering. OVER-CAP WARNING: if the response includes a "starsOverCap" field, the user has more starred companies than the limit allows and the surplus is scheduled for PERMANENT deletion on the given date. Proactively tell the user (count + date) and let them choose which companies to unstar down to the limit. NEVER unstar companies on the user's behalf just to get under the limit unless they explicitly ask you to.
+12 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Hirly

No confirmed install command for Hirly yet — follow the setup steps linked from its listing page rather than a guessed package name.

Remoet MCP

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "remoet-labs-remoet-mcp": {
      "url": "https://api.remoet.dev/mcp"
    }
  }
}

Hirly vs Remoet MCP

Which MCP server should you choose?

H
Choose Hirly when

Choose Remoet MCP when

Feature & specification comparison

Tools & capabilities

Hirly tools 9

Remoet MCP tools 24

Ready-to-paste client configs

Hirly

Remoet MCP

Frequently asked questions

HChoose Hirly when

Choose Remoet MCP when

Hirly tools 9

Remoet MCP tools 24

Hirly

Remoet MCP

Frequently asked questions

What is the main functional difference between Hirly and Remoet MCP?

How do I install Hirly or Remoet MCP in Claude Desktop, Cursor, or Windsurf?

Are Hirly and Remoet MCP free to use, or do they require API keys?

Can I run both Hirly and Remoet MCP at the same time in my AI client?

Which MCP server has higher directory engagement and quality ratings?

Popular comparisons with Hirly

Popular comparisons with Remoet MCP

H
Choose Hirly when