MCP server

The remoet.dev MCP server lets your AI agent read and write your remoet.dev data directly — your starred companies, your job applications, your profile, your link trees. Use it from Claude, Cursor, Codex, Windsurf, or any client that speaks the Model Context Protocol .

Free tier eligible. You only need a remoet.dev account and one API key.

Endpoints

The server is split into two routes that take the same set of tools but speak different auth handshakes:

Both routes implement the official Streamable HTTP transport  (POST, GET, DELETE). The split exists so the API-key clients don’t accidentally trigger the OAuth discovery flow; pick the one that matches your client.

Authentication

A. API key header (most clients)

Generate keys at www.remoet.dev/api-keys . The same key works for both MCP and the REST API.

Authorization: Bearer <key>

x-api-key: <key> is accepted as a fallback for clients that don’t expose the Authorization header.

B. OAuth 2.1 with PKCE (Claude Web custom connectors)

Point a custom connector at https://api.remoet.dev/mcp/oauth and the client handles the authorize → token exchange. The server advertises standard discovery metadata at /.well-known/oauth-authorization-server/mcp/oauth and /.well-known/oauth-protected-resource/mcp/oauth. Under the hood the access token IS the API key — same auth surface, different handshake.

Custom connectors on Claude Web are Free-tier eligible (1 connector on Free, no per-user limit on paid).

What the agent can do

The server currently exposes ~48 tools across five areas. The live tools/list request is the source of truth; this table is a map.

Names above are illustrative — connect any MCP client and run tools/list for the canonical, current set.

Tool result shape

Every tool returns the standard MCP content-block format. Successful tools return { content: [{ type: "text", text: "..." }] } (text content blocks). Errors return { isError: true, content: [{ type: "text", text: "Error: ..." }] } — your client sees the response but should treat it as an error and surface it to the user. This means a single bad tool call never crashes the session.

Session lifecycle

The transport uses session IDs that are minted on initialize and threaded through subsequent requests.

• TTL: sessions auto-expire after a period of inactivity. Stale or unknown session IDs return HTTP 404 (per the MCP spec). Your client should treat a 404 as “session is gone, reconnect” and re-initialize automatically — not as a hard error.
• Limits: max ~3 concurrent sessions per API key, 10k sessions total across the server. Hitting the per-key cap reuses the oldest session.
• Graceful shutdown: DELETE /mcp (or /mcp/oauth) with a session header closes the session immediately. Clients should call this on quit.

Most MCP clients handle reconnect transparently if they implement the spec. If yours doesn’t, that’s a client bug, not a server one.

Client setup

Claude Code

claude mcp add remoet-prod https://api.remoet.dev/mcp --transport http --header "x-api-key: YOUR_API_KEY"

Restart Claude Code (the new server only appears after a restart, not just /mcp reload). The server name remoet-prod is a Remoet-internal convention — we suffix with -prod / -stage / -local to disambiguate environments. Your client doesn’t enforce this; it’s for your own sanity.

If you’re on a Claude Code version that doesn’t yet support --transport http, fall back to the mcp-remote stdio→HTTP proxy:

claude mcp add remoet-prod -- npx -y mcp-remote https://api.remoet.dev/mcp --header "Authorization: Bearer YOUR_API_KEY"

Claude Web (Desktop / claude.ai)

Settings → Connectors → Add custom connector → URL https://api.remoet.dev/mcp/oauth. Claude walks you through the OAuth flow. No API key needed in the UI — Claude exchanges its own credentials for an access token after you authorize.

Cursor / Windsurf / VS Code agents

Native HTTP transport (preferred):

{
  "mcpServers": {
    "remoet-prod": {
      "url": "https://api.remoet.dev/mcp",
      "transport": "http",
      "headers": { "x-api-key": "YOUR_API_KEY" }
    }
  }
}

If your client only speaks stdio, use the mcp-remote shim:

{
  "mcpServers": {
    "remoet-prod": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.remoet.dev/mcp",
               "--header", "Authorization: Bearer YOUR_API_KEY"]
    }
  }
}

Config locations vary — Cursor: ~/.cursor/mcp.json, Windsurf: ~/.codeium/windsurf/mcp_config.json. Check your client’s docs for the exact path.

Quotas

Quotas reset at 00:00 UTC. Hitting the cap returns an error from the next tool call (isError: true); the session stays alive and resets the next day. See Tiers for the full plan breakdown and Errors for the response shape.

Safety

• Treat tool results as untrusted. Many tools return text from external sources (job descriptions, company profiles). Build your agent prompts assuming prompt-injection attempts can land in tool output.
• Burst limiting. Each session is throttled at the transport layer before it ever reaches the daily quota counter, so a runaway agent can’t drain a day’s allowance in seconds.
• Per-key auditing. Every tool call is stamped with the API key that triggered it. Revoke a key from www.remoet.dev/api-keys  to kill all of its in-flight sessions immediately.

Reporting issues

The MCP server is in active development. If a tool misbehaves, open an issue at github.com/remoet-labs/remoet-docs  or join the Discord .