# Dice MCP MCP server

Dice MCP: Search for tech jobs on Dice.com

## Links
- Registry page: https://www.getdrio.com/mcp/io-github-diceholdingsinc-dice-mcp

## Install
- Endpoint: https://mcp.dice.com/mcp
- Auth: Not captured

## Setup notes
- Remote endpoint: https://mcp.dice.com/mcp

## Tools
- search_jobs (Job Search) - Search for job listings by keyword, location, and filters. Returns job details, company info, and application links.

Use this tool when users want to find jobs, search employment opportunities, or explore job openings.
DO NOT use for: applying to jobs, submitting applications, or making employment decisions.

LLM USAGE INSTRUCTIONS:
- ALWAYS provide the keyword parameter (required)
- When presenting results to users, include BOTH the job details URL (detailsPageUrl)
  AND the company page URL (companyPageUrl) for each job
- Use location to find geographically relevant positions
- Combine filters to refine searches (e.g., workplace_types=['Remote'] for remote work)
- Use posted_date to find recent openings ('ONE'=1 day, 'THREE'=3 days, 'SEVEN'=7 days)
- Default jobs_per_page is reasonable, increase for comprehensive searches
- Use company_name to scope results to a specific employer
- Use sort='datePosted' when the user wants the newest listings instead of the most relevant
- Use facets to get aggregate counts (e.g., how many results are remote vs on-site) without paging through all results
- After presenting results, do NOT automatically call get_job_details for every job returned.
  Wait for the user to indicate which specific job(s) they're interested in, then pass that
  job's guid to get_job_details.

IMPORTANT - AI DISCLOSURE REQUIREMENT:
When presenting job search results to users, you MUST include an appropriate disclosure
that these results were retrieved using AI assistance. Example disclosure language:
"These job listings were found using AI-powered search. Please review all job details
carefully and verify information directly with employers before applying."

This tool provides job listing data only. Final employment decisions should always
involve human judgment and direct review of complete job postings.

Args:
    keyword: The job keyword or title to search for (required)
    location: Geographic location for the job search (city, state, country)
    radius: Search radius from the specified location (minimum 1, requires radius_unit)
    radius_unit: Unit for search radius. Options: 'mi', 'km' (requires radius)
    jobs_per_page: Number of jobs to return per page (1-100, defaults to 5)
    page_number: Page number for pagination (1-based, default is 1)
    sort: Sort order for results. Options: 'relevance', 'datePosted' (defaults to relevance)
    posted_date: Filter by posting date. Options: 'ONE' (1 day), 'THREE' (3 days), 'SEVEN' (7 days)
    workplace_types: Workplace arrangements. Options: 'Remote', 'On-Site', 'Hybrid'
    employment_types: Employment types. Options: 'FULLTIME', 'CONTRACTS', 'PARTTIME', 'THIRD_PARTY', 'INTERNSHIP'
    employer_types: Employer types. Options: 'Direct Hire', 'Recruiter', 'Other'
    willing_to_sponsor: Filter for employers willing to sponsor work authorization (boolean)
    easy_apply: Filter for jobs with easy application process (boolean)
    company_name: Filter by company name
    fields: Specific fields to include in response (optional, returns all exposed fields by default)
    facets: Facet dimensions to aggregate (optional). Options: 'employmentType', 'postedDate',
        'workFromHomeAvailability', 'workplaceTypes', 'employerType', 'easyApply', 'isRemote',
        'willingToSponsor'

Returns:
    JobSearchResult: Contains:
        - data: List of JobDisplayFields with job details including:
          * guid: The job's identifier to pass as job_id to get_job_details for the full
            description and skills list (NOT the `id` field, which is a different, internal
            identifier not accepted by get_job_details)
          * detailsPageUrl: Direct link to full job posting
          * companyPageUrl: Link to company profile page
          * title, summary, salary, location, employmentType, etc.
        - metadata: Search metadata with pagination info and facet results

Raises:
    Exception: If API call fails or input validation errors occur
 Endpoint: https://mcp.dice.com/mcp
- get_job_details (Get Job Details) - Retrieve a job's full description and associated skills by job ID.

Use this tool when users want more detail about a specific job than search_jobs returns
(e.g. after finding a job via search_jobs and wanting its full description and skills list).
DO NOT use for: searching/discovering jobs by keyword (use search_jobs instead).

LLM USAGE INSTRUCTIONS:
- Only call this after the user has picked out a specific job from search_jobs results
  (or otherwise supplied a job's guid directly) — do not call it speculatively for every
  search result.
- After returning job details, do NOT automatically call get_company. Instead, offer to
  look up the company (e.g. "Want me to pull up more info on the company?") and only call
  get_company, passing this same job_id, if the user says yes.

Args:
    job_id: The unique identifier of the job to retrieve (required). This must be the
        job's `guid` field from a search_jobs result, NOT its `id` field — `id` is a
        different, internal identifier that this tool does not accept.

Returns:
    JobDetails: Contains:
        - description: The full job description
        - skills: List of Skill objects associated with the job

Raises:
    Exception: If the API call fails, the job is not found, or input validation errors occur
 Endpoint: https://mcp.dice.com/mcp
- get_company (Get Company) - Retrieve the name and description of the company behind a job, by job ID.

Use this tool when users want more detail about a company than search_jobs/get_job_details
return (e.g. after finding a job and wanting to know more about the company that posted it).
DO NOT use for: searching/discovering companies or jobs by keyword (use search_jobs instead).

LLM USAGE INSTRUCTIONS:
- The typical flow is: search_jobs to find jobs -> user picks one -> offer to look up the
  company -> if the user agrees, call this tool with that same job_id (the same guid used
  for get_job_details; no separate lookup step is needed first).
- Do not call this automatically right after get_job_details; ask the user first unless
  they already explicitly asked for company details.
- Not every company has published an employer branding profile, and some profiles are
  marked not visible by the company. When that happens this tool does NOT raise — it
  returns a Company with `message` set and empty name/desc. Relay that message to the
  user (e.g. "Looks like that company hasn't published a public profile.") rather than
  treating it as an error.

Args:
    job_id: The unique identifier of the job whose company to look up (required). This
        must be the job's `guid` field from a search_jobs result, NOT its `id` field —
        `id` is a different, internal identifier that this tool does not accept.

Returns:
    Company: Contains:
        - name: The company name (empty if message is set)
        - desc: The company description (empty if message is set)
        - message: Set instead of name/desc when there is no visible company profile
          to show; None when name/desc are populated

Raises:
    Exception: If the job is not found, an API call itself fails (network error,
        non-200 response, GraphQL errors), or input validation errors occur
 Endpoint: https://mcp.dice.com/mcp

## Resources
Not captured

## Prompts
Not captured

## Metadata
- Owner: io.github.DiceHoldingsInc
- Version: 1.0.0
- Runtime: Streamable Http
- Transports: HTTP
- License: Not captured
- Language: Not captured
- Stars: Not captured
- Updated: Jan 5, 2026
- Source: https://registry.modelcontextprotocol.io