Dice MCP
for LuumenAI
Search Dice's tech-job database with conversational filters for role, company, location, and employment type.
Operate Dice MCP from the same conversation as the hosts it runs on. Check jobs, queues, and interfaces without a second console; run diagnostic reports; and restart or update with the change previewed, approved, and logged.
The Dice MCP toolbox
3 tools, all read-only. They answer instantly, and every call is logged.
- ReadGet companyRetrieve the name and description of the company behind a job, by job ID.
- ReadGet job detailsRetrieve a job's full description and associated skills by job ID.
- ReadSearch jobsSearch for job listings by keyword, location, and filters.
Questions
Dice MCP needs no credential of its own, so there is nothing to authorize. Access is still granted per agent, skill, and team inside Luumen, and every call is logged.
No. Every one of the 3 tools LuumenAI has for Dice MCP is read-only, so it can answer questions from Dice MCP but cannot change anything in it. Read actions still follow the configured access and approval policy, and are recorded on the audit trail.
You decide. Access is granted per agent, skill, and team, and per environment — production is not staging.
Every call to Dice MCP is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
SAP BTPGateways, jobs, and subaccounts operated from one governed chat.
SalesforceRecords and integration jobs checked without a second console.
SAP S/4HANAJobs, queues, and records in SAP S/4HANA without a second console.
SAP SuccessFactorsJobs, queues, and records in SAP SuccessFactors without a second console.Put Dice MCP to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.