MewCP LogoAStheTech
MCPs
Use Cases

Use cases by category

Productivity & InboxInbox, calendar, and daily flowEngineering & DevOpsShip, debug, and run on-callSales & CRMPipeline, outreach, and dealsMarketing & GrowthCampaigns, SEO, and growthSupport & SuccessTriage tickets, keep customers happyFinance & OpsClose, reconcile, and expensesCreative & ContentGenerate assets and contentPeople & HiringHiring, onboarding, and HRResearch & DataSynthesize data and insights
See all use cases
Resources
BlogsProduct updates and storiesArticlesIntegration guides and code examples
PricingDocsSign in
MewCP Logo

Infrastructure You Can Trust for Agentic Products

X

Categories

  • Productivity & Docs
  • Developer Tools
  • CRM & Sales
  • Finance & Commerce
  • Data & Analytics
  • Marketing & SEO
  • Search & Web
  • Communication
  • View All Servers →

Resources

  • Blog
  • Docs
  • Privacy Policy
  • Terms of Service

Blogs

  • View All Blogs →

Articles

  • View All Articles →
Browse Servers|Pricing|Contact

Browse by Category

Productivity & Docs

  • Gmail
  • Google Drive
  • Google Classroom
  • Google Calendar
  • Google People
  • YouTube
  • Notion
  • ClickUp
  • Figma
  • Google Tasks
  • Cal
  • Monday
  • Luma
  • Notion MCP
  • Mem MCP
  • Linear MCP
  • Calendly MCP
  • Consensus MCP
  • Craft MCP
  • Close MCP
  • Dice MCP

Developer Tools

  • Gemini
  • Veo
  • ClickUp
  • Firecrawl
  • Vercel
  • Apify
  • Github
  • HTTP
  • Chef
  • Scientific Calculator
  • Figma
  • Perplexity
  • Apify MCP
  • Hugging Face Hub MCP
  • Buildkite MCP
  • Cloudflare MCP
  • Context7 MCP
  • Ahrefs MCP
  • Sentry MCP
  • Brevo Docs MCP
  • X Docs MCP
  • Jev
  • Linear MCP
  • Calendly MCP
  • Craft MCP
  • DeepWiki MCP

CRM & Sales

  • Google People
  • OneSignal MCP
  • Brevo Docs MCP
  • Brevo
  • Brevo MCP
  • Carbon Voice MCP
  • Clay MCP
  • Close MCP

Finance & Commerce

  • Razorpay
  • Polymarket
  • Kite
  • Stripe
  • Binance
  • Upstox
  • Aiwyn MCP
  • Era-Context-MCP

Data & Analytics

  • Apify MCP
  • Cloudflare MCP
  • Ahrefs MCP
  • Candid MCP
  • Consensus MCP
  • Contentsquare MCP
  • Era-Context-MCP

Marketing & SEO

  • Mailchimp
  • Google Business
  • YouTube
  • Google Search Console
  • OneSignal MCP
  • Cloudflare MCP
  • Brevo Docs MCP
  • Brevo
  • Brevo MCP
  • AirOps MCP
  • Clay MCP
  • Contentsquare MCP

Search & Web

  • Web Scrapper
  • Firecrawl
  • Apify
  • Perplexity
  • Context.dev
  • Exa
  • Brave Search
  • Apify MCP
  • Ahrefs MCP
  • DeepWiki MCP
  • Dice MCP

Communication

  • Gmail
  • Google Meet
  • Mailchimp
  • Google Calendar
  • WhatsApp
  • Slack
  • OneSignal MCP
  • Brevo Docs MCP
  • Carbon Voice MCP

© 2026 MewCP. All rights reserved.

  1. Home
  2. MCPs
  3. Dice MCP
Dice MCP

Dice MCP Integration for AI Agents

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.

v1.0.04 calls3 toolsNo auth
Open in ChatGPTChatGPT
Open in ClaudeClaude
Playground
VS CodeVS Code
Connected to Dice MCP via MewCP.

Encrypted at rest, isolated from the model

Resolved from an AES-256-GCM vault at the moment of the call and attached to the request — the model never sees the secrets.

Try asking

Everything Dice MCP can do

Tools3

search_jobs

read

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

get_job_details

read

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

get_company

read

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

Connect Dice MCP to your agent

One endpoint, the same key, whichever client you use.

Apps

SDKs

Claude Desktop

Claude Desktop

~/Library/Application Support/Claude/claude_desktop_config.json (Mac) · %APPDATA%\Claude\claude_desktop_config.json (Windows)

JSON
{
  "mcpServers": {
    "mewcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://gateway.mewcp.com/personal/mcp",
        "--header",
        "Authorization: Bearer API_KEY"
      ]
    }
  }
}

Replace API_KEY with your own key.

Already have an "mcpServers" section in your config? Just add the server entry inside it.

  1. 01Open Claude Desktop → Settings → Developer → "Edit Config"
  2. 02Paste the snippet inside the outer { } of the config file (merge with your existing "mcpServers" section if you have one)
  3. 03Save the file and restart Claude Desktop
  4. 04Start a new conversation — your tool will be available

One endpoint. Every service.

VS CodeAny agent
One Gateway

Firecrawl

API Key

Web Scrapper

No auth

Google Calendar

OAuth

Dice MCP

No auth

Discovery, routing, credentials, tool scoping and execution logs all happen at the gateway→connections stay ACTIVE with no work from you

Separate connections░░░░░░░░░░░░░░░░░░░░░░░░░░░░42 tool definitions ~28k tokensWith MewCP░░░░░░░░░░░░░░░░░░░░░░░░░░░░4 meta-tools ~8.3k tokens

Built for AI agents

Dice MCP runs through a gateway that holds the credentials, scopes the access and records every call.

Nothing to connect

  • Dice MCP needs no credential, so there is no key to issue, store or rotate.
  • Add it to a toolset and start calling tools.

Credentials stay out of context

  • Dice MCP credentials are resolved at the gateway and attached to the outbound call.
  • The agent sees tool results, never a token.

Ready to connect Dice MCP?

Managed auth, hosted MCP servers, and every Gmail tool your agent needs.

Free to start.

  • Revoke an account and the next call stops working — no redeploy.
  • Scoped access, fully logged

    • Choose exactly which Dice MCP tools an agent is allowed to call.
    • Every call is logged with its outcome, latency and which account it ran as.
    • Catalog changes are reviewed before they ship, so tool descriptions cannot shift under you.

    One endpoint for every server

    • Reach Dice MCP through the same MCP endpoint as the rest of your toolset.
    • Tools are discovered on demand, so 3 tools do not fill the context window.
    • Stateless: no sessions to keep alive and no reconnect logic.