Levels.fyi
Servidor MCP de Levels.fyi
Consulta datos de salarios, niveles de empresa y empleos abiertos de los informes de pago de Levels.fyi para comparar sueldos y evaluar ofertas.
Conectar con Levels.fyi
No hace falta iniciar sesión. Conéctate con la URL propia de Levels.fyi:
Pégala en cualquier cliente compatible con servidores MCP remotos. Tu cliente habla directamente con Levels.fyi, no a través de mcp.tc.
Compartir este servidor
El enlace abre esta página, con la URL y los pasos de configuración.
mcp.tc/i/levels-fyiDescripción
Se conecta a los datos de compensación de Levels.fyi, creados a partir de más de 1M de informes de pago. Puedes convertir empresas, ubicaciones y familias de puestos en slugs y después obtener la compensación total mediana por ubicación, por nivel de empresa y para las empresas y ubicaciones mejor pagadas. También cubre calendarios de vesting, envíos recientes de salarios, búsqueda de empleos abiertos y explicaciones de métricas de pago. Los usuarios con sesión iniciada pueden leer su perfil, subir un currículum y añadir su propio salario.
El servidor está alojado en https://mcp.levels.fyi/ mediante Streamable HTTP. No hace falta una cuenta para hacer consultas. Añadir tu propio salario solo requiere un correo electrónico, y es necesario iniciar sesión para leer tu perfil o subir un currículum. El plan gratuito filtra por familia de puestos, ubicación y empresa.
Qué puedes hacer
- Convertir nombres de empresas, ubicaciones y familias de puestos en slugs
- Obtener la compensación total mediana de una familia de puestos en una ubicación
- Obtener el pago por nivel interno de empresa, como Meta E5
- Clasificar las empresas y ubicaciones mejor pagadas de un país
- Explorar los envíos individuales de salarios más recientes
- Consultar los calendarios de vesting de acciones de las empresas
- Buscar empleos abiertos con rangos salariales indicados
- Añadir tu propio salario u oferta tras una vista previa
Herramientas 30
get-permissionsSolo lecturaComprobación de conectividad que devuelve pong, descripciones de herramientas y límites de uso.
get-salary-percentilesSolo lecturaCompensación total anual mediana de una familia de puestos en una ubicación, últimos 12 meses.
get-salaries-by-company-levelSolo lecturaCompensación total mediana de cada nivel interno de una empresa.
search-raw-data-pointsSolo lecturaEnvíos individuales de salarios más recientes por familia de puestos, ubicación o empresa.
get-companySolo lecturaPerfil de la empresa con plantilla, sede, año de fundación, ticker y valoración.
get-company-levelsSolo lecturaNombres de los niveles internos de una empresa para una familia de puestos, ordenados por antigüedad.
get-company-groupSolo lecturaConvertir un grupo con nombre, como FAANG, en slugs de empresas.
search-companiesSolo lecturaBuscar empresas y obtener sus slugs de Levels.fyi.
search-companies-by-vestingSolo lecturaEncontrar empresas por tipo, forma, duración y cliff del vesting de acciones.
search-top-companiesSolo lecturaEmpresas mejor pagadas para una familia de puestos en un país según el pago mediano.
get-locationSolo lecturaDetalles de los slugs de ubicación: tipo, país superior, moneda y coordenadas.
get-location-statsSolo lecturaUbicaciones mejor pagadas para una familia de puestos dentro de un país.
Mostrar 18 herramientas más
search-locationsSolo lecturaBuscar países, áreas metropolitanas y estados de EE. UU. para obtener slugs.
get-job-familySolo lecturaÁreas de enfoque y títulos disponibles dentro de una familia de puestos.
search-job-familiesSolo lecturaBuscar familias de puestos y roles para obtener slugs.
search-job-titlesSolo lecturaBuscar títulos de puesto concretos y obtener sus ids y su familia de puestos superior.
search-focus-areasSolo lecturaBuscar especializaciones dentro de un rol y obtener sus slugs.
search-role-termsSolo lecturaBuscar juntos familias de puestos, títulos y etiquetas de enfoque en una sola llamada.
get-profileSolo lecturaLeer el perfil profesional de Levels.fyi del usuario con sesión iniciada y el estado de su currículum.
upload-resumePuede borrarAñadir o reemplazar el currículum del usuario con sesión iniciada.
add-salary-submissionEscrituraAñadir a Levels.fyi el salario u oferta de empleo del propio usuario tras una vista previa.
get-salary-submission-by-idSolo lecturaObtener un envío de salario por su UUID.
get-vesting-schedulesSolo lecturaCalendarios estructurados de vesting de acciones de una o más empresas.
search-jobsSolo lecturaBuscar empleos abiertos con rangos salariales indicados y filtros.
get-jobSolo lecturaOferta de empleo completa con descripción, rango salarial y pago estimado por nivel.
send-feedbackEscrituraInformar a Levels.fyi de datos incorrectos o ausentes, o de una función que falta.
search-allSolo lecturaBuscar a la vez empresas, familias de puestos, títulos, etiquetas de enfoque, ubicaciones e industrias.
get-available-filtersSolo lecturaListar las entradas y valores de filtro que admite el plan gratuito.
get-metric-explanationSolo lecturaExplicar una métrica de compensación como TC, salario base o bono de incorporación.
get-domain-knowledgeSolo lecturaConocimiento de referencia sobre el modelo de datos de Levels.fyi por tema.
Leídas del servidor en funcionamiento el 17 nov 2026. Solo lectura, Escritura y Puede borrar son indicaciones que declara el servidor; tu cliente decide si te pregunta antes de ejecutar una herramienta.
Prompts de ejemplo
¿Cuánto gana un ingeniero de software Meta E5 en el Bay Area?
¿Qué empresas pagan más a los ingenieros de software en Estados Unidos?
Muestra el calendario de vesting de las acciones de Amazon y Google.
Busca empleos abiertos de product manager en Nueva York con rangos salariales.
Configuración
Todos los clientes se conectan a mcp.levels.fyi. Elige el tuyo; la página recuerda tu elección.
Claude Code
- Ejecútalo en un terminal, en la carpeta de tu proyecto:
claude mcp add --transport http levels-fyi https://mcp.levels.fyi/- Inicia Claude Code y escribe
/mcp. levels-fyi debería aparecer como conectado.
Añade --scope user para que esté disponible en todos los proyectos, no solo en este.
Claude Desktop
- Abre Customize → Connectors, haz clic en + Add y luego en Add custom connector.
- Llámalo Levels.fyi y pega esta URL:
https://mcp.levels.fyi/- Haz clic en Add. Sus herramientas aparecen en el menú de herramientas del chat.
El archivo de configuración JSON de Claude Desktop solo inicia servidores locales. Los servidores remotos van por Connectors, y los conectores que añades en claude.ai también aparecen aquí.
claude.ai
- Abre el formulario de conectores en claude.ai. Este botón rellena el nombre y la URL por ti:
Añadir a claude.ai (se abre en una pestaña nueva)
- Comprueba que la URL es
https://mcp.levels.fyi/y haz clic en Add. - Actívalo en un chat desde el menú de herramientas.
Los planes gratuitos permiten un conector personalizado. En los planes Team y Enterprise lo añade un propietario en Organization settings → Connectors.
ChatGPT
- En chatgpt.com, ve a Plugins, selecciona + y luego Add custom MCP server.
- Escribe un nombre para el servidor.
- En Connection, pega
https://mcp.levels.fyi/como URL del servidor y luego, como autenticación, elige No authentication. - Marca I understand and want to continue y luego selecciona Create as a plugin.
Poder añadir un servidor MCP personalizado depende de tu plan de ChatGPT y de los permisos de tu espacio de trabajo (en los espacios Business pueden hacerlo los administradores y los propietarios).
Cursor
Añadir a Cursor (se abre en una pestaña nueva)
O añádelo a mano en ~/.cursor/mcp.json (todos los proyectos) o en .cursor/mcp.json (este proyecto):
{
"mcpServers": {
"levels-fyi": {
"url": "https://mcp.levels.fyi/"
}
}
}VS Code
Instalar en VS Code (se abre en una pestaña nueva)
O desde un terminal:
code --add-mcp '{"name":"levels-fyi","type":"http","url":"https://mcp.levels.fyi/"}'O haz commit del archivo en el repositorio como .vscode/mcp.json:
{
"servers": {
"levels-fyi": {
"type": "http",
"url": "https://mcp.levels.fyi/"
}
}
}Devin Desktop
- Añádelo a
~/.config/devin/mcp_config.json(macOS y Linux) o a%APPDATA%\devin\mcp_config.json(Windows):
{
"mcpServers": {
"levels-fyi": {
"serverUrl": "https://mcp.levels.fyi/"
}
}
}- Actualiza la lista de servidores MCP en Cascade.
Devin Desktop es el nuevo nombre de Windsurf. Para los servidores remotos lee serverUrl (o url).
Codex
codex mcp add levels-fyi --url https://mcp.levels.fyi/O edita directamente ~/.codex/config.toml:
[mcp_servers.levels-fyi]
url = "https://mcp.levels.fyi/"Gemini CLI
gemini mcp add --transport http levels-fyi https://mcp.levels.fyi/Así lo añades al proyecto actual. Añade -s user para usarlo en todas partes.
Cualquier cliente
La mayoría de los clientes aceptan esta forma. Algunos llaman de otra manera al campo de la URL: serverUrl en Devin Desktop, httpUrl en el archivo de ajustes de Gemini CLI.
{
"mcpServers": {
"levels-fyi": {
"type": "http",
"url": "https://mcp.levels.fyi/"
}
}
}Zed pone los servidores bajo context_servers en sus ajustes. Cline necesita "type": "streamableHttp"; si no, supone SSE.
¿Tu cliente solo inicia servidores locales? Conéctalo con npx -y mcp-remote https://mcp.levels.fyi/.
Insertar
Muestra Levels.fyi en un README o en tu web. Cada inserción enlaza a esta página, usa la URL propia del servidor y no instala cookies. Cómo funcionan las inserciones
La tarjeta, el iframe y el JSON están en inglés. Añade ?lang=it, fr, de o es a su dirección para otro idioma.
Insignia para README
[](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>Sigue el modo claro u oscuro de quien lee. Añade ?theme=light o ?theme=dark para fijarlo, o ?style=compact para mostrar el símbolo sin la palabra.
Tarjeta para web
<script src="https://mcp.tc/w/levels-fyi.js" async></script>La tarjeta aparece donde esté la etiqueta. Añade data-theme="dark" o data-size="compact" a la etiqueta para cambiarla. El archivo contiene todo lo que necesita, así que no hace otras solicitudes ni instala 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>Úsalo en páginas que no permiten scripts. Añade ?theme=light o ?theme=dark a la dirección para fijar los colores.
JSON
La ficha como datos para tus propias páginas y herramientas: nombre, descripción corta, la URL propia del servidor, herramientas y los enlaces «Add to». Cualquier web puede leerla (CORS abierto).
https://mcp.tc/i/levels-fyi.jsonPrompt para la IA
Pégalo en un asistente de programación con IA, como Claude Code o Cursor, y añadirá la tarjeta de Levels.fyi a tu web.
Añade a mi web la tarjeta de mcp.tc de Levels.fyi, un servidor MCP. Es un solo script estático: sin paso de build, sin paquetes que instalar, sin cookies.
Pon esta etiqueta donde deba aparecer la tarjeta. La tarjeta se muestra justo antes de ella:
```html
<script src="https://mcp.tc/w/levels-fyi.js" async></script>
```
Para mostrarla en otro sitio, pon allí este marcador y carga el mismo script una sola vez, por ejemplo antes de `</body>`. Deja el enlace dentro: lo ven los visitantes sin JavaScript.
```html
<div data-mcptc="levels-fyi"><a href="https://mcp.tc/i/levels-fyi">Levels.fyi on mcp.tc</a></div>
```
Opciones:
- `data-theme="light"` o `"dark"` en la etiqueta o el marcador fija los colores. Sin él, la tarjeta sigue el modo claro u oscuro del visitante.
- `data-size="compact"` da una tarjeta más pequeña, sin el eslogan.
- La variable CSS `--mcptc-max-width` en el marcador o en un elemento padre fija el ancho (por defecto `520px`).
- `?lang=` en la URL del script fija el idioma de la tarjeta: `en`, `it`, `fr`, `de` o `es`.
Si el sitio tiene una Content Security Policy, permite `script-src https://mcp.tc` e `img-src data:` (el icono va incrustado).
Para un README u otra documentación en Markdown, usa la insignia:
```markdown
[](https://mcp.tc/i/levels-fyi)
```
Referencia: https://mcp.tc/es/embedHistorial de cambios
Leemos la lista de herramientas de este servidor cada 3 horas y registramos lo que cambia. Última lectura: 18 nov 2026, 05:37 UTC.
-
10 herramientas cambiadas. Instrucciones del servidor cambiadas.
Nuevas instrucciones del servidor
Detalles, 16 nov 2026, 08:52 UTC
Cambiadas 10
add-salary-submissiondescripciónAntesAdd 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…DespuésAdd 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-filtersdescripciónAntesList 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.DespuésList 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-levelsdescripciónAntesGet 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.DespuésGet 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-statsdescripciónAntesGet 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.DespuésGet 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-leveldescripciónAntesGet
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.DespuésGet 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-percentilesdescripciónAntesGet 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.DespuésGet 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-iddescripciónAntesGet 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.DespuésGet 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-jobsdescripciónAntesSearch 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…DespuésSearch 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-pointsdescripciónAntesGet 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.DespuésGet 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-companiesdescripciónAntesGet 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.DespuésGet 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.
Instrucciones del servidor
AntesThis 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…
DespuésThis 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 herramientas cambiadas. Instrucciones del servidor cambiadas.
Nuevas instrucciones del servidor
Detalles, 13 nov 2026, 08:53 UTC
Cambiadas 3
add-salary-submissiondescripción y esquema de entradaAntesAdd 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…DespuésAdd 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…
- Descripción de
yearsOfExperienceAntesTotal years of professional
experience.DespuésTotal years of professional experience, in whole years; a decimal is rounded.
- Descripción de
confirmAntesfalse (default) returns a preview and
writes nothing.truewritesthe entry: only after the user said yes to the preview.Despuésfalse (default) returns a preview and adds nothing to Levels.fyi. true adds the entry: only after the user said yes to the preview.
- Descripción de
search-jobsdescripciónEl texto que se muestra aquí es igual antes y después: el cambio está más allá de los primeros 1000 caracteres o en caracteres que no se ven.
upload-resumedescripciónAntesAdd 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…
DespuésAdd 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…
Instrucciones del servidor
AntesThis 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…
DespuésThis 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…
-
Instrucciones del servidor cambiadas.
Nuevas instrucciones del servidor
Detalles, 13 nov 2026, 05:51 UTC
Instrucciones del servidor
AntesThis 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…
DespuésThis 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 herramienta cambiada. Instrucciones del servidor cambiadas.
Nuevas instrucciones del servidor
Detalles, 10 nov 2026, 14:48 UTC
Cambiadas 1
get-profiledescripciónAntesGet 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.DespuésGet 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.
Instrucciones del servidor
AntesThis 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,…
DespuésThis 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 herramientas cambiadas.
Detalles, 6 nov 2026, 11:44 UTC
Cambiadas 3
get-salaries-by-company-levelesquema de entrada- Descripción de
locationSlugAntesOne 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…DespuésOne 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.
- Descripción de
get-salary-percentilesesquema de entrada- Descripción de
locationSlugsAntesUp 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…DespuésUp 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.
- Descripción de
search-locationsdescripciónAntesSearch 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.DespuésSearch 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.
-
Instrucciones del servidor cambiadas.
Nuevas instrucciones del servidor
Detalles, 6 nov 2026, 08:43 UTC
Instrucciones del servidor
AntesThis 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…
DespuésThis 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 herramientas cambiadas. Instrucciones del servidor cambiadas.
Nuevo parámetro obligatorio, Nuevas instrucciones del servidor
Detalles, 4 nov 2026, 11:44 UTC
Cambiadas 11
add-salary-submissiondescripción y esquema de entradaEl texto que se muestra aquí es igual antes y después: el cambio está más allá de los primeros 1000 caracteres o en caracteres que no se ven.
- Parámetros eliminados:
submissionId
- Parámetros eliminados:
get-available-filtersdescripciónAntesList 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.
DespuésList 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-levelsdescripción y esquema de entradaAntesGet 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.
DespuésGet 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.
- Parámetros nuevos:
companySlugs - Parámetros eliminados:
companySlug - Ahora obligatorios:
companySlugs - Ya no obligatorios:
companySlug
- Parámetros nuevos:
get-location-statsdescripciónAntesGet 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.
DespuésGet 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-leveldescripción y esquema de entradaAntesGet 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.
DespuésGet 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.
- Parámetros nuevos:
companySlugs - Parámetros eliminados:
companySlug - Ahora obligatorios:
companySlugs - Ya no obligatorios:
companySlug - Descripción de
locationSlugAntesOne 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.DespuésOne 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…
- Parámetros nuevos:
get-salary-percentilesget-vesting-schedulessearch-jobssearch-locationssearch-raw-data-pointssearch-top-companiesInstrucciones del servidor
Parte de esta entrada no se muestra, para que la página siga siendo ligera.
-
Instrucciones del servidor cambiadas.
Nuevas instrucciones del servidor
Detalles, 3 nov 2026, 08:51 UTC
Instrucciones del servidor
Parte de esta entrada no se muestra, para que la página siga siendo ligera.
-
1 herramienta cambiada. Instrucciones del servidor cambiadas.
Nuevas instrucciones del servidor
Detalles, 30 oct 2026, 17:47 UTC
Cambiadas 1
upload-resumeInstrucciones del servidor
Parte de esta entrada no se muestra, para que la página siga siendo ligera.
-
Inicio del seguimiento: 30 herramientas.
Preguntas frecuentes
¿Puedo pegar mcp.tc/i/levels-fyi en mi cliente MCP?
No. Los enlaces de mcp.tc son páginas, no direcciones de servidores. Conéctate con https://mcp.levels.fyi/, para que tu cliente hable directamente con Levels.fyi. El enlace rápido sirve para compartir: abre esta página, con los pasos de configuración para cada cliente.
¿Levels.fyi necesita una clave de API o iniciar sesión?
No. Levels.fyi no pide cuenta ni clave.
¿Levels.fyi es un servidor remoto o local?
Remoto. Lo aloja Levels.fyi en https://mcp.levels.fyi/, y usa Streamable HTTP. No hay nada que instalar.
¿Qué puede hacer Levels.fyi?
Tiene 30 herramientas, entre ellas get-permissions, get-salary-percentiles y get-salaries-by-company-level. Puedes convertir nombres de empresas, ubicaciones y familias de puestos en slugs, obtener la compensación total mediana de una familia de puestos en una ubicación y obtener el pago por nivel interno de empresa, como Meta E5.
¿Qué clientes pueden usarlo?
Cualquier cliente compatible con servidores MCP remotos: Claude Code, Claude Desktop, claude.ai, ChatGPT, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed y otros. Los pasos de configuración cubren cada uno.
¿mcp.tc sigue los cambios de Levels.fyi?
Sí. La pestaña Historial de Levels.fyi muestra cada cambio que encontramos en sus herramientas, hasta las descripciones y los parámetros, además de las versiones nuevas y las ediciones de su responsable. Sigue la ficha para recibir un correo cuando cambie.
¿Quién escribió esta página?
El robot de mcp.tc leyó los metadatos propios de Levels.fyi (su handshake MCP, su lista de herramientas y sus páginas públicas), y un modelo de IA redactó el texto a partir de ellos. Una persona revisa todo lo que las comprobaciones no pueden confirmar. Aun así, el texto puede contener errores, así que si encuentras uno, usa Reportar esta ficha en esta página. Esta traducción la hizo un modelo de IA a partir del texto en inglés.
mcp.tc no tiene relación con Levels.fyi. Esta página se creó a partir de los metadatos públicos de Levels.fyi, comprobados por última vez el 17 nov 2026, y un modelo de IA escribió la descripción, así que puede contener errores. Los nombres y marcas pertenecen a sus titulares. ¿Algo no cuadra? Reportar esta ficha. La traducción la hizo un modelo de IA a partir del texto en inglés.