Skip to main content

Protect your MCP server with Clerk

Category
SDK
Published

Build MCP servers that follow the current MCP authorization spec, open chosen tools before sign-in, and publish Server Cards.

@clerk/mcp-tools 1.0.0, Clerk's improved MCP SDK, can now handle authorization for your MCP server end to end. Users sign in with Clerk, your server accepts only tokens issued for it, and clients get the challenges the current MCP authorization spec (revision 2026-07-28) expects.

To serve the 2026-07-28 protocol itself, use @modelcontextprotocol/server 2.3.0 or later.

What's new

  • Discoverable by default: anyone can connect to your MCP server and list its tools, but calling them still needs sign-in, so users sign in only when they reach something protected. Name the tools anyone can call with publicAccess, or set discoverable: false to keep the server fully private.
  • Audience-checked tokens: your server rejects tokens issued for another resource, even on the same Clerk instance.
  • Server Cards and AI Catalogs (beta): publish an MCP Server Card and an AI Catalog so clients and registries can discover your server. See Publish a Server Card and an AI Catalog.
  • Built-in feedback tool: submit_feedback now asks agents to report problems as soon as they find them, then continue the task.
  • Security floors: the MCP SDK peers now require versions with upstream security fixes, and MCP clients keep OAuth credentials bound to the authorization server that issued them.

Upgrading

1.0.0 is a breaking release:

  • MCP servers are discoverable by default: a client without an access token can connect and list your tools, resources, resource templates, and prompts, but calling them still needs sign-in. To require a token for every request, as in 0.9, set discoverable: false.
  • Exports drop the Clerk suffix, and the old names are gone with no aliases.
  • Clerk-verified tokens must carry your resourceUrl as their audience, and custom token verifiers get stricter checks.
  • The minimum Clerk SDK and MCP SDK versions go up.
  • Sessions stored by MCP clients before 1.0 must reconnect once.

To upgrade from 0.9, follow Upgrade to @clerk/mcp-tools 1.0.

To get started, see Build an MCP server and Allow public access to your MCP server before sign-in. For Hono, see the @clerk/mcp-tools/hono README.

Contributors
Wyatt Johnson
Bryce Kalow

Share this article