Let your assistant do the searching.
Connect the tracker once to Claude, ChatGPT, Claude Code, Cursor or VS Code. Then ask in plain words: what is new at Optiver, star every quant internship in Amsterdam, remind me of the Flow Traders deadline, write me a plan for the roles I am tracking. It signs in with your account and only ever sees your own data. Free.
https://sophron-mcp.curly-fire-2334.workers.dev/mcpLooking for the technical reference? The job tracker MCP server page has the transport, the OAuth details, copy-paste config for every client and all 24 tools.
Things people ask it.
No syntax. Say what you want; the assistant picks the right tool. Tap one to copy it.
Six briefs, ready made.
Each one pulls the data itself and hands your assistant a finished brief. In Claude they appear under the connector; in Claude Code they are slash commands; everywhere else ask for them by name.
Weekly digest
Everything posted in the last days, grouped by firm, with your tracked applications on top. Optional city.
Firm brief
One firm: what is open, what changed, where its offices are, and your history with it.
Application plan
Your starred and tracked roles turned into a week-by-week plan with the deadlines that bite first.
Deadline calendar
Roles and events closing in the next days, optionally one country, as a calendar you can act on.
Compare roles
Two roles side by side: level, location, what the posting asks for, how they sit in your pipeline.
Prep checklist
For one role: what to read, what to practise, what to have ready, built from the posting and the firm.
What it can do.
Twenty-four tools, in four groups. Writes (starring, stages, reminders) go to the same account record the site uses, so what your assistant does shows up here, and the other way round.
Search the board
search_jobslatest_jobsget_joblist_companieslist_eventsYour pipeline
my_rolessave_roleset_stageadd_notemanage_listmy_eventsAlerts and email
set_reminderlist_reminderscancel_reminderwatchlist_watchesunwatchnotification_settingscareer_alertsmute_roleYour board
hide_companyhide_rolereport_roleget_briefConnect it.
About two minutes. Pick your assistant; the steps change with your choice.
Claude.ai in the browser, the desktop app and the mobile apps. Every plan can add it; the Free plan allows one custom connector, so this would be it.
Open Settings (your initials, bottom left), then Connectors. Newer versions list it under Customize, then Connectors.
Click Add custom connector. Name it Jobs, paste the server URL from the top of this page, click Add.
Leave Advanced settings empty: no client id, no secret, no headers.
Jobs now sits in your connector list. Click Connect on its row. A Sophron page opens: sign in with your password, or ask for a login code by email, then click Allow access.
You can revoke this at any time from Claude's connector settings.
Start a new chat. Click + at the bottom of the message box, open Connectors, make sure Jobs is on. The six briefs are listed under Jobs in that same menu.
On a Team or Enterprise plan an owner adds the connector once under Organization settings; every member then clicks Connect and signs in as themselves. Connected before the briefs existed? Disconnect and connect once more.
Plus, Pro, Business, Enterprise and Edu accounts, on the web. Search and your pipeline work; the ready-made briefs are Claude only, so ask in your own words.
Turn on Developer mode: Settings, then Security and login, switch it on. Older builds keep it under Apps & Connectors, Advanced settings.
Go to Settings, Apps & Connectors, click Create. Name it Jobs, add a short description, paste the server URL as the MCP server URL, set Authentication to OAuth, tick the trust box, click Create.
Click Connect on the new Jobs entry. Sign in on the Sophron page and click Allow access.
In a chat, open the + menu, choose Developer mode and tick Jobs. Then ask, naming it: "Use Jobs to show what I starred", "Use Jobs to find new quant internships in Amsterdam this week".
ChatGPT asks you to confirm before it writes anything (star, stage, note). Read the confirmation; it shows exactly what will change.
The terminal, the VS Code and JetBrains extensions, and the desktop app. One command, one sign-in.
In a terminal, run:
claude mcp add --transport http --scope user jobs
--scope user makes it available in every project; leave it out to keep it to the current folder.
Start Claude Code and type /mcp. Pick jobs, choose Authenticate; your browser opens the Sophron page. Sign in, click Allow access; the terminal notices on its own.
The briefs are now slash commands: /jobs:weekly_digest, /jobs:firm_brief Optiver, /jobs:application_plan, /jobs:deadline_calendar, /jobs:compare_roles, /jobs:prep_checklist. Attach sophron://me/pipeline or sophron://tracker/stats with @.
Added it without --scope user? Run claude mcp remove jobs and add it again.
Cursor 1.0 or later. Remote MCP servers with OAuth work out of the box.
Open Cursor Settings (⌘ Shift J on a Mac, Ctrl Shift J on Windows), then Tools & MCP, click New MCP Server.
Paste this into the mcp.json that opens (or into ~/.cursor/mcp.json for every project) and save:
{
"mcpServers": {
"jobs": { "url": "" }
}
}Back in the list, Jobs shows Needs login. Click it. Sign in on the Sophron page, click Allow access. The dot turns green and the tools are listed.
In the agent chat the Jobs tools are on. Ask in plain words, or type / to see the briefs if your version lists MCP prompts.
VS Code 1.99 or later, with Copilot in agent mode.
Open the Command Palette (⌘ Shift P or Ctrl Shift P) and run MCP: Add Server. Choose HTTP, paste the server URL, name it jobs, pick User so it is available in every workspace.
Or by hand in mcp.json:
{
"servers": {
"jobs": { "type": "http", "url": "" }
}
}Click Start above the server entry (or MCP: List Servers, jobs, Start). VS Code asks whether the server may sign you in; allow it. Sign in on the Sophron page, click Allow access.
In Copilot Chat, switch to Agent mode. The Jobs tools are in the tool picker; ask in plain words.
Any client that speaks MCP over Streamable HTTP with OAuth 2.1 (dynamic client registration, PKCE).
Add a remote HTTP server with this URL:
No API key, no headers. The client discovers the OAuth endpoints itself and registers on first use.
On first use it opens the Sophron sign-in page. Sign in, click Allow access. Tokens last 30 days; reconnect after that.
Twenty-four tools, six prompts (the briefs) and three resources: sophron://me/pipeline, sophron://tracker/stats, sophron://firms/<name>.
Questions.
What does it see?
The public board (the same roles, firms and events as this site) and your own record: stars, stages, notes, lists, reminders, watches, email settings. Nothing about any other member. The sign-in page names the assistant that is asking, and you can revoke it in the assistant's settings any time.
Does it apply for me?
No. It searches, sorts, reminds and keeps your pipeline. Applications happen on the firm's own site, where every role links.
Does it cost anything?
No. The tracker and the connector are free. There is no plan to charge for the roles; if anything is ever charged for, it will be convenience, not data.
Will what it does show up here?
Yes, at once. A star from Claude is a star on the tracker; a stage set on the site is what your assistant reports. One record, two ways in.
Something is off with a role or a firm.
Ask the assistant to report it, or write to [email protected]. A reported posting is checked by hand.
Two minutes now, then just ask.
Create an account, verify the email, paste one URL into your assistant. From then on the board comes to you.