Levels.fyi
MCP server by Levels.fyi
Look up salary, company level and open job data from Levels.fyi pay reports to benchmark pay and evaluate offers.
Connect to Levels.fyi
No sign-in needed. Connect with Levels.fyi’s own URL:
Paste it into any client that supports remote MCP servers. Your client talks to Levels.fyi directly, not through mcp.tc.
Share this server
Opens this page, with the URL and setup steps.
mcp.tc/i/levels-fyiAbout
Connects to Levels.fyi compensation data built from over 1M pay reports. You can resolve companies, locations and job families to slugs, then get median total compensation by location, by company level, and for top-paying companies and locations. It also covers vesting schedules, recent salary submissions, open job search and pay metric explanations. Signed-in users can read their profile, upload a resume and add their own salary.
The server is hosted at https://mcp.levels.fyi/ over streamable HTTP. No account is needed to ask questions. Adding your own salary needs only an email, and signing in is needed to read your profile or upload a resume. The free tier filters by job family, location and company.
What you can do
- Resolve company, location and job family names to slugs
- Get median total compensation for a job family in a location
- Get pay by internal company level, such as Meta E5
- Rank top-paying companies and locations within a country
- Browse recent individual salary submissions
- Look up equity vesting schedules for companies
- Search open jobs with stated pay ranges
- Add your own salary or offer after a preview
Tools 30
get-permissionsRead-onlyConnectivity check that returns pong, tool descriptions and rate limits.
get-salary-percentilesRead-onlyMedian yearly total compensation for a job family in one location, last 12 months.
get-salaries-by-company-levelRead-onlyMedian total compensation for each internal level of one company.
search-raw-data-pointsRead-onlyNewest individual salary submissions by job family, location or company.
get-companyRead-onlyCompany profile with headcount, headquarters, founding year, ticker and valuation.
get-company-levelsRead-onlyA company's internal level names for a job family, ordered by seniority.
get-company-groupRead-onlyResolve a named group such as FAANG into company slugs.
search-companiesRead-onlySearch companies and get their Levels.fyi slugs.
search-companies-by-vestingRead-onlyFind companies by equity vesting type, shape, length and cliff.
search-top-companiesRead-onlyTop-paying companies for a job family in one country by median pay.
get-locationRead-onlyDetails for location slugs: type, parent country, currency, coordinates.
get-location-statsRead-onlyTop-paying locations for a job family within a country.
Show 18 more tools
search-locationsRead-onlySearch countries, metro areas and US states to get slugs.
get-job-familyRead-onlyFocus areas and titles available within a job family.
search-job-familiesRead-onlySearch job families and roles to get slugs.
search-job-titlesRead-onlySearch specific job titles and get their ids and parent job family.
search-focus-areasRead-onlySearch specializations within a role and get their slugs.
search-role-termsRead-onlySearch job families, titles and focus tags together in one call.
get-profileRead-onlyRead the signed-in user's Levels.fyi career profile and resume status.
upload-resumeCan deleteAdd or replace the signed-in user's resume.
add-salary-submissionWritesAdd the user's own pay or job offer to Levels.fyi after a preview.
get-salary-submission-by-idRead-onlyGet one salary submission by its UUID.
get-vesting-schedulesRead-onlyStructured equity vesting schedules for one or more companies.
search-jobsRead-onlySearch open jobs with stated pay ranges and filters.
get-jobRead-onlyFull job posting with description, pay range and estimated pay by level.
send-feedbackWritesReport wrong or missing data or a missing feature to Levels.fyi.
search-allRead-onlySearch companies, job families, titles, focus tags, locations and industries at once.
get-available-filtersRead-onlyList the inputs and filter values the free tier supports.
get-metric-explanationRead-onlyExplain a compensation metric such as TC, base salary or sign-on.
get-domain-knowledgeRead-onlyReference knowledge on the Levels.fyi data model by topic.
Read from the live server on 17 Nov 2026. Read-only, Writes and Can delete are hints the server declares; your client decides whether to ask before running a tool.
Example prompts
What does a Meta E5 software engineer make in the Bay Area?
Which companies pay software engineers the most in the United States?
Show the vesting schedule for Amazon and Google equity.
Find open product manager jobs in New York with pay ranges.
Set up
Every client connects to mcp.levels.fyi. Pick yours; the page remembers your choice.
Claude Code
- Run this in a terminal, in your project folder:
claude mcp add --transport http levels-fyi https://mcp.levels.fyi/- Start Claude Code and type
/mcp. levels-fyi should show as connected.
Add --scope user to make it available in every project, not just this one.
Claude Desktop
- Open Customize → Connectors, click + Add, then Add custom connector.
- Name it Levels.fyi and paste this URL:
https://mcp.levels.fyi/- Click Add. Its tools appear in the chat’s tools menu.
Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.
claude.ai
- Open the connector form on claude.ai. This button fills in the name and URL for you:
Add to claude.ai (opens in a new tab)
- Check that the URL reads
https://mcp.levels.fyi/and click Add. - Turn it on in a chat from the tools menu.
Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors.
ChatGPT
- On chatgpt.com, go to Plugins, select +, then Add custom MCP server.
- Enter a name for the server.
- Under Connection, paste
https://mcp.levels.fyi/as the server URL, then for authentication choose No authentication. - Check I understand and want to continue, then select Create as a plugin.
Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).
Cursor
Add to Cursor (opens in a new tab)
Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):
{
"mcpServers": {
"levels-fyi": {
"url": "https://mcp.levels.fyi/"
}
}
}VS Code
Install in VS Code (opens in a new tab)
Or from a terminal:
code --add-mcp '{"name":"levels-fyi","type":"http","url":"https://mcp.levels.fyi/"}'Or commit it to the repo in .vscode/mcp.json:
{
"servers": {
"levels-fyi": {
"type": "http",
"url": "https://mcp.levels.fyi/"
}
}
}Devin Desktop
- Add it to
~/.config/devin/mcp_config.json(macOS and Linux) or%APPDATA%\devin\mcp_config.json(Windows):
{
"mcpServers": {
"levels-fyi": {
"serverUrl": "https://mcp.levels.fyi/"
}
}
}- Refresh the MCP server list in Cascade.
Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.
Codex
codex mcp add levels-fyi --url https://mcp.levels.fyi/Or edit ~/.codex/config.toml directly:
[mcp_servers.levels-fyi]
url = "https://mcp.levels.fyi/"Gemini CLI
gemini mcp add --transport http levels-fyi https://mcp.levels.fyi/This adds it to the current project. Add -s user to use it everywhere.
Any client
Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI’s settings file.
{
"mcpServers": {
"levels-fyi": {
"type": "http",
"url": "https://mcp.levels.fyi/"
}
}
}Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.
Client only starts local servers? Bridge it with npx -y mcp-remote https://mcp.levels.fyi/.
Embed
Show Levels.fyi in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work
The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.
README badge
[](https://mcp.tc/i/levels-fyi)<a href="https://mcp.tc/i/levels-fyi"><img src="https://mcp.tc/i/levels-fyi/badge.svg" alt="Levels.fyi on mcp.tc" height="20"></a>It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.
Website card
<script src="https://mcp.tc/w/levels-fyi.js" async></script>The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.
iframe
<iframe src="https://mcp.tc/embed/levels-fyi" title="Levels.fyi on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.
JSON
The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).
https://mcp.tc/i/levels-fyi.jsonAI prompt
Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the Levels.fyi card to your site.
Add the mcp.tc card for Levels.fyi, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.
Put this tag where the card should appear. The card renders right before it:
```html
<script src="https://mcp.tc/w/levels-fyi.js" async></script>
```
To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.
```html
<div data-mcptc="levels-fyi"><a href="https://mcp.tc/i/levels-fyi">Levels.fyi on mcp.tc</a></div>
```
Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.
If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).
For a README or other Markdown docs, use the badge instead:
```markdown
[](https://mcp.tc/i/levels-fyi)
```
Reference: https://mcp.tc/embedChange history
We read this server’s tool list every 3 hours and record what changes. Last read 18 Nov 2026, 05:37 UTC.
-
10 tools changed. Server instructions changed.
New server instructions
Details, 16 Nov 2026, 08:52 UTC
Changed 10
add-salary-submissiondescriptionBeforeAdd the user's own compensation to Levels.fyi: pay they earn now or a job offer they received.
Call this onlywhen the useris evaluatingtheircompensation,asks to addtheir pay,or says yes when youoffer. Adding compensation is howthe datastaysuseful for everyone, the user included. Write a complete submission. Resolve the company, job family and focus area to slugs with the search tools first, and the location with search-locations and type "city". Every number must come from the user's own words or from a document the user shared; ask for each required field that is missing. Gather the details conversationally, starting with the company, role and location; do not list every field up front. Split base, yearly stock and bonus as the user stated them; never put a total into baseSalaryValue. Put nothing identifying in otherDetails: no names, managers or team nicknames. Write text fields in English. Call once withconfirm=false and show the preview to the user, then call again wit…AfterAdd the user's own compensation to Levels.fyi: pay they earn now or a job offer they received. Use it when the user has shared their own pay or an offer, asks to add it, or says yes when you offer to add it. A call with confirm=false only returns a preview and adds nothing. Each entry makes the data more useful for everyone, the user included. Write a complete submission. Resolve the company, job family and focus area to slugs with the search tools first, and the location with search-locations and type "city". Every number must come from the user's own words or from a document the user shared; ask for each required field that is missing. Gather the details conversationally, starting with the company, role and location; do not list every field up front. Split base, yearly stock and bonus as the user stated them; never put a total into baseSalaryValue. Put nothing identifying in otherDetails: no names, managers or team nicknames. Write text fields in English. Call once with confirm=fals…
get-available-filtersdescriptionBeforeList which inputs and filter values the free tier can use. The free inputs are jobFamilySlug, a location or country, and a company; every result is total compensation from the last 12 months. Dimensions marked free: false (levels, years of experience, focus areas, titles, company size, funding stage, revenue, valuation, work arrangement, offer vs employee) are
not accepted by any tool here.Call this before building a query if unsure what a tool accepts.AfterList which inputs and filter values the free tier can use. The free inputs are jobFamilySlug, a location or country, and a company; every result is total compensation from the last 12 months. Dimensions marked free: false (levels, years of experience, focus areas, titles, company size, funding stage, revenue, valuation, work arrangement, offer vs employee) are part of the Levels.fyi Benchmark product. Call this before building a query if unsure what a tool accepts.
get-company-levelsdescriptionBeforeGet the INTERNAL level names of up to 5 companies for a job family, each ordered by seniority (e.g. Google L3/L4/L5, Meta E3/E4/E5, Stripe
IC1/IC2/IC3), with any alternate names per level.Pass every company you are comparing in one call. Use this FIRST when a question names a specific level at a specific company (e.g. "what does a Meta E5 make"), then call get-salaries-by-company-level. A company with no known level structure comes back with an empty list and an explanation.Free limit: Full level datafor Amazon,Google,Microsoft,Meta and Apple. Other companies: level names only.Pass canonical slugs (jobFamilySlug, locationSlug(s), countrySlug, companySlug(s)): resolve names first with search-job-families, search-locations and search-companies; never guess a slug. REQUIRED arguments: companySlugs, jobFamilySlug. Array-typed arguments (companySlugs) must be passed as arrays, even for a single value.AfterGet the INTERNAL level names of up to 5 companies for a job family, each ordered by seniority (e.g. Google L3/L4/L5, Meta E3/E4/E5, Stripe IC1/IC2/IC3). Pass every company you are comparing in one call. Use this FIRST when a question names a specific level at a specific company (e.g. "what does a Meta E5 make"), then call get-salaries-by-company-level. A company with no known level structure comes back with an empty list and an explanation. Each level's name and order. Open to everyone for about 40 large tech companies (e.g. Google, Meta, Amazon, Apple, Microsoft, Nvidia, OpenAI, Stripe); other companies are free to view with a Levels.fyi sign-in. Pass canonical slugs (jobFamilySlug, locationSlug(s), countrySlug, companySlug(s)): resolve names first with search-job-families, search-locations and search-companies; never guess a slug. REQUIRED arguments: companySlugs, jobFamilySlug. Array-typed arguments (companySlugs) must be passed as arrays, even for a single value.
get-location-statsdescriptionBeforeGet the top-paying locations for a job family within one country, ranked by median (p50) yearly total compensation in USD from submissions in the last 2 years. Returns up to 10 locations with their median. Use it to compare where a role pays most inside a country. Its window differs from get-salary-percentiles (the last 12 months), so the same location can show a different median: quote get-salary-percentiles for one location's pay.
Free limit: Median (p50) total compensation for the top locations in one country. No company or level filter.Pass canonical slugs (jobFamilySlug, locationSlug(s), countrySlug, companySlug(s)): resolve names first with search-job-families, search-locations and search-companies; never guess a slug. REQUIRED arguments: jobFamilySlug, countrySlug.AfterGet the top-paying locations for a job family within one country, ranked by median (p50) yearly total compensation in USD from submissions in the last 2 years. Returns up to 10 locations with their median. Use it to compare where a role pays most inside a country. Its window differs from get-salary-percentiles (the last 12 months), so the same location can show a different median: quote get-salary-percentiles for one location's pay. Pass canonical slugs (jobFamilySlug, locationSlug(s), countrySlug, companySlug(s)): resolve names first with search-job-families, search-locations and search-companies; never guess a slug. REQUIRED arguments: jobFamilySlug, countrySlug.
get-salaries-by-company-leveldescriptionBeforeGet
median (p50)yearly total compensation in USD for each internal level (e.g. Google L3/L4/L5, Meta E3/E4/E5) of up to 5 companies, for a job family in onelocation, from submissions inthelast 12 months.Pass every company you are comparing in one call. Call get-company-levels first to learn each company's level names. A company must have a known level structure.Free limit: Totalcompensation perlevelfor up to 5 companies per call, in one job family and location.No percentiles or counts.Pass canonical slugs (jobFamilySlug, locationSlug(s), countrySlug, companySlug(s)): resolve names first with search-job-families, search-locations andsearch-companies; never guess a slug. REQUIRED arguments: jobFamilySlug, locationSlug, companySlugs. Array-typed arguments (companySlugs) must be passed as arrays, even for a single value.AfterGet yearly total compensation in USD for each internal level (e.g. Google L3/L4/L5, Meta E3/E4/E5) of up to 5 companies, for a job family in one location: the median and average, the 10th and 90th percentile, and the average base salary, yearly stock and bonus, as the Levels.fyi level pages show them. Pass every company you are comparing in one call. Call get-company-levels first to learn each company's level names. A company must have a known level structure. Median, average, 10th and 90th percentile total compensation per level, with the average base salary, yearly stock and bonus, for up to 5 companies per call, in one job family and location. Open to everyone for about 40 large tech companies (e.g. Google, Meta, Amazon, Apple, Microsoft, Nvidia, OpenAI, Stripe); other companies are free to view with a Levels.fyi sign-in. Pass canonical slugs (jobFamilySlug, locationSlug(s), countrySlug, companySlug(s)): resolve names first with search-job-families, search-locations and search-comp…
get-salary-percentilesdescriptionBeforeGet the median (p50) yearly total compensation in USD for a job family in each of up to 5 locations, across all levels, from submissions in the last 12 months. Pass every location you are comparing in one call. This is the figure to quote for a location's pay; get-location-stats ranks locations over a longer window, so its medians can differ. For one company's pay by level, use get-salaries-by-company-level instead.
Free limit: Median (p50) total compensation for one job family in up to 5 locations per call. No other percentiles, sample size, level split, or company, focus area or funding filters.Pass canonical slugs (jobFamilySlug, locationSlug(s), countrySlug, companySlug(s)): resolve names first with search-job-families, search-locations and search-companies; never guess a slug. REQUIRED arguments: jobFamilySlug, locationSlugs. Array-typed arguments (locationSlugs) must be passed as arrays, even for a single value.AfterGet the median (p50) yearly total compensation in USD for a job family in each of up to 5 locations, across all levels, from submissions in the last 12 months. Pass every location you are comparing in one call. This is the figure to quote for a location's pay; get-location-stats ranks locations over a longer window, so its medians can differ. For one company's pay by level, use get-salaries-by-company-level instead. Pass canonical slugs (jobFamilySlug, locationSlug(s), countrySlug, companySlug(s)): resolve names first with search-job-families, search-locations and search-companies; never guess a slug. REQUIRED arguments: jobFamilySlug, locationSlugs. Array-typed arguments (locationSlugs) must be passed as arrays, even for a single value.
get-salary-submission-by-iddescriptionBeforeGet a single salary submission by its UUID: company, title, level, location, years of experience, offer date, base salary and total compensation. Every amount is in USD; originalCurrency is only the currency the salary was submitted in. Use the uuid from a search-raw-data-points row. Free
limit: Basesalary and totalcompensation only,in USD. REQUIRED arguments: uuid.AfterGet a single salary submission by its UUID: company, title, level, location, years of experience, offer date, base salary and total compensation. Every amount is in USD; originalCurrency is only the currency the salary was submitted in. Use the uuid from a search-raw-data-points row. Free with a Levels.fyi sign-in: base salary and total compensation, in USD. REQUIRED arguments: uuid.
search-jobsdescriptionBeforeSearch open jobs on Levels.fyi, with the pay range each posting states. Returns { jobs, totalMatchingJobs, nextOffset }; each job has its title, company, locations, work arrangement, posting date, pay range, url (the Levels.fyi job page) and applyUrl. Simplify the user's request to role names and terms that appear in job posts. Pass at most one location per call, and only one the user named: resolve it with
search-locations, and never usetheuser's own position.Resolve companies and job families with search-companies and search-job-families. If nothing matches, widen the search (drop a filter or simplify the query) and try once more; if there's still nothing, say so rather than listing unrelated jobs. When the user asks for jobs without saying which role, offer to search from their Levels.fyi profile. If they agree, call get-profile and draft the query from its title, job family and location (locationSlug). Before searching, show theuser the values you will use and ask them to conf…AfterSearch open jobs on Levels.fyi, with the pay range each posting states. Returns { jobs, totalMatchingJobs, nextOffset }; each job has its title, company, locations, work arrangement, posting date, pay range, url (the Levels.fyi job page) and applyUrl. Simplify the user's request to role names and terms that appear in job posts. Pass at most one location per call, and only one the user named: resolve it with search-locations. Use a location only when the user names one; don't infer it from where the user is. Resolve companies and job families with search-companies and search-job-families. If nothing matches, widen the search (drop a filter or simplify the query) and try once more; if there's still nothing, say so rather than listing unrelated jobs. When the user asks for jobs without saying which role, offer to search from their Levels.fyi profile. If they agree, call get-profile and draft the query from its title, job family and location (locationSlug). Before searching, show the user…
search-raw-data-pointsdescriptionBeforeGet the newest individual salary submissions for a job family, optionally narrowed to one location and/or one company. Each row has the company, title, level, location, years of experience, base salary and total compensation. Every amount is in USD; originalCurrency is only the currency the salary was submitted in. Returns { total, rows }; total counts matches up to 250, and only the newest rows are returned. Free
limit: The3 newest submissions, with base salary and totalcompensation only. No text search, level, years-of-experience, sort or paging.Pass canonical slugs (jobFamilySlug, locationSlug(s), countrySlug, companySlug(s)): resolve names first with search-job-families, search-locations and search-companies; never guess a slug. REQUIRED arguments: jobFamilySlug.AfterGet the newest individual salary submissions for a job family, optionally narrowed to one location and/or one company. Each row has the company, title, level, location, years of experience, base salary and total compensation. Every amount is in USD; originalCurrency is only the currency the salary was submitted in. Returns { total, rows }; total counts matches up to 250, and only the newest rows are returned. Free with a Levels.fyi sign-in: the 3 newest submissions, with base salary and total compensation. Pass canonical slugs (jobFamilySlug, locationSlug(s), countrySlug, companySlug(s)): resolve names first with search-job-families, search-locations and search-companies; never guess a slug. REQUIRED arguments: jobFamilySlug.
search-top-companiesdescriptionBeforeGet the top-paying companies for a job family within one country, ranked by median (p50) yearly total compensation in USD. Returns up to 10 companies with their median. Companies with too few submissions are left out.
Free limit: Median (p50) total compensation for the top companies in one country. No sample size, level or years-of-experience filter.Pass canonical slugs (jobFamilySlug, locationSlug(s), countrySlug, companySlug(s)): resolve names first with search-job-families, search-locations and search-companies; never guess a slug. REQUIRED arguments: jobFamilySlug, countrySlug.AfterGet the top-paying companies for a job family within one country, ranked by median (p50) yearly total compensation in USD. Returns up to 10 companies with their median. Companies with too few submissions are left out. Pass canonical slugs (jobFamilySlug, locationSlug(s), countrySlug, companySlug(s)): resolve names first with search-job-families, search-locations and search-companies; never guess a slug. REQUIRED arguments: jobFamilySlug, countrySlug.
Server instructions
BeforeThis server exposes Levels.fyi compensation data on the free tier. All compensation amounts are in USD. Levels.fyi covers 5,000+ companies, with historical data available for up to 5+ years. Inputs are CANONICAL SLUGS, never free text. Resolve names first, then pass the returned slugs: - companies → search-companies / get-company - locations → search-locations / get-location - job families → search-job-families / get-job-family - a company's own level names → get-company-levels The tools that resolve a name (search-companies, search-locations, search-job-families, search-job-titles, search-focus-areas, search-role-terms and search-all) take it as searchText; search-jobs takes query. get-company-levels and every pay tool also need a jobFamilySlug. Read a tool's input schema before the first call to it. Each data tool takes one job family and, where asked, one location or country. get-salary-percentiles takes up to 5 locations, and get-company-levels and get-salaries-by-company-level up to 5 companies: pass everything you are comparing in one call. There is no level, years-of-experience, focus area or title filter: do not present a result as level- or title-specific unless it comes from get-salaries-by-company-level, which is per company level. For "what does a Meta E5 make", call get-company-levels for the company's real level names, then get-salaries-by-company-level. Data tools end their result with an explanation (where the data comes from) and nextSteps (follow-ups the user might want). Use the explanation when saying where a figure comes from, and offer nextSteps as options; don't run them unasked. Most people who look up pay want to know whether their own pay is fair. When the user asks what a role, level or company pays, asks about pay for a job they hold or an offer they have, or is looking for a job, and hasn't shared their own pay, offer a pay check after answering, in this form: "I can also check whether you're paid fairly for your level and locatio…
AfterThis server exposes Levels.fyi compensation data on the free tier. All compensation amounts are in USD. Levels.fyi covers 5,000+ companies, with historical data available for up to 5+ years. Inputs are CANONICAL SLUGS, never free text. Resolve names first, then pass the returned slugs: - companies → search-companies / get-company - locations → search-locations / get-location - job families → search-job-families / get-job-family - a company's own level names → get-company-levels The tools that resolve a name (search-companies, search-locations, search-job-families, search-job-titles, search-focus-areas, search-role-terms and search-all) take it as searchText; search-jobs takes query. get-company-levels and every pay tool also need a jobFamilySlug. Read a tool's input schema before the first call to it. Each data tool takes one job family and, where asked, one location or country. get-salary-percentiles takes up to 5 locations, and get-company-levels and get-salaries-by-company-level up to 5 companies: pass everything you are comparing in one call. Level-specific figures come from get-salaries-by-company-level, per company level. The other pay tools cover all levels, years of experience and titles together. For "what does a Meta E5 make", call get-company-levels for the company's real level names, then get-salaries-by-company-level. Data tools end their result with an explanation (where the data comes from) and nextSteps (follow-ups the user might want). Use the explanation when saying where a figure comes from, and offer nextSteps as options; don't run them unasked. Most people who look up pay want to know whether their own pay is fair. When the user asks what a role, level or company pays, asks about pay for a job they hold or an offer they have, or is looking for a job, and hasn't shared their own pay, offer a pay check after answering, in this form: "I can also check whether you're paid fairly for your level and location. What do you make today?" Don't offe…
-
3 tools changed. Server instructions changed.
New server instructions
Details, 13 Nov 2026, 08:53 UTC
Changed 3
add-salary-submissiondescription and input schemaBeforeAdd the user's own compensation to Levels.fyi: pay they earn now or a job offer they received. Call this only when the user is evaluating their compensation, asks to add their pay, or says yes when you offer. Adding compensation is how the data stays useful for everyone, the user included. Write a complete submission. Resolve the company, job family and focus area to slugs with the search tools first, and the location with search-locations and type "city". Every number must come from the user's own words or from a document the user shared; ask for each required field that is missing. Gather the details conversationally,
a question or two at a time,starting with the company, role and location; do not list every field up front. Write text fields in English. Call once with confirm=false and show the preview to the user, then call againwith the same arguments and confirm=true only after a clear yes. If the user isn't signed in, ask for their email before the confirm=true call and send i…AfterAdd the user's own compensation to Levels.fyi: pay they earn now or a job offer they received. Call this only when the user is evaluating their compensation, asks to add their pay, or says yes when you offer. Adding compensation is how the data stays useful for everyone, the user included. Write a complete submission. Resolve the company, job family and focus area to slugs with the search tools first, and the location with search-locations and type "city". Every number must come from the user's own words or from a document the user shared; ask for each required field that is missing. Gather the details conversationally, starting with the company, role and location; do not list every field up front. Split base, yearly stock and bonus as the user stated them; never put a total into baseSalaryValue. Put nothing identifying in otherDetails: no names, managers or team nicknames. Write text fields in English. Call once with confirm=false and show the preview to the user, then call again wit…
- Description of
yearsOfExperienceBeforeTotal years of professional
experience.AfterTotal years of professional experience, in whole years; a decimal is rounded.
- Description of
confirmBeforefalse (default) returns a preview and
writes nothing.truewritesthe entry: only after the user said yes to the preview.Afterfalse (default) returns a preview and adds nothing to Levels.fyi. true adds the entry: only after the user said yes to the preview.
- Description of
search-jobsdescriptionThe text shown here is the same before and after: the change is past the first 1,000 characters or in characters that don’t show.
upload-resumedescriptionBeforeAdd or replace the signed-in user's resume on Levels.fyi. When the user shares their resume or asks for help with a job search, you can offer this once; call it only after the user asks or agrees. Before you call, tell the user Levels.fyi uses it to fill in their profile and match them with jobs and recruiters. Never upload a resume for another person. Accepts a PDF (at most 5 pages) or a DOCX, at most 4.5 MB. Set fileType from the file's actual extension: the upload must be a file of that format, or it cannot be read. Returns two ways to upload: - upload: a presigned S3 upload that expires in 10 minutes. Use it only if you can read the user's file and make HTTP requests yourself, e.g. a terminal agent with the file on disk: send an HTTP POST with multipart/form-data to upload.url, with every entry of upload.fields as form fields, followed by the file in a field named "file". A 201 response means it worked; a larger file is refused. - webUploadUrl: otherwise, give the user this link t…
AfterAdd or replace the signed-in user's resume on Levels.fyi. Offer it when the user shares a resume or asks for help with a job search; call it only after they agree. Before you call, tell the user Levels.fyi reads it to fill their profile; the result's disclosure has the details. Never upload a resume for another person. Accepts a PDF (at most 5 pages) or a DOCX, at most 4.5 MB. Set fileType from the file's actual extension: the upload must be a file of that format, or it cannot be read. Returns up to two ways to upload (a hosted client such as Claude.ai or ChatGPT gets webUploadUrl only): - upload: a presigned S3 upload that expires in 10 minutes. Use it only if you can read the user's file and make HTTP requests yourself, e.g. a terminal agent with the file on disk: send an HTTP POST with multipart/form-data to upload.url, with every entry of upload.fields as form fields, followed by the file in a field named "file". A 201 response means it worked; a larger file is refused. - webUploa…
Server instructions
BeforeThis server exposes Levels.fyi compensation data on the free tier. All compensation amounts are in USD. Levels.fyi covers 5,000+ companies, with historical data available for up to 5+ years. Inputs are CANONICAL SLUGS, never free text. Resolve names first, then pass the returned slugs: - companies → search-companies / get-company - locations → search-locations / get-location - job families → search-job-families / get-job-family - a company's own level names → get-company-levels The tools that resolve a name (search-companies, search-locations, search-job-families, search-job-titles, search-focus-areas, search-role-terms and search-all) take it as searchText; search-jobs takes query. get-company-levels and every pay tool also need a jobFamilySlug. Read a tool's input schema before the first call to it. Each data tool takes one job family and, where asked, one location or country. get-salary-percentiles takes up to 5 locations, and get-company-levels and get-salaries-by-company-level up to 5 companies: pass everything you are comparing in one call. There is no level, years-of-experience, focus area or title filter: do not present a result as level- or title-specific unless it comes from get-salaries-by-company-level, which is per company level. For "what does a Meta E5 make", call get-company-levels for the company's real level names, then get-salaries-by-company-level. Data tools end their result with an explanation (where the data comes from) and nextSteps (follow-ups the user might want). Use the explanation when saying where a figure comes from, and offer nextSteps as options; don't run them unasked. Most people who look up pay want to know whether their own pay is fair. When the user asks what a role, level or company pays, asks about pay for a job they hold or an offer they have, or is looking for a job, and hasn't shared their own pay, offer a pay check once per conversation, after answering, in this form: "I can also check whether you're paid fairly for…
AfterThis server exposes Levels.fyi compensation data on the free tier. All compensation amounts are in USD. Levels.fyi covers 5,000+ companies, with historical data available for up to 5+ years. Inputs are CANONICAL SLUGS, never free text. Resolve names first, then pass the returned slugs: - companies → search-companies / get-company - locations → search-locations / get-location - job families → search-job-families / get-job-family - a company's own level names → get-company-levels The tools that resolve a name (search-companies, search-locations, search-job-families, search-job-titles, search-focus-areas, search-role-terms and search-all) take it as searchText; search-jobs takes query. get-company-levels and every pay tool also need a jobFamilySlug. Read a tool's input schema before the first call to it. Each data tool takes one job family and, where asked, one location or country. get-salary-percentiles takes up to 5 locations, and get-company-levels and get-salaries-by-company-level up to 5 companies: pass everything you are comparing in one call. There is no level, years-of-experience, focus area or title filter: do not present a result as level- or title-specific unless it comes from get-salaries-by-company-level, which is per company level. For "what does a Meta E5 make", call get-company-levels for the company's real level names, then get-salaries-by-company-level. Data tools end their result with an explanation (where the data comes from) and nextSteps (follow-ups the user might want). Use the explanation when saying where a figure comes from, and offer nextSteps as options; don't run them unasked. Most people who look up pay want to know whether their own pay is fair. When the user asks what a role, level or company pays, asks about pay for a job they hold or an offer they have, or is looking for a job, and hasn't shared their own pay, offer a pay check after answering, in this form: "I can also check whether you're paid fairly for your level and locatio…
-
Server instructions changed.
New server instructions
Details, 13 Nov 2026, 05:51 UTC
Server instructions
BeforeThis server exposes Levels.fyi compensation data on the free tier. All compensation amounts are in USD. Levels.fyi covers 5,000+ companies, with historical data available for up to 5+ years. Inputs are CANONICAL SLUGS, never free text. Resolve names first, then pass the returned slugs: - companies → search-companies / get-company - locations → search-locations / get-location - job families → search-job-families / get-job-family - a company's own level names → get-company-levels Each data tool takes one job family and, where asked, one location or country. get-salary-percentiles takes up to 5 locations, and get-company-levels and get-salaries-by-company-level up to 5 companies: pass everything you are comparing in one call. There is no level, years-of-experience, focus area or title filter: do not present a result as level- or title-specific unless it comes from get-salaries-by-company-level, which is per company level. For "what does a Meta E5 make", call get-company-levels for the company's real level names, then get-salaries-by-company-level. Data tools end their result with an explanation (where the data comes from) and nextSteps (follow-ups the user might want). Use the explanation when saying where a figure comes from, and offer nextSteps as options; don't run them unasked. Most people who look up pay want to know whether their own pay is fair. When the user asks what a role, level or company pays, asks about pay for a job they hold or an offer they have, or is looking for a job, and hasn't shared their own pay, offer a pay check once per conversation, after answering, in this form: "I can also check whether you're paid fairly for your level and location. What do you make today?" Don't offer it to an employer (a recruiter, or a compensation or HR team), and don't offer it again after a no. When the user answers, ask for what a like-for-like comparison needs, a question or two at a time, skipping anything they already said: company, job title, level, locat…
AfterThis server exposes Levels.fyi compensation data on the free tier. All compensation amounts are in USD. Levels.fyi covers 5,000+ companies, with historical data available for up to 5+ years. Inputs are CANONICAL SLUGS, never free text. Resolve names first, then pass the returned slugs: - companies → search-companies / get-company - locations → search-locations / get-location - job families → search-job-families / get-job-family - a company's own level names → get-company-levels The tools that resolve a name (search-companies, search-locations, search-job-families, search-job-titles, search-focus-areas, search-role-terms and search-all) take it as searchText; search-jobs takes query. get-company-levels and every pay tool also need a jobFamilySlug. Read a tool's input schema before the first call to it. Each data tool takes one job family and, where asked, one location or country. get-salary-percentiles takes up to 5 locations, and get-company-levels and get-salaries-by-company-level up to 5 companies: pass everything you are comparing in one call. There is no level, years-of-experience, focus area or title filter: do not present a result as level- or title-specific unless it comes from get-salaries-by-company-level, which is per company level. For "what does a Meta E5 make", call get-company-levels for the company's real level names, then get-salaries-by-company-level. Data tools end their result with an explanation (where the data comes from) and nextSteps (follow-ups the user might want). Use the explanation when saying where a figure comes from, and offer nextSteps as options; don't run them unasked. Most people who look up pay want to know whether their own pay is fair. When the user asks what a role, level or company pays, asks about pay for a job they hold or an offer they have, or is looking for a job, and hasn't shared their own pay, offer a pay check once per conversation, after answering, in this form: "I can also check whether you're paid fairly for…
-
1 tool changed. Server instructions changed.
New server instructions
Details, 10 Nov 2026, 14:48 UTC
Changed 1
get-profiledescriptionBeforeGet the signed-in user's own Levels.fyi career profile: current title, company, career level, job family, focus area, location, years of experience, skills, certifications and work history, plus the status of their resume (none, pending while it is being parsed, parsed, or failed) and when it was uploaded. Never returns contact details or the resume file.
Useitto personalize answersaboutthe user'sownpay, levelorcareer.AfterGet the signed-in user's own Levels.fyi career profile: current title, company, career level, job family, focus area, location, years of experience, skills, certifications and work history, plus the status of their resume (none, pending while it is being parsed, parsed, or failed) and when it was uploaded. Never returns contact details or the resume file. Needs a Levels.fyi sign-in: call it only when the user asks about their own profile or asks you to use it. For a pay check, ask the user instead.
Server instructions
BeforeThis server exposes Levels.fyi compensation data on the free tier. All compensation amounts are in USD. Levels.fyi covers 5,000+ companies, with historical data available for up to 5+ years. Inputs are CANONICAL SLUGS, never free text. Resolve names first, then pass the returned slugs: - companies → search-companies / get-company - locations → search-locations / get-location - job families → search-job-families / get-job-family - a company's own level names → get-company-levels Each data tool takes one job family and, where asked, one location or country. get-salary-percentiles takes up to 5 locations, and get-company-levels and get-salaries-by-company-level up to 5 companies: pass everything you are comparing in one call. There is no level, years-of-experience, focus area or title filter: do not present a result as level- or title-specific unless it comes from get-salaries-by-company-level, which is per company level. For "what does a Meta E5 make", call get-company-levels for the company's real level names, then get-salaries-by-company-level. Data tools end their result with an explanation (where the data comes from) and nextSteps (follow-ups the user might want). Use the explanation when saying where a figure comes from, and offer nextSteps as options; don't run them unasked. Most people who look up pay want to know whether their own pay is fair. When the user asks about pay for a job they hold, an offer they have, or a company or role they might join, or is looking for a job, and hasn't shared their own pay, offer a pay check once per conversation, after answering, in this form: "I can also check whether you're paid fairly for your level and location. What do you make today?" Don't offer it to an employer (a recruiter, or a compensation or HR team), and don't offer it again after a no. When the user answers, ask for what a like-for-like comparison needs, a question or two at a time, skipping anything they already said: company, job title, level, location,…
AfterThis server exposes Levels.fyi compensation data on the free tier. All compensation amounts are in USD. Levels.fyi covers 5,000+ companies, with historical data available for up to 5+ years. Inputs are CANONICAL SLUGS, never free text. Resolve names first, then pass the returned slugs: - companies → search-companies / get-company - locations → search-locations / get-location - job families → search-job-families / get-job-family - a company's own level names → get-company-levels Each data tool takes one job family and, where asked, one location or country. get-salary-percentiles takes up to 5 locations, and get-company-levels and get-salaries-by-company-level up to 5 companies: pass everything you are comparing in one call. There is no level, years-of-experience, focus area or title filter: do not present a result as level- or title-specific unless it comes from get-salaries-by-company-level, which is per company level. For "what does a Meta E5 make", call get-company-levels for the company's real level names, then get-salaries-by-company-level. Data tools end their result with an explanation (where the data comes from) and nextSteps (follow-ups the user might want). Use the explanation when saying where a figure comes from, and offer nextSteps as options; don't run them unasked. Most people who look up pay want to know whether their own pay is fair. When the user asks what a role, level or company pays, asks about pay for a job they hold or an offer they have, or is looking for a job, and hasn't shared their own pay, offer a pay check once per conversation, after answering, in this form: "I can also check whether you're paid fairly for your level and location. What do you make today?" Don't offer it to an employer (a recruiter, or a compensation or HR team), and don't offer it again after a no. When the user answers, ask for what a like-for-like comparison needs, a question or two at a time, skipping anything they already said: company, job title, level, locat…
-
3 tools changed.
Details, 6 Nov 2026, 11:44 UTC
Changed 3
get-salaries-by-company-levelinput schema- Description of
locationSlugBeforeOne location slug
(metro,country or region; not astate or city),e.g. "san-francisco-bay-area". Resolve it with search-locations first; for acity,use itsparent metro, and for a state, its metro…AfterOne location slug (city, metro, country or region; not a state), e.g. "san-francisco-bay-area". Resolve it with search-locations first; for a state, use its metro or country.
- Description of
get-salary-percentilesinput schema- Description of
locationSlugsBeforeUp to 5 location slugs
(metro,country or region; not astate or city),compared in one call. Resolve each with search-locations first; for acity,use itsparent metro, and for a state, itsmetroor…AfterUp to 5 location slugs (city, metro, country or region; not a state), compared in one call. Resolve each with search-locations first; for a state, use its metro or country.
- Description of
search-locationsdescriptionBeforeSearch locations (countries, metro areas / DMAs, US states and cities) using searchText input (required) and get their Levels.fyi slugs. Use this to resolve a location name (e.g. "San Francisco", "United States") into the slug the benchmark tools require in their locationSlugs filter. Each result includes its location type. Optionally restrict to one type. Results can include cities; a city's parent location (a metro, or the country where there is
none) is the slug to pass to the pay tools.Search by place name alone: "Cambridge", not "Cambridge, MA". Several places can share a name: pick the one the user means from context, and ask if unsure. If this returns no matches, fall back to search-all, which searches every entity type and applies a fuzzy fallback. REQUIRED arguments: searchText.AfterSearch locations (countries, metro areas / DMAs, US states and cities) using searchText input (required) and get their Levels.fyi slugs. Use this to resolve a location name (e.g. "San Francisco", "United States") into the slug the benchmark tools require in their locationSlugs filter. Each result includes its location type. Optionally restrict to one type. Results can include cities; pass a city's own slug to the pay tools. When a tool says a city has too little data, pass its parent location instead (a metro, or the country where there is none). Search by place name alone: "Cambridge", not "Cambridge, MA". Several places can share a name: pick the one the user means from context, and ask if unsure. If this returns no matches, fall back to search-all, which searches every entity type and applies a fuzzy fallback. REQUIRED arguments: searchText.
-
Server instructions changed.
New server instructions
Details, 6 Nov 2026, 08:43 UTC
Server instructions
BeforeThis server exposes Levels.fyi compensation data on the free tier. All compensation amounts are in USD. Levels.fyi covers 5,000+ companies, with historical data available for up to 5+ years. Inputs are CANONICAL SLUGS, never free text. Resolve names first, then pass the returned slugs: - companies → search-companies / get-company - locations → search-locations / get-location - job families → search-job-families / get-job-family - a company's own level names → get-company-levels Each data tool takes one job family and, where asked, one location or country. get-salary-percentiles takes up to 5 locations, and get-company-levels and get-salaries-by-company-level up to 5 companies: pass everything you are comparing in one call. There is no level, years-of-experience, focus area or title filter: do not present a result as level- or title-specific unless it comes from get-salaries-by-company-level, which is per company level. For "what does a Meta E5 make", call get-company-levels for the company's real level names, then get-salaries-by-company-level. Data tools end their result with an explanation (where the data comes from) and nextSteps (follow-ups the user might want). Use the explanation when saying where a figure comes from, and offer nextSteps as options; don't run them unasked. Levels.fyi data exists only because people share their own pay. When the user has shared their own salary or an offer, ask once per conversation, after answering, in this form: "These numbers came from people sharing their own pay. Want to add this offer for the next person, without your name?" Say "your pay" instead of "this offer" when they shared their current pay. Don't ask during a plain lookup about other people's pay, and don't ask again after a no. Label where every figure comes from. A number a Levels.fyi tool returned is "Levels.fyi data": say which job family, location and window it covers. A number from anywhere else, such as a web search, your general knowledge or an assum…
AfterThis server exposes Levels.fyi compensation data on the free tier. All compensation amounts are in USD. Levels.fyi covers 5,000+ companies, with historical data available for up to 5+ years. Inputs are CANONICAL SLUGS, never free text. Resolve names first, then pass the returned slugs: - companies → search-companies / get-company - locations → search-locations / get-location - job families → search-job-families / get-job-family - a company's own level names → get-company-levels Each data tool takes one job family and, where asked, one location or country. get-salary-percentiles takes up to 5 locations, and get-company-levels and get-salaries-by-company-level up to 5 companies: pass everything you are comparing in one call. There is no level, years-of-experience, focus area or title filter: do not present a result as level- or title-specific unless it comes from get-salaries-by-company-level, which is per company level. For "what does a Meta E5 make", call get-company-levels for the company's real level names, then get-salaries-by-company-level. Data tools end their result with an explanation (where the data comes from) and nextSteps (follow-ups the user might want). Use the explanation when saying where a figure comes from, and offer nextSteps as options; don't run them unasked. Most people who look up pay want to know whether their own pay is fair. When the user asks about pay for a job they hold, an offer they have, or a company or role they might join, or is looking for a job, and hasn't shared their own pay, offer a pay check once per conversation, after answering, in this form: "I can also check whether you're paid fairly for your level and location. What do you make today?" Don't offer it to an employer (a recruiter, or a compensation or HR team), and don't offer it again after a no. When the user answers, ask for what a like-for-like comparison needs, a question or two at a time, skipping anything they already said: company, job title, level, location,…
-
11 tools changed. Server instructions changed.
Newly required parameter, New server instructions
Details, 4 Nov 2026, 11:44 UTC
Changed 11
add-salary-submissiondescription and input schemaThe text shown here is the same before and after: the change is past the first 1,000 characters or in characters that don’t show.
- Removed parameters:
submissionId
- Removed parameters:
get-available-filtersdescriptionBeforeList which inputs and filter values the free tier can use. The free inputs are jobFamilySlug, one locationSlug or countrySlug, and companySlug; every result is total compensation from the last 12 months. Dimensions marked free: false (levels, years of experience, focus areas, titles, company size, funding stage, revenue, valuation, work arrangement, offer vs employee) are not accepted by any tool here. Call this before building a query if unsure what a tool accepts.
AfterList which inputs and filter values the free tier can use. The free inputs are jobFamilySlug, a location or country, and a company; every result is total compensation from the last 12 months. Dimensions marked free: false (levels, years of experience, focus areas, titles, company size, funding stage, revenue, valuation, work arrangement, offer vs employee) are not accepted by any tool here. Call this before building a query if unsure what a tool accepts.
get-company-levelsdescription and input schemaBeforeGet a company's INTERNAL level names for a job family, ordered by seniority (e.g. Google L3/L4/L5, Meta E3/E4/E5, Stripe IC1/IC2/IC3), with any alternate names per level. Use this FIRST when a question names a specific level at a specific company (e.g. "what does a Meta E5 make"), then call get-salaries-by-company-level. Returns an empty list with an explanation when the company has no known level structure. Free limit: Full level data for Amazon, Google, Microsoft, Meta and Apple. Other companies: level names only. Pass canonical slugs (jobFamilySlug, locationSlug, countrySlug, companySlug): resolve names first with search-job-families, search-locations and search-companies; never guess a slug. REQUIRED arguments: companySlug, jobFamilySlug.
AfterGet the INTERNAL level names of up to 5 companies for a job family, each ordered by seniority (e.g. Google L3/L4/L5, Meta E3/E4/E5, Stripe IC1/IC2/IC3), with any alternate names per level. Pass every company you are comparing in one call. Use this FIRST when a question names a specific level at a specific company (e.g. "what does a Meta E5 make"), then call get-salaries-by-company-level. A company with no known level structure comes back with an empty list and an explanation. Free limit: Full level data for Amazon, Google, Microsoft, Meta and Apple. Other companies: level names only. Pass canonical slugs (jobFamilySlug, locationSlug(s), countrySlug, companySlug(s)): resolve names first with search-job-families, search-locations and search-companies; never guess a slug. REQUIRED arguments: companySlugs, jobFamilySlug. Array-typed arguments (companySlugs) must be passed as arrays, even for a single value.
- New parameters:
companySlugs - Removed parameters:
companySlug - Now required:
companySlugs - No longer required:
companySlug
- New parameters:
get-location-statsdescriptionBeforeGet the top-paying locations for a job family within one country, ranked by median (p50) yearly total compensation in USD from submissions in the last 2 years. Returns up to 10 locations with their median. Use it to compare where a role pays most inside a country. Its window differs from get-salary-percentiles (the last 12 months), so the same location can show a different median: quote get-salary-percentiles for one location's pay. Free limit: Median (p50) total compensation for the top locations in one country. No company or level filter. Pass canonical slugs (jobFamilySlug, locationSlug, countrySlug, companySlug): resolve names first with search-job-families, search-locations and search-companies; never guess a slug. REQUIRED arguments: jobFamilySlug, countrySlug.
AfterGet the top-paying locations for a job family within one country, ranked by median (p50) yearly total compensation in USD from submissions in the last 2 years. Returns up to 10 locations with their median. Use it to compare where a role pays most inside a country. Its window differs from get-salary-percentiles (the last 12 months), so the same location can show a different median: quote get-salary-percentiles for one location's pay. Free limit: Median (p50) total compensation for the top locations in one country. No company or level filter. Pass canonical slugs (jobFamilySlug, locationSlug(s), countrySlug, companySlug(s)): resolve names first with search-job-families, search-locations and search-companies; never guess a slug. REQUIRED arguments: jobFamilySlug, countrySlug.
get-salaries-by-company-leveldescription and input schemaBeforeGet median (p50) yearly total compensation in USD for each of ONE company's internal levels (e.g. Google L3/L4/L5, Meta E3/E4/E5) for a job family in one location, from submissions in the last 12 months. Call get-company-levels first to learn the company's level names. The company must have a known level structure. Free limit: Total compensation per level for one company and job family. No percentiles or counts. Pass canonical slugs (jobFamilySlug, locationSlug, countrySlug, companySlug): resolve names first with search-job-families, search-locations and search-companies; never guess a slug. REQUIRED arguments: jobFamilySlug, locationSlug, companySlug.
AfterGet median (p50) yearly total compensation in USD for each internal level (e.g. Google L3/L4/L5, Meta E3/E4/E5) of up to 5 companies, for a job family in one location, from submissions in the last 12 months. Pass every company you are comparing in one call. Call get-company-levels first to learn each company's level names. A company must have a known level structure. Free limit: Total compensation per level for up to 5 companies per call, in one job family and location. No percentiles or counts. Pass canonical slugs (jobFamilySlug, locationSlug(s), countrySlug, companySlug(s)): resolve names first with search-job-families, search-locations and search-companies; never guess a slug. REQUIRED arguments: jobFamilySlug, locationSlug, companySlugs. Array-typed arguments (companySlugs) must be passed as arrays, even for a single value.
- New parameters:
companySlugs - Removed parameters:
companySlug - Now required:
companySlugs - No longer required:
companySlug - Description of
locationSlugBeforeOne location slug (metro,
state,country or region; not a city), e.g. "san-francisco-bay-area". Resolve it with search-locations first; for a city, use its parentmetro.AfterOne location slug (metro, country or region; not a state or city), e.g. "san-francisco-bay-area". Resolve it with search-locations first; for a city, use its parent metro, and for a state, its metro…
- New parameters:
get-salary-percentilesget-vesting-schedulessearch-jobssearch-locationssearch-raw-data-pointssearch-top-companiesServer instructions
Part of this entry is left out to keep the page short.
-
Server instructions changed.
New server instructions
Details, 3 Nov 2026, 08:51 UTC
Server instructions
Part of this entry is left out to keep the page short.
-
1 tool changed. Server instructions changed.
New server instructions
Details, 30 Oct 2026, 17:47 UTC
Changed 1
upload-resumeServer instructions
Part of this entry is left out to keep the page short.
-
Tracking started: 30 tools.
FAQ
Can I paste mcp.tc/i/levels-fyi into my MCP client?
No. mcp.tc links are pages, not server addresses. Connect with https://mcp.levels.fyi/, so your client talks to Levels.fyi directly. The quick link is for sharing: it opens this page, with setup steps for every client.
Does Levels.fyi need an API key or a sign-in?
No. Levels.fyi doesn’t ask for an account or key.
Is Levels.fyi a remote or a local server?
Remote. Levels.fyi hosts it at https://mcp.levels.fyi/, and it speaks Streamable HTTP. There’s nothing to install.
What can Levels.fyi do?
It has 30 tools, including get-permissions, get-salary-percentiles and get-salaries-by-company-level. You can resolve company, location and job family names to slugs, get median total compensation for a job family in a location and get pay by internal company level, such as Meta E5.
Which clients can use it?
Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.
Does mcp.tc track changes to Levels.fyi?
Yes. Levels.fyi’s History tab shows each change we find to its tools, down to descriptions and parameters, plus new versions and edits by its owner. Follow the listing to get an email when it changes.
Who wrote this page?
mcp.tc’s robot read Levels.fyi’s own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.
mcp.tc isn’t affiliated with Levels.fyi. This page was built from Levels.fyi’s public metadata, last checked on 17 Nov 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.