For devs with bots

Let your job agent do the sifting.

Plug Claude, Cursor or your own agent into Full Stack Jobbies. It searches rated full stack jobs that match your stack, salary floor and where you can work, and it can vet any listing you throw at it. Free, read-only, no key.

Your agent finds and vets. Applying still happens on the company's own page, and a good agent asks you before it sends anything.

1. MCP server

One URL for any MCP client: https://fullstackjobbies.com/mcp. Two tools: search_jobs and rate_job. No sign-in.

Claude

Customize → Connectors → + Add → Add custom connector. Name it Full Stack Jobbies, paste the URL above, and pick No sign in. Then switch it on from the + menu in a chat.

Claude Code
claude mcp add --transport http \
  fullstackjobbies \
  https://fullstackjobbies.com/mcp
Cursor and others
{ "mcpServers": {
  "fullstackjobbies": {
    "url": "https://fullstackjobbies.com/mcp"
} } }

2. REST API

Plain JSON over HTTPS for your own scripts and agents. CORS is open.

Search jobs

GET /api/jobs?where=US,CA&min_rating=4
             &stack=react,node
             &hide_interview_styles=live_algorithm
             &salary_min_usd=150000&limit=20
  • where: country codes you can work from
  • min_rating: 0 Bloody mess … 5 Rocket ship
  • stack: every one must be required
  • hide_interview_styles: live_algorithm, take_home, unpaid_take_home, paid_take_home, pairing, conversation
  • salary_min_usd, remote_only, q, limit (max 100)

Rate any job

curl -X POST https://fullstackjobbies.com/api/rate \
  -H 'content-type: application/json' \
  -d '{"url": "https://boards.greenhouse.io/acme/jobs/123"}'

Or send {"text": "…the description…"}. You get the rating, the reasons behind it, red flags, salary, stack and interview style. LinkedIn and Indeed links can't be read; send their text instead.

3. Agent skill

One file that teaches your agent the Jobbie Scale, the API, and the house rule: ask before applying to anything.

Download SKILL.md

Play nice

The data refreshes once a day, so there's no need to poll. Search once per task and reuse the results. If a job came from Remote OK, credit and link them; their terms require it, and the API tells you when.