careersfuture-mcp

A Model Context Protocol server (TypeScript, stdio) for searching Singapore job postings on MyCareersFuture.

Unofficial. This wraps the public web API that the MyCareersFuture site itself uses. It was reverse-engineered (see docs/mycareersfuture-api.md), is not documented or supported by the operator, and can change or break without notice. No authentication is used, and the server never calls the view-count or analytics endpoints. Please keep request volume modest.

Install

Published on npm as careersfuture-mcp. Requires Node.js 20+. No API key or configuration needed.

The easiest way is to let your MCP client run it with npx, which downloads and starts the latest version on demand:

npx -y careersfuture-mcp

Or install it globally and use the careersfuture-mcp command:

npm install -g careersfuture-mcp

Claude Code

claude mcp add careersfuture -- npx -y careersfuture-mcp

On Windows (native, not WSL), wrap it with cmd /c:

claude mcp add careersfuture -- cmd /c npx -y careersfuture-mcp

Claude Desktop and other MCP clients

Add to claude_desktop_config.json (or your client's equivalent MCP config):

{
  "mcpServers": {
    "careersfuture": {
      "command": "npx",
      "args": ["-y", "careersfuture-mcp"]
    }
  }
}

On Windows, use "command": "cmd" and "args": ["/c", "npx", "-y", "careersfuture-mcp"]. If you installed globally, you can use "command": "careersfuture-mcp" with no args instead.

Related MCP server: Remotive Scout MCP

What this MCP does not do

• Auto-submit an application

• Send an email

What this MCP do

Tools

All tools are read-only (readOnlyHint, openWorldHint), return JSON text plus structuredContent (with an outputSchema), and report failures as isError results instead of crashing.

search_jobs

Search postings. Returns { total, page, limit, hasMore, results[] } (plus filteredOutByMinPostingDate when minPostingDate is set). Each result is a compact summary: uuid, title, company, hiringCompany, salary min/max/type, isHideSalary, employmentTypes, positionLevels, categories, district, newPostingDate, jobPostId, totalNumberJobApplication. With detail: "full" it also has address, skills and jobDetailsUrl. Descriptions and ranking scores are never included; use get_job. Text output is compact (unindented) JSON, and large limit values still produce large outputs.

Only provided fields are sent. The body always has "sessionId": "" and never guid.

get_job

Full posting for one job. Inputs: uuid (32 hex chars; hyphenated UUIDs accepted), optional lang (english | zh-Hans | ms | ta), optional includeRawHtml (default false). The HTML description is converted to plain text. Never sends updateApplicationCount.

list_employment_types

No inputs. Returns a static, live-tested table { employmentTypes: [{ id, searchName, graphqlName }] } with no network call. Pass searchName to search_jobs; graphqlName is the upstream lookup's label, which search rejects for Internship and Flexi Time (the lookup is not used, for that reason).

suggest_skills

Input: jobTitle. Returns { skills: [{ skill, uuid }] }; the uuids work as skillUuids in search_jobs.

suggest_jobs

Input: searchTerms (string[]) and/or skillUuids (string[]); at least one required. Returns { total, results[] } with the same summaries as search_jobs.

popular_job_titles / in_demand_job_titles

No inputs. Return { titles: [{ title, count }] }.

Resources

• careersfuture://about - what the server does and its tools

• careersfuture://filters - all allowed, live-tested filter values: employment types, categories, position levels, flexible work arrangements, scheme ids, region to district id table, posting company, sort options, languages.

Example usage

Basic usage

Ask your MCP client something like:

Find the 5 newest permanent software engineer jobs paying at least 6000 a month, then show me the full description of the first one.

which becomes roughly:

{ "name": "search_jobs", "arguments": { "search": "software engineer", "employmentTypes": ["Permanent"], "salary": 6000, "sortBy": "new_posting_date", "limit": 5 } }

{ "name": "get_job", "arguments": { "uuid": "3a368bc886540633415264664f9fdcfa" } }

Advanced usage

Run a cron job everyday at 6pm.

Read my resume at ~/Documents/resume.pdf. From it, work out 3–5 job titles I’m a strong fit for, my seniority, and my core skills.

For each title, call search_jobs with salary: 6000, sortBy: "new_posting_date", minPostingDate set to today’s date in Singapore time, and limit: 50. Keep paging while hasMore is true. Merge the results and remove duplicates by uuid.

Drop any job whose salary is hidden or whose minimum monthly salary is below 6000. For the rest, call get_job and keep only roles whose requirements match my experience and seniority.

Save the results to jobs/.md as a table ranked by fit: title, company, salary range, a one-line reason it fits me, and the job link. If nothing qualifies, write “No matches today.”

0 18 * * * cd ~/job-hunt && claude -p "$(cat daily-jobs-prompt.md)" --allowedTools "Read,Write,mcp__careersfuture__*"

Development

To work on the server from a clone of this repo:

pnpm install
pnpm build
pnpm start         # runs dist/index.js over stdio
pnpm dev           # watch mode via tsx
pnpm typecheck
pnpm test          # no network needed; the HTTP client is faked

The server logs to stderr only; stdout is reserved for MCP JSON-RPC.

Test with the Inspector

pnpm build
pnpm inspect

This runs pnpm dlx @modelcontextprotocol/inspector node dist/index.js and opens the Inspector UI.

Use a local build in Claude

To point a client at your local build instead of the npm package:

claude mcp add careersfuture -- node <abs path>/dist/index.js

For Claude Desktop, use "command": "node" and "args": ["<abs path>/dist/index.js"].