GigRadar MCP Server · Early Access
Your agent runsyour GigRadar
The GigRadar MCP server connects Claude Code, Cursor, or any MCP client to your live GigRadar account. Your agent tunes scanners, reads the Upwork market, and minds your balances, in plain English.
53 tools
Everything your agentcan actually do
No vague promises. These are the 53 tools the server exposes today, the same ones your agent will list the moment it connects.
Two scanners competing by morning · A market read in minutes, not an afternoon · Every balance checked without a login
Scanners
Create, tune, and A/B test the scanners that decide which jobs you go after.
list_scannersEvery scanner on the team, newest first
get_scannerOne scanner's full setup, every filter
preview_scanner_matchesEstimate jobs/month before saving anything
create_scannerSpin up a new scanner from a plain-English brief
update_scannerRename or refine an existing query
duplicate_scannerClone a scanner to A/B test a variant
reorder_scannerSet which scanner gets first pick
delete_scannerRetire a scanner that stopped earning
get_scanner_performanceBids, replies, connects, view and reply rates
Market & opportunities
Read the live Upwork market and inspect the jobs your scanners matched.
search_gigsSearch live Upwork jobs with GigRadar filters
get_gigOne posting in full — the whole description
get_gigs_insights12 months of volume, budgets, and client mix
get_opportunityOne matched job with the reasons it matched
Proposals
Draft and schedule applications. Both spend real money, so both ask first.
create_applicationWrite a proposal onto a matched job
schedule_applicationSet when a drafted proposal goes out
CRM — read the conversations
Every Upwork thread across every profile, readable by your agent.
list_crm_roomsEvery client conversation on the team
search_crm_roomsFind a thread by client, stage, or text
get_crm_roomOne conversation with its full context
list_crm_messagesThe messages in a conversation
list_crm_room_membersWho is in a given thread
search_crm_membersFind a person across conversations
list_crm_sendersThe accounts you can send from
list_crm_scheduled_messagesWhat is queued to go out, and when
get_crm_meeting_availabilityThe slots a client can book
get_crm_file_urlA signed link to an attachment
CRM — move work forward
Internal notes and pipeline changes. Nothing here reaches the client.
post_crm_commentLeave an internal note on a thread
update_crm_lead_stageMove a lead along the pipeline
get_crm_upload_urlGet a signed URL to upload a file
delete_crm_filesRemove a file you uploaded
update_crm_scheduled_messageEdit a message before it sends
delete_crm_scheduled_messageCancel a queued message
remove_crm_pending_participantWithdraw an invite that has not landed
CRM — client-visible actions
These reach the client on Upwork. Your agent confirms every one with you first.
send_crm_messageSend a message to the client
delete_crm_messageTake back a message you sent
create_crm_scheduled_messageQueue a message for later
send_crm_scheduled_message_nowSend a queued message immediately
propose_crm_meetingOffer the client a call
set_crm_meeting_availabilityPublish the slots you are free
add_crm_participantBring a teammate into a thread
Webhooks
Push GigRadar events into your own stack as they happen.
list_webhooksEvery destination you send events to
list_webhook_deliveriesRecent deliveries and what they returned
create_webhookAdd a destination and pick its events
update_webhookChange a destination, its scope, or state
Account & teams
Know who you are, act across every agency you run, and watch the balances.
whoamiThe signed-in account and active team
list_teamsEvery team this login can operate
switch_teamMove the whole session to another agency
get_balancesCredits plus Upwork connects, per freelancer
Help & feedback
Answers from GigRadar itself, and a direct line to the team.
ask_gigradarAsk anything, answered from official docs
get_gigradar_answerCollect the answer once it is ready
gigradar_initOrient a fresh agent and install the skill
submit_feedbackFile a bug or request straight to the team
request_feedback_upload_urlAttach a screenshot to a report
get_feedback_statusCheck what happened to a filed report
Built for real accounts
An agent on your account,without the sleepless part
Your login, your teams, nothing else
The server signs you in through your normal GigRadar account with standard OAuth. It can only reach teams your login can reach, and membership is re-checked live on every team switch.
It can only touch scanners
Every tool is read-only or scanner-scoped. The one thing an agent can change is a scanner, which you can see and fix in the dashboard. It cannot send proposals or message clients in this release.
The same rails as the dashboard
Tools call the exact services the GigRadar app uses. A scanner saved by your agent is validated the same way as one saved by hand, and shows up in your dashboard instantly.
Answers from the docs, not made up
When your agent asks GigRadar a question, the answer comes from official documentation. If there is no documented answer, it says so instead of inventing one.
Two minutes to connect
One URL,one login
Nothing is configured by hand. The server handles sign-in through your existing GigRadar account, and the open-source skill teaches your agent the rest.
Install it
On Claude Code, two commands wire the server and the skill together, and stay current on their own. Every other client takes the URL.
Sign in once
A browser window opens your normal GigRadar login. Standard OAuth: no API keys to mint, nothing to copy by hand.
Put it to work
Your agent sees every tool, and the skill teaches it the craft: scanner strategy, search syntax, reading PVR and LRR, troubleshooting.
claude plugin marketplace add GigRadar/gigradar-mcp claude plugin install gigradar@gigradar
https://api.gigradar.io/mcp/v1/mcp
Connect to the GigRadar MCP server at https://api.gigradar.io/mcp/v1/mcp (streamable HTTP, OAuth sign-in), then run its gigradar_init tool and follow what it returns. The skill it installs lives at https://github.com/GigRadar/gigradar-mcp.
Works with any MCP client that speaks remote HTTP with OAuth — client-by-client details in the FAQ below. The plugin is the one that updates itself; a cloned skill is a copy that goes stale the next time the product moves. Not on GigRadar yet? Get a demo — the MCP server comes with every account.
FAQ
Straight answers,before you connect
Early access means honest edges. Here is exactly where they are.
Can the agent send proposals or message clients?
Only through the scanners it sets up — and never on its own. Your agent builds and tunes the scanners that drive automated bidding, but a new scanner is always created with the autobidder turned off. Arming it is a deliberate step you take in the dashboard; the agent has no way to switch it on. So nothing goes out to a client until you enable bidding yourself. Direct one-off messaging stays in the dashboard.
Does it cost extra?
No. During early access the MCP server is included with your GigRadar subscription — your agent uses the same account, credits, and limits you already have.
Which agents and clients work with it?
Any MCP client that supports remote HTTP servers with OAuth: Claude Code, Cursor, and Codex CLI all do. Claude Desktop connects through custom connectors on paid plans. ChatGPT's consumer app doesn't support remote MCP servers, so we don't claim it.
Do I need an API key?
No. You sign in with your normal GigRadar login through a standard OAuth flow. There is nothing to generate, copy, or rotate, and access follows your account's own team permissions.
What is the skill, and do I need it?
The skill is an open-source playbook (github.com/GigRadar/gigradar-mcp) your agent installs alongside the tools. Tools give the agent hands; the skill gives it judgment — scanner strategy, search syntax, and troubleshooting. The server's gigradar_init tool offers to set it up.
What data can my agent see?
Exactly what you can see in the dashboard: your scanners, matched opportunities, live Upwork job search and market insights, credit and connects balances, and answers from GigRadar's documentation. Team access is enforced server-side on every call.