@clerk
Basic information
Tools for building modern & secure MCP integrations across the client and server side
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
MCP Tools is a library built on top of the MCP TypeScript SDK that simplifies adding OAuth-based authentication to both MCP clients and servers. It is designed for developers who want to let AI applications (like Claude or ChatGPT) access user-protected data (e.g., emails, private repos) after obtaining explicit permission.
Install the @clerk/mcp-tools package. For a server, use generateProtectedResourceMetadata to expose a .well-known/oauth-protected-resource endpoint and framework-specific adapters (Express.js, Next.js) to create an MCP request handler. For a client, use createDynamicallyRegisteredMcpClient to initiate an OAuth flow, completeAuthWithCode to handle the callback, and pass a persistent store adapter (e.g., file system, Redis). Then call MCP tools with callTool after reconnecting via getClientBySessionId.
MCP Tools wraps the SDK with pre-built helpers for the OAuth authorization flow required by the MCP spec. It handles protected resource metadata generation, authorization server metadata, and OAuth callback orchestration, reducing boilerplate.
It requires Node.js and the MCP TypeScript SDK. For authentication, it can work with any OAuth 2.0 provider; integration with Clerk is optional but has dedicated helpers. The client side also needs a persistent store (file system for development, Redis for production).
Session data is stored externally via a pluggable store adapter. The library provides built-in file system (for dev) and Redis (for production) stores. You can also implement a custom store.
MCP Tools relies on the HTTP/Streamable HTTP transport defined by the MCP spec. The framework-specific adapters (Express.js, Next.js) handle the underlying request/response objects.
Yes, it supports the latest draft spec with OAuth 2.0 dynamic client registration. The older "authorization server metadata" approach is provided as a fallback but is not fully implemented yet.
A curated list of references for MLOps
Model Context Protocol Servers
Connect your AI assistant to your own YOUB endurance training account. Read recorded activities with full analysis, planned sessions, race goals, wellness (HRV, sleep, resting HR) and your athletic profile. Create or mov
AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents
This open-source curriculum introduces the fundamentals of Model Context Protocol (MCP) through real-world, cross-language examples in .NET, Java, TypeScript, JavaScript, Rust and Python. Designed for developers, it focuses on practical techniques for building modular, scalable,
Comments