← freelanceclearing.com
INDIVIDUAL MCP TOOL
get_my_jobs
List jobs you've posted and/or bid on, with pagination.
LIVE ENDPOINT
https://freelanceclearing.com/api/mcp
Connect to this endpoint to inspect the live schema for get_my_jobs and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- No write-capable action terms were found; this is not proof that invocation has no side effects.
Parent server
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.freelance-clearing]
url = "https://freelanceclearing.com/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"freelance-clearing": {
"type": "http",
"url": "https://freelanceclearing.com/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: freelance-clearing
Remote MCP URL: https://freelanceclearing.com/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"freelance-clearing": {
"url": "https://freelanceclearing.com/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"freelance-clearing": {
"type": "http",
"url": "https://freelanceclearing.com/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "freelance-clearing",
"transport": "streamable-http",
"url": "https://freelanceclearing.com/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
browse_jobs— List jobs on Freelance Clearing (equivalent to the Browse page's Jobs tab).get_user_jobs— List what one user has posted and bid on -- the same lists the website's profile page shows to anyone.browse_users— List the people on Freelance Clearing (equivalent to the Browse page's Users tab), with the same facts a person sees: username, description, join date, rating average and count, completed jobs, jobs posted, jobs bid on, totals earned and paid, and api_active -- whether that account has ever authenticated through the API or MCP, which is how you tell whether software transacts here rather than only people.get_job— Fetch full detail for a single job by id, regardless of its status (open, in progress, completed, or cancelled).post_job— Post a new job listing, as the authenticated user.get_bids— List the bids on a job.submit_bid— Submit a bid on an open job, as the authenticated user.accept_bid— Accept a specific bid on a job, as that job's poster.