Claude Dice connectorWhat Claude can do in your Dice account.
The Claude Dice connector exposes 1 tool. That single tool reads, 0 write anything, and 0 are left undocumented. Below: what Claude can search in Dice's tech job board, what it will not do for you, and who decides whether it is switched on.
Verified Trustpilot reviews · AI, automation & growth agency
What changes once Claude can search Dice
Instead of stacking filters on a job board, you describe the role you want and Claude runs the search for you. It queries Dice's listings of active tech jobs, then brings back the postings, the company behind each one and the link to apply, so you can narrow things down by simply replying.
A shortlist from one sentence. Ask for remote data engineering roles near Austin and Claude calls search_jobs with a keyword, a place and the right filters. Each result comes back with its job details, company information and application links.
Fresh postings only. Dice's documentation lists a recency filter of 1, 3 or 7 days, plus workplace options (Remote, On-Site, Hybrid). Handy when last month's results are already stale.
Refine by talking. Too many on-site roles? Say so, and Claude reruns the same tool with tighter criteria instead of making you start over.
Now what it will not do. The tool is built for finding jobs, and the publisher's own instructions to Claude rule out applying, submitting an application or making a hiring decision. Claude also works only while it answers you: no search runs on its own when a new posting appears, so there is no alert. A recurring job digest belongs to an automation tool, which does a different job; the Integrations hub covers that side. To compare with a connector that does change an account, see the Claude affinity connector page.
Four words to know before you start
Claude's vocabulary around this connector, in one short read.
- Connector
- The link you set up once between Claude and a service, so Claude can use that service while it answers you.
- Tool
- One named action the connector gives Claude. Claude chooses it by itself mid-answer; the directory lists every tool by name.
- Approval
- The confirmation Claude waits for before doing something that changes an account, shown in the conversation when it matters.
- MCP
- The shared standard connectors are built on, the thing that lets an assistant such as Claude talk to an outside service like Dice.
Connect Dice to Claude in three steps
- 01
Find Dice in your settings
Open Claude's settings, go to Customize, then Connectors, and look Dice up in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it before members can connect.
- 02
Start the connection
Click Connect on the Dice row. If the service opens its own window, go through it there. Should the link ever break, use Disconnect and connect again; that is the official fix.
- 03
Check what you grant
If an authorization screen appears, read it before accepting. It belongs to the service, not to Claude, and it is what sets the reach of the access. Dice's page adds that no authentication is needed for basic use.
The 1 tool, and what it covers
Dice gives Claude 1 tool: 1 that read your account, 0 that change something in it.
Tools are grouped by what they do. The name stays exactly as Claude shows it.
- 1 read
What Claude reads (1)
1 toolOne tool that looks at Dice's listings and changes nothing.
search_jobs
Runs a keyword search across Dice's tech job listings, optionally narrowed by location and filters, and returns each match with its details, company information and the links to apply.
What Claude checks with you first
By default, Claude stops and asks before each action it takes on an account on someone's behalf. A plain search changes nothing, which is why no source attaches a confirmation to it.
On Team and Enterprise workspaces, owners decide whether members may let some actions pass without a prompt each time. They can also restrict what a connector may do across the organization, and that setting binds everyone. Claude works with the rights of the connected person and nothing beyond. The per-tool label of read only versus write lives in a signed-in account's settings, not on any public page.
Which plans can use it
None of the 819 sheets in the official directory states plan availability. For Dice, as for every other connector, that answer is published nowhere.
The general rule is what is documented: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables a connector for the organization before members can connect. For Dice's current state, check its sheet in the official directory, the only place that keeps it up to date.
Where this connector stops
A connector is not an automation. Claude calls the search while it answers you, so nothing fires when a new role goes live.
One tool reading is an observed floor, not a guarantee: an administrator can open actions that no public sheet shows. The partner badge in the directory is not a security audit, and Anthropic states on every sheet that it neither picks the tools a publisher exposes nor vouches for how they behave. Everything known about this connector comes from Dice itself, as no Claude help article covers it, so read its documentation before relying on a detail.
Need help connecting Dice to Claude?
A person reads every message.
