Claude Unblocked connectorWhat Claude can do in your Unblocked workspace.
The Claude Unblocked connector exposes 2 tools. Both read your organization's context, 0 write to it, and 0 lack a description. Here is what Claude goes looking for, what Unblocked needs before you connect, and who stays in control.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when a question spans several tools
An answer can depend on a pull request, an issue and a chat thread at once. You ask Claude, it goes through Unblocked, which searches those connected sources and returns a synthesized answer with its sources cited, while enforcing the permissions already set in each connected tool.
Find out why something was built that way. context_research researches across code, pull requests, documentation, issues and messaging, then returns a synthesized answer that cites its sources.
Trade speed for depth. The same tool takes an effort setting: the higher it goes, the more exhaustive the search across your connected sources, at the cost of a slower reply.
Open a link without leaving the chat. context_get_urls fetches the content behind one or more URLs from your connected services, whether an issue, a documentation page or a message thread, or a pull request. The URLs can be ones you provide or ones Claude comes across.
What Claude does not do here: neither documented tool changes anything in your tools, comments on an issue or posts a message. And nothing starts by itself, so no watcher runs when a new discussion appears. For that kind of trigger you need an automation tool, a different trade; Integrations gathers that side.
The vocabulary in one minute
Five words to follow the rest without detours.
- Connector
- The link you set up once between Claude and an account you already have, so it can work there while it answers you.
- Tool
- A named action the connector opens to Claude. Claude picks the ones it needs on its own; the directory sheet lists them.
- Authorization
- Unblocked's own sign-in screen, where you hand Claude the access it will use. You can take it back the same way.
- Approval
- The confirmation Claude waits for before an action that changes an account, shown in the chat right when it matters.
- MCP
- The shared standard behind connectors: it is what lets an assistant like Claude talk to an outside service.
Connect the Claude Unblocked connector
- 01
Find Unblocked
In Claude's settings, open Customize, then Connectors, and look for Unblocked. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it first so each member can connect.
- 02
Start the connection
Click Connect on its row, then sign in through the window Unblocked opens itself. If the link ever breaks, use Disconnect and connect again from the same row.
- 03
Read the authorization screen
Read the authorization screen before you approve. It belongs to Unblocked, not to Claude, and it decides what the access covers. Whatever you grant there can be withdrawn later.
The 2 tools in the Claude Unblocked connector
Unblocked gives Claude 2 tools: 2 that read your account, 0 that change something in it.
Two reading tools, both described by Unblocked. Tool names stay exactly as Claude shows them.
- 2 read
What Claude reads (2)
2 toolsTwo tools that look up your organization's context without changing it.
context_research
Runs a research query across code, pull requests, docs, issues and messaging, then returns a synthesized answer backed by citations.
context_get_urls
Fetches what sits behind one or more URLs you paste or that Claude runs into along the way: an issue, a documentation page, a message thread or a pull request.
What Claude asks before it acts
By default, Claude stops and asks for your go-ahead before every action it takes on an account for you. The request appears in the chat at the right moment.
By default, the Unblocked sheet exposes reading only: research and link fetching. On a Team or Enterprise workspace, owners decide whether a member may let some actions through without a new prompt, and they can cap what the connector does for the whole organization. Unblocked also says it enforces the permissions already set in each connected tool, so Claude reaches nothing you could not reach yourself.
Which plans it is available on
None of the 819 sheets in the official directory shows plan availability. That answer, connector by connector, is not published anywhere.
The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, and desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner switches the connector on for the organization before members connect. On Unblocked's side, a license is required. The current state is on the connector's sheet in the directory.
Where this connector stops
A connector is not an automation: Claude calls these tools while it answers you, and nothing fires on its own. Only Unblocked documents this connector, in its own docs.
A sheet that only shows reading is an observed floor: an admin can open actions no public page shows. The directory badge is not a security audit, and Anthropic says so on every sheet: it does not choose a publisher's tools and does not guarantee they behave as described. Connect what comes from a publisher you know. To chain actions without you, look at the automation tools gathered under Integrations.
Need help connecting Unblocked to Claude?
A person reads every message.
