Claude BoardWise connectorWhat Claude can do in your BoardWise account.
The Claude BoardWise connector exposes 4 tools. 3 of them read BoardWise's educational material, 0 write anything, and 1 stays undocumented by any official source. Here: what Claude can look up for a nurse, pharmacist or driver facing a board, and where it stops.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can draw on BoardWise
A state licensing-board matter, from a complaint to a hearing notice, comes with response deadlines that depend on the jurisdiction. With BoardWise connected, a licensed professional can describe the situation to Claude in plain words and get structured, educational material back: an outline for the reply, the relevant guides, and resources matched to the type of matter.
A skeleton for the reply letter. Through get_response_letter_guidance, Claude can build a structured outline for a response to the board, which the professional then fills with their own facts.
The right guide, not the whole library. find_relevant_guide searches BoardWise's collection of educational guides, so a social worker facing a complaint reads the guide that fits instead of browsing.
Resources by situation. get_resources surfaces curated material for complaints, continuing-education audits, consent agreements, hearing notices and self-reports.
What it will not do: BoardWise says everything it returns is general educational information, not legal advice, and it does not take in personal or case data. Claude does not file anything with a board, and nothing runs unless you ask. To see how other connectors handle real account data, the Integrations hub gathers every family covered here.
Five terms, one minute
The words Claude uses around connectors, defined once for this page.
- Connector
- The link you set up once between Claude and an outside service, so Claude can call on it while it answers you.
- Tool
- A single named capability the connector hands to Claude. Claude picks it on its own, and the directory sheet lists each one by name.
- Authorization
- The service's own sign-in screen, where you grant Claude the access it will use afterwards. It is given per person and can be withdrawn.
- Approval
- The check Claude waits for before doing something that changes an account, displayed in the chat at the point it matters.
- MCP
- The shared standard behind connectors: it is what lets an assistant such as Claude exchange with an outside service like BoardWise.
Connect BoardWise to Claude in three steps
- 01
Find BoardWise in the list
Open Claude's settings, then Customize and Connectors, and look for BoardWise. On a Team or Enterprise workspace, an Owner or Primary Owner has to turn the connector on for the organization before any member can sign in to it.
- 02
Launch the connection
Press Connect on the BoardWise row and complete the window the service opens. Should the link break later, Disconnect it and connect again; that is how Claude expects a damaged connection to be repaired.
- 03
Check the authorization
If BoardWise shows an authorization screen, read it before approving. The screen comes from the service, not from Claude, and it defines what the access covers from then on.
The 4 tools of the Claude BoardWise connector
BoardWise gives Claude 4 tools: 3 that read your account, 0 that change something in it, and 1 no official source describes.
Three tools are tied to a capability BoardWise describes on its directory sheet; the fourth is only named. Tool names stay as Claude displays them.
- 3 read
- 1 not documented
What Claude reads (3)
3 toolsThree tools that pull educational material from BoardWise without changing anything.
get_response_letter_guidance
Gives Claude a structured outline for a letter answering a licensing board, so the reply starts from a clear frame instead of an empty page.
find_relevant_guide
Searches the BoardWise library of educational guides and brings back the ones that match the situation you describe, so Claude can work from the relevant text.
get_resources
Surfaces material BoardWise has selected for typical board matters: complaints, CEU audits, consent agreements, hearing notices and self-reports.
Not documented (1)
1 toolA tool whose name appears on the sheet but that no official source describes. Its effect is unknown, so it is not explained here.
get_board_guidance
No official source describes this tool: the directory sheet publishes its name and nothing more, and BoardWise links no page that explains it. Its effect is therefore not stated here. Like any tool, it falls under the general approval rule described further down.
What Claude asks you first
By default, Claude pauses and asks for confirmation before each action it carries out on an account for someone, right in the conversation.
BoardWise describes its service as read-only and educational, so the three documented tools have nothing to change. On Team and Enterprise workspaces, owners choose whether members may let certain actions pass without a prompt each time, and they can cap what a connector may do for the whole organization, a setting nobody overrides from their own account. Claude also works only with the rights of the person who connected. No source says whether a prompt appears for the undocumented tool.
Which plans include BoardWise
No official source publishes plan availability connector by connector: 0 of the 819 sheets in the directory shows it, and that hole is real.
What exists is the general rule. Remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile; desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner opens a connector for the organization before members can connect. The BoardWise sheet in the official directory is the only place showing its current state. Note that this connector is documented by its publisher alone, through that sheet.
Where the connector stops
A connector is not an automation. Claude calls these tools while it answers you, so nothing reacts by itself when a board letter lands in your mailbox.
By default, the sheet exposes only reading, which is an observed floor and not a guarantee: an administrator can open actions that no public sheet lists. The partner badge is not a security audit, and Anthropic notes on every sheet that it does not choose the tools a publisher exposes nor guarantee their behavior. Connect only what comes from a publisher you trust. For a connector built around a real business account, see the Claude adobe-workfront connector.
Need help connecting BoardWise to Claude?
A person reads every message.
