Plugin · hr talent & recruitment
Groxbot + ZipRecruiter MCP
Search job listings across ZipRecruiter's marketplace by role, location, and salary.
How a Bot uses ZipRecruiter MCP
1 ZipRecruiter MCP tools. Connect under Plugins. The Bot still asks before anything leaves the thread.
- Use ZipRecruiter MCP the way you would: open it, do the task, come back with evidence.
- Work stays in the Bot thread. Anything leaving Groxbot needs your OK.
- If it hits a login, 2FA, or a paywall, it stops on the computer for you.
Never without you
- Change live ZipRecruiter MCP settings
- Message anyone outside the Bot thread
First message
Use ZipRecruiter MCP for this task. Stay in the thread. Stop if you would change anything live.
Tools a Bot can call
A sample from the ZipRecruiter MCP toolkit. The Bot calls these after you connect. Writes that would go live still wait for approval.
- Search jobs
Jobs that use ZipRecruiter MCP
- Talent scout — Source candidates from the brief. Never email anyone without approval. End with a shortlist and why.
- Bug reproduction — Reproduce the bug from the report. Write steps, expected vs actual, and a minimal fixture. Do not change production.
- Chief of staff — A source-linked digest of Slack, inbox, calendar, and notes — only the items that map to this week’s priorities. Does not send. Does not move meetings.
Related integrations
FAQ
Does Groxbot have a native ZipRecruiter MCP integration?
Connect ZipRecruiter MCP under Plugins when it is listed. If not, the Bot still has a real computer — it can work in ZipRecruiter MCP in the browser the way you would, then stop when it needs a login or approval.
Can a Bot change live ZipRecruiter MCP data?
Not by default. Groxbot is talk-first: draft in the thread, grant access when it hits a wall. Live ZipRecruiter MCP writes wait for you.
Do I need a workflow builder?
No. Create a Bot, message it, grant access as needed. There isn't anything to learn — it's like bringing on a coworker.