Skip to main content

MCP Integration

Connect your AI agent to Trabajos Online using the Model Context Protocol. For direct REST API access, see the API docs.

What is MCP?

The Model Context Protocol (MCP) is an open standard that allows AI assistants like Claude, ChatGPT, and others to interact with external services. With Trabajos Online’s MCP server, your AI agent can search freelancers, browse jobs, create gigs, and manage contracts — all through natural language.

Installation

MCP Server Configuration

No API key needed upfront. Your agent will use get_pairing_code to pair with your account automatically. Or add TRABAJOS_API_KEY to the env if you already have one.
The easiest way to get API access. Your agent generates a pairing code, your operator enters it on the dashboard, and the API key is auto-configured. No manual key copying needed.
1

Generate code

Agent calls get_pairing_code — gets a code like TRB-A3B7
2

Enter code

Agent tells its operator: “Enter this code at trabajosonline.org/settings”
3

Verify pairing

Agent calls check_pairing_status — API key is auto-saved
No API key needed to start — pairing uses cryptographic agent identity.

Manual API Key Setup (Alternative)

An API key is required for write operations (posting jobs, submitting proposals, sending messages). Read-only operations like searching freelancers work without one.
1

Create account

Sign up at trabajosonline.org and create your account
2

Generate API Key

Go to Settings → API Keys and generate a key
3

Configure

Add it to your MCP config as TRABAJOS_API_KEY
Your key starts with trb_ — copy it immediately, it’s only shown once.
For REST API usage, pass the key as a header:

What you can do

Two roles, one connector. Here is what the agent unlocks for each, and what both share.

Client

You hire someoneDashboard & overview — Active contracts, jobs you posted and unread messages in one call. getDashboardFind talent and services — Search people by skill, city and hourly rate, or packages with a fixed price. searchFreelancers · searchGigs · getUserProfilePost and manage jobs — Draft a posting from a short brief and publish it. Freelance postings are free. postJob · listCategoriesReview proposals and hire — Read the proposals a posting received and accept one to start the contract. getJobApplications · acceptProposalPayments you approve — The agent prepares the deposit or the release and hands you a link. Nothing moves without your confirmation. createDeposit · releasePayment · checkPaymentConfirmation · getPaymentStatus

Freelancer

You do the workDashboard & overview — Active contracts, proposals sent and unread messages in one call. getDashboardFind the right jobs — Search by keyword, category, budget, location and salary range. searchJobs · listCategoriesDraft and submit proposals — Write your proposal with budget and delivery time, and submit it. submitProposalSell service packages — Publish a gig with its packages, price and delivery time so clients can buy directly. createGigContracts and payment status — Follow your contracts and check whether a payment is deposited or released. listActiveContracts · getContract · getPaymentStatus

Shared by both

Available Tools

The following tools are available through the MCP server:

Public Tools (no authentication)

Which search do I use?
  • searchFreelancers → finds people. Tells you who you can hire and what they charge per hour.
  • searchGigs → finds ready-made services, with a set price and delivery date. Like buying a product.

Authenticated Tools (require API key)

The agent never moves your money

The agent asks. You approve. Just like paying online and your bank asking you to confirm on your phone: the shop requests the charge, but you are the one who approves it. Step by step:
1

The agent prepares it

You say “pay the €900 for the contract”. The agent calls releasePayment, but nothing is charged yet.
2

It gives you a link

The agent hands you an address like trabajosonline.org/confirm-payment/73885f28...
3

You confirm

You open the link, see the contract and the amount, and press confirm. That is when the money moves.
This is what the agent returns in the first step:
With checkPaymentConfirmation the agent can keep an eye on it: still pending, done, failed, or expired.
Confirming requires signing in on the website. An API key will not do, not even the agent’s own. If the agent could confirm what it asks for itself, this would protect nothing.
Two more safeguards:
  • The link expires after 15 minutes. Let it lapse and it has to be requested again.
  • Each link works once. Even if the agent retries, you never pay twice.

Compatible Clients

  • Claude Desktop — Full MCP support with tool use
  • Claude Code — CLI with MCP server support
  • Cursor — AI code editor with MCP integration
  • Windsurf — AI-powered IDE with MCP support