- Last commit
- 25d ago
- Forks
- 0
- Open issues
- 0
- Registry update
- Oct 13, 2026
Connect
remote$claude mcp add --transport http jobs https://4dayweek.io/api/mcpHeaders
Nothing to configure — it works as is.
Security review
Review passedReviewed 27m ago.
- tools
- 6 tools scanned
- metadata
- scanned
No findings.
Tools
6explain_schedule_type
Defines a working-hours schedule precisely: what it means, whether it genuinely reduces weekly hours, whether that reduction is at full pay, the typical hours, and — where one is commonly made — the mistake most often made about it. Call it when the user's question turns on what a schedule means, for example whether a compressed 4x10 counts as a 4-day week, or whether a schedule is at full pay. A compressed 4x10 gives four days but not fewer hours, and is not a 4-day week. Omitting the argument returns every definition at once.
get_company
Fetch one employer's full profile by slug, as returned by search_companies. Returns the schedule policy and what it means, full-time weekly hours, the office-presence policy and whether the employer hires worldwide, benefits, industry, headcount, founding year, the work-life score, the count of open roles, and the employer's own website. Where the employer has published them, it also returns which day is off, vacation days, fully-paid parental leave weeks for both parents, a no-meeting day, and verified work-life awards with the year and a proof url for each. Where the employer's schedule is sourced from a public announcement, four_day_reference_url is that source.
get_job
Fetch one live job listing in full by its slug, as returned by search_jobs. Returns the complete description, the schedule type and what it means, weekly hours, work arrangement and locations, category, seniority, contract type, required skills, acceptable timezones where the employer listed them, visa sponsorship where the employer stated one, the work-life score, and salary ONLY where the employer published one — we never estimate a salary. A very long description is truncated on a paragraph boundary; when that happens the response says so and gives the url of the full listing. Applying happens on the job's page on 4dayweek.io, which the url field points to. apply_method says what a person finds there: "external" means the page hands off to the employer's own application form, "on_page" means they apply on 4dayweek.io itself. There is no separate employer link in this response, and constructing one is not possible from it.
get_market_stats
Aggregate statistics on the reduced-hours job market: how many employers are tracked, how many run each schedule type, the distribution of weekly hours, and which day the non-working day falls on. Use this for "how common is a 4-day week" questions. The response separates genuinely reduced-hours employers from compressed 4x10 employers, and reports the full-pay and pro-rata splits separately, so quote whichever the question actually asked for. Figures carry an as_of date; cite it.
search_companies
Search employers by their working-hours policy. This answers "which companies offer a 4-day week" style questions at the employer level, where the policy actually lives, rather than per listing. The same schedule_type semantics as search_jobs apply: "compressed_week" is a 4x10 and is not a 4-day week. Two location facts are separate and are often confused. country is where the employer is based. hires_worldwide is whether it accepts applicants from any country. remote_level is its office-presence policy, and a fully-remote employer can still hire in one country only. Each result carries the employer's name, slug, url, schedule type, full-time hours, remote level and count of open roles. get_company takes the slug and returns the full profile. Paging works as in search_jobs: at most 25 employers per call, with page, page_size, returned, total_matching, has_more and next_page.
search_jobs
Search live job listings with genuinely better working hours. Every listing carries an explicit schedule_type, so you never have to infer one: - "4_day_week": 36 hours or less, 100% salary. The ONLY type that is reduced hours at full pay. - "4_day_week_pro_rata": four days at pro-rata (reduced) pay. - "9_day_fortnight", "half_day_fridays", "rotating_4_day", "summer_fridays", "part_time": other genuinely reduced-hours patterns. - "compressed_week": a 4x10. The SAME 40 hours in four days. NOT a 4-day week, and never to be described as one. - "flexible_hours", "unlimited_pto", "generous_pto", "flex_fridays", "no_meeting_days", "generous_parental_leave", "best_place_to_work": a full working week with a flexibility or leave policy. To answer "find me a 4-day week job", pass schedule_type="4_day_week". Passing nothing returns all reduced-hours AND flexibility listings, which is usually broader than the user meant. On locations: a job with no location restriction is worldwide-rem
README
4dayweek/mcp/README.md4dayweek.io MCP server
A free, read-only Model Context Protocol server over 4dayweek.io, a job board for roles with genuinely reduced working hours: 4-day weeks, 9-day fortnights, half-day Fridays and more.
Connect it to Claude, ChatGPT, Cursor, Codex or any other MCP client and your assistant can search live listings and employers directly, instead of scraping the site. There is no API key and no sign-up.
| Endpoint | https://4dayweek.io/api/mcp |
| Transport | Streamable HTTP (stateless) |
| Authentication | None — anonymous, read-only |
| Server name | io.4dayweek/jobs |
| Version | 1.3.0 |
| Documentation | https://4dayweek.io/mcp |
This repository holds the manifest and the documentation. The server itself runs on 4dayweek.io; there is nothing to install or host.
Add it to your assistant
Claude Code
claude mcp add --transport http 4dayweek https://4dayweek.io/api/mcp
Claude (web and desktop) — Settings → Connectors → Add custom connector, then paste
https://4dayweek.io/api/mcp. No authentication needed.
ChatGPT — Settings → Connectors → Advanced → Developer mode, then add a connector pointing at
https://4dayweek.io/api/mcp.
Codex
codex mcp add 4dayweek --url https://4dayweek.io/api/mcp
or in ~/.codex/config.toml:
[mcp_servers.4dayweek]
url = "https://4dayweek.io/api/mcp"
Cursor — .cursor/mcp.json in your project, or ~/.cursor/mcp.json globally:
{
"mcpServers": {
"4dayweek": {
"url": "https://4dayweek.io/api/mcp"
}
}
}
VS Code — .vscode/mcp.json:
{
"servers": {
"4dayweek": {
"type": "http",
"url": "https://4dayweek.io/api/mcp"
}
}
}
Anything else — the transport is streamable HTTP, so any MCP client can reach it directly:
curl -X POST https://4dayweek.io/api/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{
"protocolVersion":"2025-06-18","capabilities":{},
"clientInfo":{"name":"curl","version":"1.0"}}}'
As a Claude Code plugin
This repository doubles as a Claude Code plugin marketplace, so the connector can be installed by name and listed alongside your other plugins:
/plugin marketplace add 4dayweek/mcp
/plugin install 4dayweek@4dayweek-io
The claude mcp add line above does the same job in one command; the plugin route just keeps it in
your plugin list and updates with this repository.
Tools
Six tools. Every one is read-only and says so in the protocol, so a cautious client can call them freely.
| Tool | What it returns |
|---|---|
search_jobs | Live listings, filtered by schedule type, category, country, work arrangement, seniority, skills, work-life score or posting date. |
get_job | One listing in full by slug, including hours, locations and a published salary. |
search_companies | Employers by working-hours policy, country, office-presence policy and whether they hire worldwide. |
get_company | One employer's full profile: schedule policy, weekly hours, office policy, benefits and work-life score — plus day off, vacation and awards where the employer has published them. |
get_market_stats | Aggregate market data across tracked employers, carrying an as-of date and its own caveats. |
explain_schedule_type | Precise definitions: whether a schedule genuinely reduces weekly hours, and whether that is at full pay. |
Try it
Find me remote 4-day-week engineering jobs open to applicants in the UK.
What is a 9-day fortnight, and is it the same as a compressed week?
Which employers run a genuine 4-day week at full pay, and how many are there?
Tell me about AWIN's 4-day week, and how it was verified.
Show me senior product roles at 32 hours a week, posted in the last fortnight.
A compressed 4x10 is not a 4-day week
This is the distinction the tool descriptions exist to carry. A compressed week packs the same 40
hours into four days; a 4-day week is 36 hours or fewer with no cut in pay. Every listing carries an
explicit schedule type, and explain_schedule_type states, for any schedule, whether it genuinely
reduces weekly hours and whether that reduction is at full pay — so an assistant reading these tools
gets it right without being prompted.
Limits and behaviour
- Rate limit: 300 requests per minute sustained, bursting to 60.
X-RateLimit-Limitreports the burst ceiling. - Paging: 10 results per page by default, 25 maximum, up to page 200. Responses carry
has_moreandnext_page, and say so when the page ceiling is reached. - Read-only by construction: the server can only reach read methods — a tool that writes would not compile. Nothing you send is stored as user data, and there is no account to create.
- Applications happen on the site.
get_jobreturns the job's page on 4dayweek.io and whether the employer takes applications on-site or elsewhere; it never returns the employer's raw application URL.
Privacy
The endpoint is anonymous. Each call is logged with the requesting IP, user agent, path, timestamp and the name of the tool called, for abuse prevention and to see which tools are used — at most 14 days, in practice about two. No account, no cookies, no personal data. Full policy: https://4dayweek.io/privacy
Licence
The contents of this repository — the manifest, this documentation and the configuration snippets — are MIT licensed (see LICENSE and NOTICE).
That is not a licence to the data. Results returned by the API and the MCP endpoint are covered by section 10 of our Terms: a limited, revocable licence to use and display them in your own product, conditioned on crediting 4dayweek.io and linking back, staying within the rate limits, not misstating an employer's working-hours policy, and not using them to build a competing job board. Our aggregate market statistics are separately published under CC BY 4.0 on our data page.
Support
- Documentation: https://4dayweek.io/mcp
- Contact: https://4dayweek.io/contact
From the server's repository — third-party content, read it before running anything it suggests.
More in Marketing
kazi-mcp
io.github.gabrielmahia
MCP server for jobs and employment coordination in East Africa (kazi = work)
Instoryview
io.github.instoryview
Instagram profiles, follower/following snapshots and changes, with budgeted public lookups.
AdAnvil
io.github.maxbuildog
Lets an AI agent edit vertical 9:16 video ads from your footage, a reference ad or an idea.
LinkBit
io.github.yutotanakastar
Shorten URLs, bulk create, QR, and click analytics for LinkBit.
Openings
co.avagama
Search jobs on verified employer job boards. Every link is the employer's own posting.
YouTube MCP
io.github.granitebps
Read YouTube video metadata, transcripts, comments, and search results. No API key needed.
Listing from the official MCP Registry · repository facts from GitHub, 30m ago.