mcp-lever
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| resolve_companyA | Turn company names into the Lever site names that address their job boards, and report every instance that answered. search_jobs resolves names on its own, so reach for this to check which of several companies are on Lever at all: it probes names without reading a single board, where a search would read one per company. |
| search_jobsA | Search the openings published by named companies on Lever. |
| get_jobA | Read one Lever opening in full: the advert, its named sections, and the salary as published. company_slug and instance are the ones the row carried, and a site living on both instances holds different openings on each. |
| list_filter_valuesA | List the team, location and commitment wordings one company uses on Lever, so a filter can carry the words that company publishes. The vocabulary belongs to each company: one writes Full-time, another Full Time, another EE Full-Time. Lever publishes no vocabulary for department, so a department filter is checked against the openings a company has open right now. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: resolve_company checks company presence, search_jobs queries openings, get_job retrieves full details, and list_filter_values provides filter vocabulary. No overlap in functionality.
All tool names follow the same verb_noun pattern (resolve_company, search_jobs, get_job, list_filter_values) with consistent snake_case, making the interface predictable.
With 4 tools, the server is well-scoped for its purpose. Each tool addresses a distinct need without unnecessary bloat or missing essential functionality.
The tool set covers the full read-only workflow for Lever job boards: verifying companies, searching jobs, retrieving details, and preparing filters. No obvious gaps in the provided functionality.