Remoote Remote Jobs MCP
This is the public metadata and docs repository for Remoote Remote Jobs MCP.
- Website and docs: https://remoote.app/agents
- MCP endpoint: https://api.remoote.app/remoote/agents/mcp
- Token setup: https://remoote.app/agents/connect
Remoote MCP gives agents a structured way to search current remote jobs, read job details, compare salary stats, show popular roles, create job alerts, and request user-confirmed apply redirects. It is meant for agent builders who need job data without scraping pages or exposing raw employer application links.
Tools
| Tool | Access | What it does |
|---|---|---|
search_jobs | Public or token | Searches active Remoote jobs by query, skills, location filters, seniority, employment type, and salary visibility. |
get_job | Public or token | Returns public details for one active job, including salary fields, location rules, skills, excerpts, and the Remoote job URL. |
get_salary_stats | Public or token | Returns salary stats for matching jobs when enough normalized compensation data is available. |
get_top_jobs | Public or token | Returns a capped list of currently popular remote jobs. |
create_apply_intent | Token required | Creates a Remoote apply redirect for an authenticated user after the agent asks for confirmation. |
create_alert | Token required | Creates a daily or weekly Remoote job alert for the authenticated user. |
Public vs. token-authenticated behavior
Public calls are available without a token for discovery and read-only job research. They are capped and return public Remoote fields, canonical Remoote URLs, and safe next actions.
Token-authenticated calls use a user-created bearer token. Use them only when the agent needs account-tied workflows such as alerts or apply intents. Create or revoke a token at https://remoote.app/agents/connect, then pass it as:
Authorization: Bearer rma_...
Only grant the scopes your workflow needs.
Apply safety
Public responses do not include raw employer apply URLs. They point users back to Remoote job pages.
create_apply_intent also returns a Remoote redirect, not a raw employer URL. The agent should ask the user to confirm before opening it, because opening the redirect may count as an application redirect or entitlement check.
Quick curl examples
All examples call the remote MCP endpoint directly over JSON-RPC.
List tools
curl -sS \
-H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}' \
https://api.remoote.app/remoote/agents/mcp
Expected result: tools includes search_jobs, get_job, get_salary_stats, get_top_jobs, create_apply_intent, and create_alert.
Search public jobs
curl -sS \
-H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"search_jobs","arguments":{"query":"python","limit":3,"salary_required":true}}}' \
https://api.remoote.app/remoote/agents/mcp
Expected result: structuredContent.status is ok and each job links back to Remoote instead of exposing a raw employer apply URL.
Create an alert with a token
export REMOOTE_AGENT_TOKEN='rma_...'
curl -sS \
-H 'content-type: application/json' \
-H "Authorization: Bearer $REMOOTE_AGENT_TOKEN" \
-d '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"create_alert","arguments":{"name":"Python remote jobs","criteria":{"query":"python","salary_required":true},"frequency":"daily","limit":10}}}' \
https://api.remoote.app/remoote/agents/mcp
Use a placeholder like rma_... in examples. Do not put real tokens in docs, logs, or prompts.
More examples
Registry metadata
server.json is prepared for MCP directories and registries. The repository URL points to the intended future public GitHub location: https://github.com/asmisha/remoote-mcp.