DevSnipe MCP Server: Find Freelance Work From Claude
Connect Claude Code, Claude Desktop, or Cursor to your DevSnipe job feed and hunt for freelance work in the same chat window you already code in. Ask which Upwork jobs came in overnight, have the model score the best one against your profile, tighten your matching preferences in plain English, and get a cover letter drafted, without opening a browser tab.
https://devsnipe.com/v1/mcpWhat You Can Do With It
DevSnipe watches Upwork, Skool, LinkedIn, Indeed, and Freelancer and matches new postings against a profile of what you actually do. The MCP server hands that feed to your assistant as tools it can call on its own, so job hunting becomes something you ask for rather than something you go and check.
- Ask for your newest matches and get them summarised, ranked, or filtered however you asked, instead of scrolling a feed
- Paste a job URL into the chat and have the model pull what DevSnipe already knows about it and explain whether it fits you
- Fix your matching profile by describing the change out loud, then see the effect on the next batch of jobs
- Draft a cover letter for a job while the code you would be pitching is still on screen
Connect It in Four Steps
There is no OAuth flow and nothing to install. The DevSnipe MCP server is a stateless HTTP endpoint, and it authenticates with the DevSnipe API key you already have.
1.Grab your DevSnipe API key
Your API key lives on your dashboard. Copy it and keep it handy, it is the only credential the server needs. Everywhere below,
Open your dashboard →YOUR_DEVSNIPE_API_KEYmeans that key. Both a raw key andBearer <key>are accepted, so either form works.2a.Add the server in Claude Code
Run this in your terminal, with your own key swapped in.
Terminalclaude mcp add --transport http devsnipe https://devsnipe.com/v1/mcp --header "Authorization: YOUR_DEVSNIPE_API_KEY"Adding
-s userto that command makes DevSnipe available in every project instead of only the directory you ran it in.2b.Or add it in Claude Desktop or Cursor
If your client is configured with JSON instead, add this block to your MCP config and restart the app.
MCP config{ "mcpServers": { "devsnipe": { "type": "http", "url": "https://devsnipe.com/v1/mcp", "headers": { "Authorization": "YOUR_DEVSNIPE_API_KEY" } } } }3.Confirm the connection
In Claude Code, this lists your configured servers and whether each one connected. DevSnipe should show up as connected.
Terminalclaude mcp list4.Try it in a fresh chat
Paste this into a new conversation. It reads your account, pulls your newest matches, scores the best one, and asks the model to warn you before anything costs a credit.
PromptUsing the devsnipe MCP tools: call get_account and tell me my plan and remaining quota, then list_jobs for my 3 newest matches, then score_job on the best one and explain the score. Tell me the cost before anything that spends credits.
The Nine Tools, and What They Cost
Six tools are free on every plan. Only two spend anything, and they are marked below. Cost and plan are separate things here, so a tool can be free to call and still need a paid plan.
get_accountFreeAll plansYour plan, what funds your next proposal draft, and how much scoring quota you have left today.
list_jobsFreeAll plansYour matched jobs, newest first.
lookup_jobFreeAll plansLook up jobs DevSnipe already knows about by URL.
list_proposalsFreeAll plansThe proposals you have already generated.
get_preferencesFreeAll plansYour matching profile, the description of what you do that decides which jobs reach you.
update_preferencesFreeAll plansChange your matching profile. Patch semantics, so only the fields you send change and everything else is left alone.
score_jobCosts 1 scoring creditAll plansScore a job against your profile. Re-scoring the same job within the 24 hour cache window is free.
submit_jobFreePaid plans onlySubmit a job URL for DevSnipe to ingest and match.
generate_proposalCosts 1 proposal draftPaid plan or proposal creditsDraft a cover letter for a job, using your voice and past work. Needs a paid plan, or a free account holding purchased proposal credits.
It Reads and Drafts, It Does Not Apply
There is no apply tool on the DevSnipe MCP server, and that is on purpose. An assistant connected to it can find jobs and write you a draft, and then it stops. Submitting a proposal happens in the DevSnipe Chrome extension, in your own logged-in browser, where you can watch it and cancel it.
- No tool on this server submits an application or spends Upwork Connects
- The most a model can spend here is a scoring credit or a proposal draft on your DevSnipe account
- Applying stays a separate, deliberate step you take in the browser
Frequently Asked Questions
What is the DevSnipe MCP server?
The DevSnipe MCP server is a Model Context Protocol server at https://devsnipe.com/v1/mcp that gives an AI assistant direct access to a freelancer's DevSnipe job feed. Once connected, an assistant such as Claude Code, Claude Desktop, or Cursor can read the jobs DevSnipe has matched to that freelancer, score a specific job against their profile, edit their matching preferences, and draft a proposal, all from an ordinary chat. It exposes nine tools and uses stateless HTTP transport.
Is the DevSnipe MCP server free to use?
Connecting to the DevSnipe MCP server costs nothing, and six of its nine tools are free on every plan including the free tier: get_account, list_jobs, lookup_job, list_proposals, get_preferences, and update_preferences. Only two tools spend anything. score_job uses one of the daily scoring credits the account already has, and generate_proposal uses one proposal draft. Two tools are also plan-gated: submit_job needs a paid DevSnipe plan, and generate_proposal needs either a paid plan or a free account holding purchased proposal credits.
Which AI clients work with the DevSnipe MCP server?
The DevSnipe MCP server works with any MCP client that supports remote servers over streamable HTTP, which includes Claude Code, Claude Desktop, and Cursor. There is no OAuth flow to complete. Authentication is a DevSnipe API key sent in the Authorization header, so any client that can attach a custom header to an HTTP MCP server can connect.
Can the DevSnipe MCP server apply to jobs for me?
No. The DevSnipe MCP server cannot apply to a job, submit a proposal, or spend Upwork Connects, because no such tool exists on the server. It can read jobs and draft a proposal, and that is where it stops. This is deliberate: applying is handled separately by the DevSnipe Chrome extension, which acts in the freelancer’s own logged-in browser where they can see and cancel what is happening. Keeping the two apart means an AI assistant can never spend Connects on a freelancer’s behalf.
Do I need a paid DevSnipe plan to use the MCP server?
No, a free DevSnipe account is enough to connect to the DevSnipe MCP server and use most of it. Reading matched jobs, looking up a job by URL, reading past proposals, and reading or updating the matching profile are all free on every plan, and score_job works on the free tier too by spending one of that day’s scoring credits. Two tools are gated. submit_job, which asks DevSnipe to ingest a new job URL, needs a paid plan. generate_proposal, which drafts a cover letter, needs either a paid plan or a free account that has bought proposal credits.
What does the DevSnipe MCP server cost to run in a long chat?
Most of a normal session on the DevSnipe MCP server costs nothing, because listing jobs, looking one up, reading proposals, and reading or updating preferences are free and unmetered on every plan. Spending only happens on two calls: each score_job consumes one daily scoring credit, though re-scoring the same job within the 24 hour cache window is free and does not consume another, and each generate_proposal consumes one proposal draft. Calling get_account at the start of a chat reports the remaining scoring quota and what is funding the next proposal draft.
How is the DevSnipe MCP server different from the DevSnipe REST API?
The DevSnipe MCP server and the DevSnipe REST API are two doors into the same house. They serve the same data, enforce the same plan limits and credit costs, and authenticate with the same DevSnipe API key. The difference is who is calling. The REST API is for code a freelancer writes themselves, while the MCP server is for an AI assistant that discovers the available tools on its own and calls them during a conversation. Using one instead of the other does not unlock extra data or raise any limit.
Applying is handled by the Chrome extension.
You Need a DevSnipe Account First
The MCP server reads your job feed, so it needs an account to read. Sign up free, describe what you do, and your API key is on the dashboard a minute later. Most of the server works on the free tier.