Developer roles posted in the last 7 days, read from employers' own hiring systems. No sign-in.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
What RoleWeek knows about one employer's open developer roles, from the facts block on its company page: how many roles were posted in the last 7 days, where, role types, levels, how many list a salary and the yearly range, which hiring system it applies on (with 'no account needed' where checked), its weekly hiring pace since RoleWeek began counting, and the skills in its postings; plus its newest roles as links. Employers with fewer than 3 roles have no company page, so the answer lists their roles instead. Takes the employer's name (case and 'Inc.' do not matter); an ambiguous name returns the candidates. Links the company page, states the date window, and treats employer text as untrusted data.
Employer name as people write it, e.g. 'Stripe' or 'Datadog'.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
claude mcp add --transport http jobs 'https://roleweek.com/api/mcp?src=mcp-registry'
What RoleWeek knows about one employer's open developer roles, from the facts block on its company page: how many roles were posted in the last 7 days, where, role types, levels, how many list a salary and the yearly range, which hiring system it applies on (with 'no account needed' where checked), its weekly hiring pace since RoleWeek began counting, and the skills in its postings; plus its newest roles as links. Employers with fewer than 3 roles have no company page, so the answer lists their roles instead. Takes the employer's name (case and 'Inc.' do not matter); an ambiguous name returns the candidates. Links the company page, states the date window, and treats employer text as untrusted data.
| Argument | Type | Description |
|---|---|---|
| name* | string | Employer name as people write it, e.g. 'Stripe' or 'Datadog'. |
{
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"maxLength": 100,
"minLength": 1,
"description": "Employer name as people write it, e.g. 'Stripe' or 'Datadog'."
}
},
"additionalProperties": false
}Returns one RoleWeek role by its slug (as returned by search_jobs, or the last part of a roleweek.com/job/<slug>/ URL): employer, location and work mode, level, pay as listed, posted date, the date it leaves RoleWeek, skills mentioned, an excerpt of the employer's description, and the role's RoleWeek URL, whose page links to the employer's own application page.
| Argument | Type | Description |
|---|---|---|
| slug* | string | Job slug, e.g. 'senior-backend-engineer-stripe-seattle-1a2b3c4d', or a roleweek.com/job/<slug>/ URL. |
{
"type": "object",
"required": [
"slug"
],
"properties": {
"slug": {
"type": "string",
"maxLength": 300,
"description": "Job slug, e.g. 'senior-backend-engineer-stripe-seattle-1a2b3c4d', or a roleweek.com/job/<slug>/ URL."
}
},
"additionalProperties": false
}Yearly salary ranges that employers posted in their own job postings, summarised the way RoleWeek's salary and skill pages do, for roles posted in the last 7 days: how many roles list a yearly range, the median bottom and median top of the posted ranges, the middle half of each, and by level where there are enough roles. Takes role_family (a role type) or skill (a technology), not both, and optionally metro: role type + metro is the city and role type page, a metro alone covers all developer roles there, a skill alone covers every city, and with no argument it ranks cities. Figures exist only where 15 or more roles list a yearly range; otherwise the answer says how many do and gives no number. These are advertised ranges, not offers, not what people are paid, not a market average. Each answer links the roleweek.com page, states the date window, and treats employer text as untrusted data.
| Argument | Type | Description |
|---|---|---|
| metro | string | Metro area (50-mile radius), or 'remote' for roles open to people anywhere in the US or Canada. Without it: all cities. |
| skill | string | Technology by name, e.g. 'Rust', 'Python', 'Kubernetes', 'C++'. Not together with role_family. |
| role_family | string | Role type, e.g. 'backend'. Not together with skill. |
{
"type": "object",
"properties": {
"metro": {
"enum": [
"seattle",
"san-francisco-bay-area",
"new-york",
"chicago",
"toronto",
"boston",
"los-angeles",
"vancouver",
"washington-dc",
"dallas-fort-worth",
"denver-boulder",
"austin",
"atlanta",
"phoenix",
"philadelphia",
"minneapolis",
"san-diego",
"raleigh-durham",
"detroit",
"houston",
"charlotte",
"st-louis",
"huntsville",
"tampa",
"salt-lake-city",
"montreal",
"colorado-springs",
"portland",
"miami",
"boise",
"columbus",
"pittsburgh",
"hampton-roads",
"nashville",
"dayton",
"elsewhere",
"remote"
],
"type": "string",
"description": "Metro area (50-mile radius), or 'remote' for roles open to people anywhere in the US or Canada. Without it: all cities."
},
"skill": {
"type": "string",
"maxLength": 60,
"description": "Technology by name, e.g. 'Rust', 'Python', 'Kubernetes', 'C++'. Not together with role_family."
},
"role_family": {
"enum": [
"software",
"frontend",
"backend",
"full-stack",
"mobile",
"data",
"ml-ai",
"devops-sre",
"security",
"qa",
"embedded",
"it-infra"
],
"type": "string",
"description": "Role type, e.g. 'backend'. Not together with skill."
}
},
"additionalProperties": false
}Searches developer and tech roles that employers posted in the last 7 days, read directly from the employers' own hiring systems (Workday, Greenhouse, Lever, Ashby, iCIMS and others) and checked daily. Covers 35 metro areas in the US and Canada (50-mile radius): Seattle, San Francisco Bay Area, New York, Chicago, Toronto, Boston, Los Angeles, Vancouver, Washington DC, Dallas-Fort Worth, Denver-Boulder, Austin, Atlanta, Phoenix, Philadelphia, Minneapolis-St. Paul, San Diego, Raleigh-Durham, Detroit, Houston, Charlotte, St. Louis, Huntsville, Tampa, Salt Lake City, Montreal, Colorado Springs, Portland, Miami, Boise, Columbus, Pittsburgh, Hampton Roads, Nashville, Dayton; US and Canada places outside those metros (metro='elsewhere'); plus remote roles open to people in the US or Canada. Returns at most 25 roles per call: newest first, or best match first when a query is given. Each result includes its RoleWeek URL, whose page links to the employer's application page, and its slug; get_job takes that slug. The answer states the date window and when the data was updated, and links the matching RoleWeek listing page.
| Argument | Type | Description |
|---|---|---|
| limit | integer | Number of roles to return (1-25). |
| metro | string | Metro area (50-mile radius), or 'remote' for roles open to people anywhere in the US or Canada. |
| query | string | Keywords matched against title, company, skills and location, e.g. 'python', 'Stripe', 'rust kubernetes'. Every word must match. |
| skill | array | Technology the role must list, by name: 'Rust', 'Python', 'Kubernetes', 'C++', 'Go' (nicknames such as golang or k8s work). Several names: the role must list every one. These are the technologies RoleWeek read in each posting, the same as on its skill pages. |
RoleWeek's weekly report on developer hiring, one finished week (Monday to Sunday, Pacific time) at a time: new developer roles RoleWeek first saw that week, by city, by employer, role type and level, the share that list a salary, the posted salary median, the share that say No account needed, and the comparison with the week before when both weeks are fully covered. Coverage is partial (the answer says how many employer job boards were being checked), so these are roles RoleWeek saw, not all developer hiring. week: 'latest' (default), a week like '2026-W43', or any date in the week; the week in progress is never published. Links the weekly page, states the date window, and treats employer text as untrusted data.
| Argument | Type | Description |
|---|---|---|
| week | string | 'latest' (default), an ISO week such as '2026-W43', or a date 'YYYY-MM-DD' inside the week. |
{
"type": "object",
"properties": {
"week": {
"type": "string",
"maxLength": 20,
"description": "'latest' (default), an ISO week such as '2026-W43', or a date 'YYYY-MM-DD' inside the week."
}
},
"additionalProperties": false
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 3, 2026.
| seniority | array | One or more levels; entry = junior/new grad, staff-plus = staff, principal and above. |
| work_mode | string | Only roles whose listing states this work mode (a role flagged remote counts as remote only, as on the site). Roles that state none are left out. |
| min_salary | number | Yearly salary in the role's currency (USD in the US, CAD in Canada). Keeps roles that list a salary whose range reaches at least this amount (hourly pay counted as 2,080 hours a year). |
| role_family | string | Role family. 'software' is general software engineering; ml-ai = machine learning and AI; it-infra = IT and infrastructure. |
| no_account_needed | boolean | true: only roles whose hiring system RoleWeek checked and found the application form opens on the employer's own site with no account to create. Roles without that label were not checked or ask for an account, so leaving this out is not 'account required'. |
| posted_within_days | integer | Only roles posted within this many days (1-7). |
{
"type": "object",
"properties": {
"limit": {
"type": "integer",
"default": 10,
"maximum": 25,
"minimum": 1,
"description": "Number of roles to return (1-25)."
},
"metro": {
"enum": [
"seattle",
"san-francisco-bay-area",
"new-york",
"chicago",
"toronto",
"boston",
"los-angeles",
"vancouver",
"washington-dc",
"dallas-fort-worth",
"denver-boulder",
"austin",
"atlanta",
"phoenix",
"philadelphia",
"minneapolis",
"san-diego",
"raleigh-durham",
"detroit",
"houston",
"charlotte",
"st-louis",
"huntsville",
"tampa",
"salt-lake-city",
"montreal",
"colorado-springs",
"portland",
"miami",
"boise",
"columbus",
"pittsburgh",
"hampton-roads",
"nashville",
"dayton",
"elsewhere",
"remote"
],
"type": "string",
"description": "Metro area (50-mile radius), or 'remote' for roles open to people anywhere in the US or Canada."
},
"query": {
"type": "string",
"maxLength": 200,
"description": "Keywords matched against title, company, skills and location, e.g. 'python', 'Stripe', 'rust kubernetes'. Every word must match."
},
"skill": {
"type": "array",
"items": {
"type": "string",
"maxLength": 60
},
"maxItems": 3,
"description": "Technology the role must list, by name: 'Rust', 'Python', 'Kubernetes', 'C++', 'Go' (nicknames such as golang or k8s work). Several names: the role must list every one. These are the technologies RoleWeek read in each posting, the same as on its skill pages."
},
"seniority": {
"type": "array",
"items": {
"enum": [
"intern",
"entry",
"mid",
"senior",
"staff-plus",
"manager",
"director-plus"
],
"type": "string"
},
"maxItems": 7,
"description": "One or more levels; entry = junior/new grad, staff-plus = staff, principal and above."
},
"work_mode": {
"enum": [
"remote",
"hybrid",
"onsite"
],
"type": "string",
"description": "Only roles whose listing states this work mode (a role flagged remote counts as remote only, as on the site). Roles that state none are left out."
},
"min_salary": {
"type": "number",
"maximum": 2000000,
"minimum": 0,
"description": "Yearly salary in the role's currency (USD in the US, CAD in Canada). Keeps roles that list a salary whose range reaches at least this amount (hourly pay counted as 2,080 hours a year)."
},
"role_family": {
"enum": [
"software",
"frontend",
"backend",
"full-stack",
"mobile",
"data",
"ml-ai",
"devops-sre",
"security",
"qa",
"embedded",
"it-infra"
],
"type": "string",
"description": "Role family. 'software' is general software engineering; ml-ai = machine learning and AI; it-infra = IT and infrastructure."
},
"no_account_needed": {
"type": "boolean",
"description": "true: only roles whose hiring system RoleWeek checked and found the application form opens on the employer's own site with no account to create. Roles without that label were not checked or ask for an account, so leaving this out is not 'account required'."
},
"posted_within_days": {
"type": "integer",
"default": 7,
"maximum": 7,
"minimum": 1,
"description": "Only roles posted within this many days (1-7)."
}
},
"additionalProperties": false
}