Levels.fyi
Server Details
Salary, level and job data from 1M+ pay reports. Benchmark pay, evaluate offers, search open jobs.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- Levels-fyi/levels-fyi-plugin
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- Levels.fyi
TDQS
Scored across 30 tools
The pay-comparison tools (get-salary-percentiles, get-location-stats, search-top-companies, get-salaries-by-company-level) overlap heavily but their descriptions explicitly cross-reference when to use which, which rescues them. The bigger problem is the search family: search-all, search-role-terms, and the four type-specific searchers plus search-companies-by-vesting all answer 'resolve this name', and an agent must read several paragraphs to pick correctly. Descriptions help, but boundaries are fuzzy.
Every tool follows a consistent verb_noun kebab-case pattern: get-*, search-*, add-*, send-*, upload-*. Compound names like get-salaries-by-company-level and search-companies-by-vesting extend the same pattern predictably rather than breaking it.
At 30 tools this is on the heavy side for one server, spanning pay benchmarks, entity resolution, job search, submissions, profile/resume, and meta utilities. Most tools earn their place, but the seven-plus search/resolution tools and four pay-comparison tools suggest consolidation was possible. The breadth is defensible but unwieldy.
Coverage is broad and coherent: entity resolution, benchmark data by location/company/level, vesting, job postings, submission creation, profile, resume upload, feedback, and self-describing meta tools. Minor gaps exist — no way to view, edit, or delete a user's own past submissions, and no lifecycle tools around saved jobs or alerts. These are workarounds, not blockers.
Publisher details
- Operator
- Levels.fyi · Publisher source
- Operator website
- https://www.Levels.fyi · Publisher source
- Vendor relationship
- First-party
- Documentation
- Not available
- Privacy policy
- https://www.levels.fyi/about/privacy.html · Publisher source
- Trust center
- Not available
- Restrictions
- Not available
Available Tools
30 toolsadd-salary-submissionAInspect
Add 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=false and show the preview to the user, then call again with 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 it in email; signing in isn't needed. Amounts are in the submission's own currency. Stock options go in the option fields (totalOptionsGranted for an offer, avgAnnualOptionsGranted for current pay, with the strike and preferred price), not in otherDetails; option prices may use optionPriceCurrency. If the user wants enhanced anonymity, set anonymise=true; the preview shows it.
Do not submit: pay for another person, a number you estimated or took from Levels.fyi data, a range from a job posting, a hypothetical or negotiation target, or a test entry.
One submission per distinct job or offer per conversation, and at most 5 confirmed submissions per 60s. Never repeat a confirmed submission. A submission is reviewed before it counts in the data. Nobody replies here, and submitting does not end your turn: keep working on the user's task. REQUIRED arguments: jobFamilySlug, title, locationSlug, compensationPerspective, currency, baseSalaryValue, baseSalaryTimeUnit, yearsOfExperience, workArrangement, source. Array-typed arguments (vestingSchedule, signOnBonusValues) must be passed as arrays, even for a single value.
Inputs: title (required), source (required), currency (required), locationSlug (required), +31 more.
get-available-filtersARead-onlyInspect
List 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.
Inputs: no named parameters.
get-companyARead-onlyInspect
Look up a single company by its slug (preferred) or name, returning its full profile: name, slug, employee count, headquarters, founding year, ticker, company type, and estimated valuation. Use search-companies first if you only have a name and need the exact slug. REQUIRED arguments: companyNameOrSlug.
Inputs: companyNameOrSlug (required).
get-company-groupARead-onlyInspect
Resolve a named company group (e.g. "FAANG", "AI", "Fintech") into its list of company slugs, for use in the benchmark tools' companySlugs filter. Matching is case- and separator-insensitive. Omit "group" (or pass an unknown one) to get the list of available group names. Available groups: FAANG, AUTOMOTIVE, SPACE, SOCIAL_MEDIA, AI, AI_PLUS, FINTECH, FAANG_PLUS, HEDGE_FUNDS, SEMICONDUCTOR, BIOTECH, WEB3, TRADING_FIRMS, DEFENSE.
Inputs: group.
get-company-levelsARead-onlyInspect
Get 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.
Inputs: companySlugs (required), jobFamilySlug (required).
get-domain-knowledgeARead-onlyInspect
Get reference knowledge about the Levels.fyi data model, by topic: compensation, levels, vesting, company_groups, locations, job_families, enums, negotiation_coaching. Covers compensation concepts, the standard level ladder, vesting patterns, company groups, and how to resolve locations / job families / enums. negotiation_coaching describes Levels.fyi's offer negotiation coaching: use it only when the user asks for help negotiating. Omit "topic" to get every data-model topic.
Inputs: topic.
get-jobARead-onlyInspect
Get one job posting by its jobId from search-jobs: the full description as text, locations, work arrangement, employment type, the pay range the posting states, Levels.fyi's estimated total compensation by level for the role (USD; matchesThisPosting marks the level the posting is for), the company, the url of the Levels.fyi job page, and applyUrl to apply on the employer's site. REQUIRED arguments: jobId.
Inputs: jobId (required).
get-job-familyARead-onlyInspect
Look up a job family by its slug and get its focus areas (specializations) with their titles, plus untagged titles. Use this to discover the focus tags and titles available within a role (e.g. to find focusTagSlugs for the benchmark tools). Use search-job-families first if you only have a name. REQUIRED arguments: jobFamilySlug.
Inputs: jobFamilySlug (required).
get-locationARead-onlyInspect
Look up one or more location slugs and get their details: name, type (country / metro-DMA / state), parent country, currency, and coordinates. Use search-locations first if you only have a name. Errors if any slug is invalid. REQUIRED arguments: locationSlugs. Array-typed arguments (locationSlugs) must be passed as arrays, even for a single value.
Inputs: locationSlugs (required).
get-location-statsARead-onlyInspect
Get 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.
Inputs: countrySlug (required), jobFamilySlug (required).
get-metric-explanationARead-onlyInspect
Explain a Levels.fyi compensation metric or concept (e.g. "TC" / total_compensation, base salary, total_cash, tc_first_year, vesting, sign_on, target_bonus) — its meaning, formula, and caveats. Pass an unknown metric to get the list of known ones. REQUIRED arguments: metric.
Inputs: metric (required).
get-permissionsARead-onlyInspect
Connectivity check for the Levels.fyi MCP server. Returns "pong", echoes an optional message, and lists what each tool returns and the rate limits. Call it when a result looks smaller than expected, instead of retrying.
Inputs: message.
get-profileARead-onlyInspect
Get 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.
Inputs: no named parameters.
get-salaries-by-company-levelARead-onlyInspect
Get 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-companies; never guess a slug. REQUIRED arguments: jobFamilySlug, locationSlug, companySlugs. Array-typed arguments (companySlugs) must be passed as arrays, even for a single value.
Inputs: companySlugs (required), locationSlug (required), jobFamilySlug (required).
get-salary-percentilesARead-onlyInspect
Get 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.
Inputs: jobFamilySlug (required), locationSlugs (required).
get-salary-submission-by-idARead-onlyInspect
Get 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.
Inputs: uuid (required).
get-vesting-schedulesARead-onlyInspect
Get equity vesting schedules for one or more companies, decoded into structured data: per-year vesting percent and frequency (cliff/quarterly/monthly), whether there's a 1-year cliff, whether it's backloaded (e.g. Amazon 5/15/40/40) / frontloaded / linear, plus a plain-English description and vesting type (RSU, options). A company that uses more than one schedule lists the others in alternatives, decoded the same way. Pass company slugs (use search-companies to resolve names first). REQUIRED arguments: companySlugs. Array-typed arguments (companySlugs) must be passed as arrays, even for a single value.
Inputs: companySlugs (required).
search-allARead-onlyInspect
Search across ALL entity types at once (companies, job families, job titles, focus tags, locations, and industries) by passing searchText (required) and get a single ranked list, each result tagged with its type and slug/id. Use this when you don't yet know which track an entity belongs to, or to disambiguate an ambiguous name; once the type is known, prefer the type-specific tools (search-companies, search-job-titles, search-locations, search-job-families, search-focus-areas) for tighter results. If a match is found under a DIFFERENT entity type than the user expected, do not silently substitute it — surface that mismatch and confirm with the user before proceeding. REQUIRED arguments: searchText.
Inputs: searchText (required), limit, excludeFamilyLikeTitles.
search-companiesARead-onlyInspect
Search companies using searchText input (required) and get their Levels.fyi slugs. Use this FIRST to resolve a company name (e.g. "Google", "Meta") into the slug that the benchmark tools require in their companySlugs filter. Also matches former names and aliases, so a renamed company is found under its old name. Returns an array of { name, slug } matches. If this returns no matches, fall back to search-all, which searches every entity type and applies a fuzzy fallback. REQUIRED arguments: searchText.
Inputs: searchText (required), limit.
search-companies-by-vestingARead-onlyInspect
Find companies by their equity vesting characteristics: vesting/equity type (e.g. "RSU"), vesting shape (frontloaded, backloaded like Amazon, linear, one/two/three_year, or extended 5+ years), total years, and whether there's a 1-year cliff. Returns matching companies (most data-rich first) with their decoded vesting schedules.
Inputs: limit, hasCliff, maxYears, minYears, +2 more.
search-focus-areasARead-onlyInspect
Search focus tags (specializations within a role, e.g. "mobile-ios-android", "ml-ai", "devops", "security") using searchText input (required) and get their slugs. Use this to resolve a specialization into the focusTagSlugs the benchmark tools accept. Returns matching focus tags with their slugs. If this returns no matches, fall back to search-all, which searches every entity type and applies a fuzzy fallback. REQUIRED arguments: searchText.
Inputs: searchText (required), limit.
search-job-familiesARead-onlyInspect
Search job families / roles using searchText input (required) and get their Levels.fyi slugs. Use this to resolve a role name (e.g. "software engineer", "product manager", "data scientist") into the jobFamilySlug the benchmark tools require. Returns matching job families with their slugs. A specific title (e.g. "UX designer") is not a job family: if this returns no matches, use search-role-terms, which returns the title with its job family slug, then search-all. REQUIRED arguments: searchText.
Inputs: searchText (required), limit.
search-jobsARead-onlyInspect
Search 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 the values you will use and ask them to confirm or change them: a profile describes the job they have, not necessarily the one they want next. Do not call get-profile without asking.
Results come up to 2 jobs per company; limit counts companies, except with a single companySlug, where it counts jobs. A page can hold fewer than limit; keep paging while nextOffset is not null. Put each job's url on its title and keep URLs complete. When the client shows results as cards, do not list them again in text: summarise the patterns instead. Call get-job for a posting's full description. For a signed-in user the result also says whether a resume is on file (profile.resumeStatus). REQUIRED arguments: query. Array-typed arguments (e.g. companySlugs, jobFamilySlugs) must be passed as arrays, even for a single value.
Inputs: query (required), limit, offset, sortBy, +9 more.
search-job-titlesARead-onlyInspect
Search specific job titles by name. Each result includes its id (the titleId the benchmark tools accept in the jobTitleIds filter) and its parent job family, so use this to narrow a benchmark query to an exact title (e.g. "Forward Deployed Software Engineer") within a job family. Set excludeFamilyLikeTitles to drop titles that are effectively just the job family. If this returns no matches, fall back to search-all, which searches every entity type and applies a fuzzy fallback. REQUIRED arguments: searchText.
Inputs: searchText (required), limit, excludeFamilyLikeTitles.
search-locationsARead-onlyInspect
Search 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.
Inputs: searchText (required), type, limit.
search-raw-data-pointsARead-onlyInspect
Get 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.
Inputs: jobFamilySlug (required), companySlug, locationSlug.
search-role-termsARead-onlyInspect
Resolve a role term by searching job families, job titles, and focus tags TOGETHER in one call. Use this when you're unsure whether a term (e.g. "ML engineer", "mobile", "SRE") is a job family, a specific title, or a specialization — each result is tagged with its type and slug so you can feed the right one to the benchmark tools. REQUIRED arguments: searchText.
Inputs: searchText (required), limit.
search-top-companiesARead-onlyInspect
Get 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.
Inputs: countrySlug (required), jobFamilySlug (required).
send-feedbackAInspect
Report wrong or missing Levels.fyi data, or a missing feature, to the Levels.fyi team. Call it only after telling the user what you will send and getting their agreement. Never include personal details; contactEmail only when the user wants a reply and gives it. Returns { received, id }. REQUIRED arguments: kind, message.
Inputs: kind (required), message (required), toolName, companySlug, +3 more.
upload-resumeADestructiveIdempotentInspect
Add 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.
webUploadUrl: otherwise, give the user this link; they sign in there with the same Levels.fyi account they connected here, upload the file themselves, and come back and say "uploaded". Never paste the resume's text or contents anywhere else.
The resume is parsed in the background, usually within a couple of minutes. Call get-profile afterwards to check it; until parsing finishes, it can still show the previous resume. REQUIRED arguments: fileType.
Inputs: fileType (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Search job postings from employer career pages, match companies, and get pay and hiring insights
Open jobs with salaries from Workday, Greenhouse, Lever, Ashby and 3 more careers-page systems.
Search open jobs, track new and closed roles, and get salaries on Greenhouse, Ashby, Lever, Workday.
Live healthcare pay data: advertised ranges by role/state/city, offer checks, transparency scores.
Related MCP Servers
- AlicenseAqualityCmaintenanceLive tech-hiring intelligence for AI agents. Search 130K+ open jobs collected daily from ~500 tech companies' own career sites â plus company hiring profiles, tech stacks, salary benchmarks, and skill trends. Five tools work with no account.31193 npmMIT
- AlicenseAqualityCmaintenanceEnables querying open job postings directly from company applicant-tracking systems (Greenhouse, Ashby, Lever), finding a company's job board, listing and comparing roles, and accessing salary data, all without scraping or API keys.360 PyPI1MIT
- AlicenseNot gradedqualityDmaintenanceUS + EU salary benchmarking, pay transparency compliance, and semantic endpoints. 1,400+ US occupations, 28 EU countries. MCP server for AI agents.MIT
- FlicenseNot gradedqualityDmaintenanceEnables querying real disclosed salary data across 20 regions, with tools to search jobs, retrieve salary statistics, and find similar roles.-
Glama MCP Gateway
Add one secure layer between your agents and this server.