Since August 17, anyone with a browser could open remoet.dev/jobs and read every role on it without signing in. Anyone with an agent could not. Every tool on our MCP server asked for an API key, so the first thing your agent learned about Remoet was "go make an account", before it had shown you a single job.

That was backwards. We built Remoet for people who job hunt through an agent, made the catalogue public, and then left the door shut for exactly those people (a little embarrassing, in hindsight).

As of September 16 the door is open. Point an MCP client at our server and it can search the board straight away. No account, no key, no signup form in the middle of your conversation.

What works without an account

Two tools.

search_jobs searches every role on the public board, across every company on it. You can filter by keywords, tech stack, company, location, remote policy, seniority and a salary floor, and sort by newest or by salary.

get_listing reads one company: what it does, its perks, how many roles it has open, and a preview of its tech stack. You can hand it your own stack and it checks the overlap against the company's full stack, not just the preview.

Everything else on the server (your profile, your stars, the roles you keep on file, your feed) still needs an account, because that is your data and it has to belong to someone. The account is free. If your agent reaches for one of those tools anyway, the server answers in plain words: this one needs an account, here is where to get a key, and search_jobs and get_listing still work. We wanted the agent to get a way forward, not a dead end it has to explain to you.

Ask it something real

A few questions that work well:

• "Find senior Rust roles that are fully remote and publish a salary."

• "What is open at companies that use both Go and Kubernetes, in Germany or the Netherlands?"

• "Show me the newest junior frontend roles, then tell me what each company actually builds."

Every role that comes back carries its Remoet page, the link to the employer's own posting (that is where you apply), the salary band when the company published one, when we first saw the role and when we last confirmed it was still open. When one company posts the same role many times, you get it once.

When we ran the Rust question on September 17, the first result was a Senior Platform Engineer role at GitLab, fully remote, with a published band of $139,200 to $235,200. That role may well be gone by the time you read this, which is sort of the point of asking live.

A few things worth knowing, because they trip agents up:

• A country matches its cities. Ask for Germany and you also get roles that only say Berlin.

• A salary floor drops every role without a published number, and plenty of companies still do not publish one. If you care more about finding the role than filtering on pay, leave the floor off and read the bands yourself.

• A stack filter matches any of the technologies you give it by default. If you mean "must have all of these", say so, and a good agent will pass techStackMatch: "all".

Hooking it up

For most clients the address is https://api.remoet.dev/mcp, with no key and no auth header. We connected Hermes and Claude Code this way while writing this post. The other snippets are the same config shapes our docs use, minus the key.

Hermes Agent

hermes mcp add remoet --url https://api.remoet.dev/mcp

Hermes first asks whether the server requires authentication. Answer n. It then lists the tools and asks which ones to enable: pick select and keep search_jobs and get_listing, because the rest only answer once an account is connected (that was on Hermes 0.14). When you do want your account, run the same command again, answer y to overwrite the existing entry and y when it asks about authentication, then paste a free key. Hermes stores it for you.

OpenClaw

openclaw mcp set remoet '{"url":"https://api.remoet.dev/mcp","transport":"streamable-http"}'
openclaw mcp list

Honest note: we have not run this one on a clean OpenClaw install ourselves. It is the same config shape our OpenClaw skill uses, minus the key. If it misbehaves, tell us and we will fix the post.

Claude Code

claude mcp add --transport http remoet https://api.remoet.dev/mcp

Cursor

In ~/.cursor/mcp.json:

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

VS Code

In .vscode/mcp.json (the top level key really is servers here, not mcpServers):

{
  "servers": {
    "remoet": { "type": "http", "url": "https://api.remoet.dev/mcp" }
  }
}

Windsurf

In ~/.codeium/windsurf/mcp_config.json, where the field is called serverUrl:

{
  "mcpServers": {
    "remoet": { "serverUrl": "https://api.remoet.dev/mcp" }
  }
}

Codex

In ~/.codex/config.toml:

[mcp_servers.remoet]
url = "https://api.remoet.dev/mcp"

Anything else

A client that speaks MCP over Streamable HTTP should work the same way. claude.ai and Claude Desktop connectors are the exception: they go through a separate OAuth address, and the docs walk through that setup.

The limits, and why they exist

Searching without an account runs on tighter limits than a signed-in key: up to 20 results a page, ten pages deep, and a modest number of calls per minute and per day. That is plenty for one person asking questions about their next job. It is not much for someone trying to copy the whole board, and that is deliberate. We have had a crawler take the board down before, and we would rather not repeat it. If lots of people search at the same moment you may occasionally be asked to retry in a few seconds.

A free account raises the limits.

When you want more than search

Search answers "what is open right now". The account is for everything after that. Star the companies you would actually work for, and their new roles come to you in your feed and through your agent, instead of you asking again every week. Keep roles on file with a note about why you liked them. Build a profile your agent can read, so "find me something that fits" means something.

If you connect an agent we have not listed here, or one of these setups does not behave the way we said, come tell us in Discord. We read everything, and we are curious which agents people are actually job hunting with.