Search Dice's tech-focused job database through AI assistants using natural language. Find technology jobs by role, skills, location, remote or hybrid work preferences, salary, visa sponsorship, and posting date. Discover relevant career opportunities and build automated job search workflows with real-time listings and direct application links.
Codex is OpenAI's coding agent for the terminal. It reads MCP servers from its config and signs in to remote ones with OAuth.
This guide connects Dice MCP to Codex through MewCP, so Codex can use Dice MCP's 3 tools, like search_jobs, get_job_details and get_company.
Dice MCP needs no credentials, but every call still runs through MewCP: scoped, checked and logged like any other.
More apps
AI-powered job search and application tracking for AI Assistants. Search jobs across major job boards and company career pages, build personalized shortlists, evaluate job fit, tailor resumes and cover letters, and track applications from submission through interviews and offers.
JobYap aggregates live tech job listings from official company career pages, enabling AI agents to search openings by role, company, location, and remote status, retrieve salary ranges and application links, match jobs to candidate skills, and explore community discussions about salaries and interviews.
ContactOut helps recruiters and sales teams find professional contact information and build targeted prospect lists. Discover work emails, phone numbers, and professional profiles, search for candidates by role and company, and enrich lead records for recruiting and B2B outreach.
Ploid provides AI agents access to a living index of over 2 billion people, enabling natural-language people search, verified prospect and candidate list building, decision-maker discovery, and evidence-backed person research. Enrich profiles with professional history, social presence, and source-linked information for recruiting, sales prospecting, and market research.
Other clients
Dice MCP works the same way in every client below. Pick yours for its own guide.
Free to start.
Scope access to the exact Dice MCP tools and accounts you allow, work and personal side by side. Anything outside that scope is refused at call time, even when the model asks for it.
Each call is logged: what ran, on which account, and whether it worked. Failures come back structured, so the agent knows whether to retry instead of guessing.
Every app sits behind one secure MCP URL, and there is no server for you to deploy or keep running. Add an integration in the dashboard and it is live on the next call, with no config to change and no new credentials to wire up. Tools load only when a task needs them, so your agent stays fast and focused however many apps you connect.
Run this and approve access in the browser window.
Start a new chat and ask: "List the tools you can use from MewCP." You should see your connected apps.
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
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
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
