ZipRecruiter MCP
for LuumenAI
Search job listings across ZipRecruiter's marketplace by role, location, and salary.
Operate ZipRecruiter 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 ZipRecruiter MCP toolbox
1 tools: 0 read, 1 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- WriteSearch jobsUse this tool whenever the user asks to find, browse, view, recommend, or search for jobs, roles, openings, gigs, internships, or job listings. Approval by default
Questions
ZipRecruiter 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.
Read actions answer immediately. Anything that writes — search jobs — is shown as a plan and requires approval by default. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to ZipRecruiter MCP — read or write, approved or declined — 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 ZipRecruiter MCP to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.