Remote Jobs MCP
Dengan terhubung ke server MCP Jobicy publik, alat AI Anda dapat secara mandiri mencari, memfilter, dan mengambil daftar pekerjaan jarak jauh terbaru secara real-time.
Dokumentasi
On this page
Endpoint
api/v2/remote-jobs Authentication
Not required Updated
July 30, 2026
01 · Overview
One endpoint for current remote jobs.
The public Jobs API returns the latest remote listings available on Jobicy. Use it for job discovery products, research tools, community websites, internal dashboards, and prototypes.
FORMAT
Clean JSON
Structured fields for the employer, role, location, job type, description, and salary.
ACCESS
No API key
Start with a simple GET request. No account or authentication header is required.
RESULTS
Up to 100 jobs
Retrieve the latest records and combine location, category, and keyword filters.
Base request Copy
GET https://jobicy.com/api/v2/remote-jobs
02 · Quick start
From zero to the first response.
Start with the public endpoint, add only the filters you need, and keep the source URL when displaying a listing.
- Send a GET request No token or account is required for the public Jobs API.
- Add optional filters Use
count,geo,industry, andtag. - Read the jobs array Store only what your interface needs and retain the original Jobicy URL.
JavaScript Copy
const response = await fetch(
"https://jobicy.com/api/v2/remote-jobs?count=10&geo=usa&industry=engineering"
);
if (!response.ok) {
throw new Error(`HTTP ${response.status}`);
}
const data = await response.json();
console.log(data.jobs);
03 · Query parameters
Request only the listings you need.
All filters are optional. Combine them to narrow the results by count, geographic eligibility, job category, or text keyword.
count
Number of listings to return. Accepted range: 1–100.
Default 100
geo
Location slug such as usa, europe, or apac.
Optional
industry
Category slug such as engineering, marketing, or data-science.
Optional
tag
Keyword search applied to the available job content.
Optional
Use current slugs
Load the location list and category list before storing values in a production integration.
Request examples
Keyword search
Twenty recent jobs mentioning Python.
GET /api/v2/remote-jobs?count=20&tag=python
Country filter
Fifteen recent jobs available in Canada.
GET /api/v2/remote-jobs?count=15&geo=canada
Category and location
Marketing jobs available to applicants in the USA.
GET /api/v2/remote-jobs?geo=usa&industry=marketing
Customer success
Five recent customer support opportunities.
GET /api/v2/remote-jobs?count=5&industry=supporting
04 · Response fields
Data ready for display or analysis.
Each job includes its source URL, employer, eligibility, employment type, description, publication date, and salary information when supplied.
| Field | Type | Description |
|---|---|---|
| id | integer | Unique Jobicy listing ID. |
| url | string | Canonical Jobicy job URL. |
| jobTitle | string | Role title. |
| companyName | string | Employer name. |
| companyLogo | string | Employer logo URL when available. |
| jobIndustry | array | Job category labels. |
| jobType | array | Employment type values. |
| jobGeo | string | Remote location eligibility. |
| jobLevel | string | Experience or seniority level. |
| jobExcerpt | string | Short listing summary, up to 55 characters. |
| jobDescription | HTML string | Full job description. |
| pubDate | date-time | Original publication date. |
| salaryMin / salaryMax | number | Salary bounds when provided. |
| salaryCurrency | string | ISO currency code. |
| salaryPeriod | string | Salary interval, such as yearly or hourly. |
Job object Copy
{
"id": 123456,
"url": "https://jobicy.com/jobs/example-role",
"jobTitle": "Senior Product Designer",
"companyName": "Example Company",
"companyLogo": "https://example.com/logo.png",
"jobIndustry": ["Creative & Design"],
"jobType": ["full-time"],
"jobGeo": "Anywhere",
"jobLevel": "Senior",
"jobExcerpt": "Short summary of the role",
"jobDescription": "<p>Complete HTML job description</p>",
"pubDate": "2026-07-30T12:00:00+00:00",
"salaryMin": 90000,
"salaryMax": 125000,
"salaryCurrency": "USD",
"salaryPeriod": "yearly"
}
05 · Live API playground
Build and run a request here.
Choose filters, send the request, inspect the JSON response, and copy it into your development workflow.
Request builder GET /api/v2/remote-jobs
Run request Reset
Response Copy
GET https://jobicy.com/api/v2/remote-jobs?count=5
{ "status": "Ready to send a request" }
06 · MCP server
Remote job search for AI tools.
The public MCP server lets compatible assistants, agents, and IDEs discover valid filters and retrieve structured listings through the public Jobicy MCP endpoint.
TOOL 01
get_jobs
Retrieves jobs using optional count, geo, industry, and tag filters.
TOOL 02
get_taxonomies
Returns current location or category slugs before a tool applies strict filters.
MCP configuration Copy
{
"mcpServers": {
"jobicy-jobs": {
"url": "https://jobicy.com/mcp"
}
}
}
Install in Cursor Install in VS Code
07 · RSS feed
Build a filtered feed.
RSS works well for readers, publishing workflows, and automation services that do not need a JSON integration.
Generated feed URL Copy
https://jobicy.com/jobs/feed
Canonical and legacy URLs
Use /jobs/feed for new integrations. The older /feed/job_feed address remains available for compatibility. Polling a few times per day is normally sufficient and must not exceed once per hour.
08 · Fair use
Build useful experiences with Jobicy data.
The Jobicy API is designed for websites, applications, newsletters, research tools, AI products, and other services that help users discover remote work opportunities.
- You may use Jobicy listings in your own products and user experiences without requesting individual permission.
- Keep Jobicy as the original source and preserve the canonical Jobicy job URL when displaying listings.
- You may create your own interfaces, summaries, categories, search experiences, and additional context around listings.
- Do not present Jobicy listings as your own original job postings or remove source attribution.
- Avoid excessive API requests and cache responses where appropriate to provide a reliable experience for everyone.
- Do not use the API to create spam networks, misleading job databases, or services that negatively affect employers or candidates.
No approval required for normal integrations
Most integrations, including job boards, newsletters, career tools, AI assistants, and internal applications, can use the public API without a separate agreement. Contact us only for high-volume commercial partnerships or custom data arrangements.
09 · Integrations
Embed or automate without rebuilding everything.
Use a small widget, the official WordPress plugin, or an automation recipe when a custom API client would add unnecessary work.
01
IFTTT applets
Send new remote jobs to LinkedIn, X, Facebook, Telegram, Slack, Discord, or WordPress.
02
Embeddable widget
Add a responsive job search interface with light and dark themes.
03
WordPress plugin
Display fresh Jobicy listings with the [jobicy_jobs] shortcode.
Widget example
HTML Copy
<div id="jobicy-widget"></div>
<script>
window.jobicyWidgetConfig = {
query: "Developer",
theme: "light",
autoSearch: true,
limit: 10
};
</script>
<script src="https://jobicy.com/api/prod/wg.js"></script>
Get the WordPress plugin Jobicy to WordPress applet Publish to Slack Publish to Discord
10 · Frequently asked questions
Before moving to production.
The main operational details for a stable public API or feed integration.
Does the Jobs API require an API key?
No. The public remote jobs endpoint and taxonomy requests do not require authentication.
How many jobs can one request return?
The count parameter accepts values from 1 to 100. The endpoint returns the latest available matching jobs.
How should a client discover valid filters?
Use ?get=locations and ?get=industries instead of relying on a hard-coded list indefinitely.
Can the job description contain HTML?
Yes. Treat jobDescription as HTML and sanitize it according to the security rules of your application.
How often should an integration poll?
A few checks per day are usually enough. Automated checks must not run more frequently than once per hour.
Ready to test an integration?
Start with the public endpoint, inspect current filter values, and move to MCP, RSS, or the widget when the use case is clear.
Open playground Contact Jobicy
Jobs Talent
Post a Job Add a Company Set a Job Alert
Salaries
Menu
Ask AI
Feedback