BoardWise MCP Server

The BoardWise MCP server is a hosted, read-only connector aimed at a narrow but badly underserved audience: nurses, physicians, therapists, engineers, accountants and other licensed professionals who have just opened an envelope from their state licensing board. It runs at https://uakozrqrztgrgwoywxkx.supabase.co/functions/v1/mcp-server over Streamable HTTP, so nothing gets installed locally — you authorize once through OAuth and your assistant can pull jurisdiction-specific procedure into the conversation.

What it does

A board complaint is a procedural problem before it is anything else. There is a clock, a required form of response, an investigator, and a set of options that differ by state and by profession. Most people in that position do not have a lawyer on retainer and do not know which of the dozens of PDFs on a board's website actually applies to them. BoardWise exists to close that gap: it hands the model structured, jurisdiction-tagged material so the answer you get is anchored to the board that actually sent the letter, rather than to a generic blog post about a different state.

The project is deliberately conservative about scope. It presents itself as educational, it does not hold itself out as counsel, and the connector is read-only — nothing it exposes files anything, contacts anyone, or changes a record. That framing is not marketing hedging; it shapes what the tools return.

Key capabilities

• Deadline and timeline context — the response window, extension practice, and downstream milestones that attach to a particular board and complaint type.
• Response scaffolding — a structured outline for a written reply, organized around the allegations and the questions the board actually posed.
• Curated educational material — vetted background on investigations, informal conferences, consent orders, and hearings, filtered to the relevant jurisdiction.
• Procedural orientation — plain-language explanation of who the investigator is, what happens after a response is filed, and where the decision points sit.
• Read-only by design — no write path, no submissions, no data leaving on your behalf.

When to use it

Reach for BoardWise in the first 72 hours after a complaint notice arrives, when the most valuable thing is knowing what the clock is and what shape the response should take. It is also useful for compliance officers and practice managers who field these questions across a team and want a consistent starting point. It is not a substitute for a licensing-defense attorney, and you should not treat its output as a filing. If the matter involves a criminal referral, an emergency suspension, or anything with your ability to practice on the line next week, the correct use of this server is to help you brief a lawyer faster — not to replace one.

Compared with a general legal-research connector, BoardWise trades breadth for fit. Broad legal tools will happily answer questions about civil procedure or case law; BoardWise only knows one problem, and it knows the administrative-law corner of it that generalist tools tend to flatten. If your question is not about a licensing board, this is the wrong server.

Honest caveats

The server is small and independently run, hosted on Supabase Edge Functions rather than on a vendor's own infrastructure — treat availability accordingly. Coverage depth varies by state and profession; some boards publish detailed procedural rules and some publish almost nothing, and the connector cannot conjure what does not exist. There is no published tool schema or source repository, so you are trusting the operator's description of what the endpoint returns. Finally, everything it produces is educational context, not advice, and the model on the other end can still be wrong about your specific facts.