@dyeoman2
Basic information
A production-ready template for building Model Context Protocol (MCP) servers with Clerk authentication on Cloudflare Workers
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.
A production-ready template for building Model Context Protocol (MCP) servers that integrate Clerk authentication with Cloudflare Workers. It provides a complete OAuth 2.0 flow, Durable Objects for session state, and KV storage for temporary OAuth sessions. Designed for developers who want to connect their existing Clerk-authenticated applications to Claude AI through secure MCP tools.
Clone the repository, run npm install, configure environment variables (CLERK_SECRET_KEY, CLERK_PUBLISHABLE_KEY, APP_URL) in a .dev.vars file, create a KV namespace with Wrangler, update the namespace ID in wrangler.jsonc, and start the development server with npm run dev. Requires Node.js 22+, a Clerk account, a Cloudflare account with Workers enabled, and an existing application using Clerk for authentication.
It bridges your existing Clerk-authenticated application with Claude AI through MCP tools. Unlike generic MCP servers, it provides a ready-made OAuth flow and session management tailored for Clerk, reducing integration effort.
You need Node.js 22+, a Clerk account with API keys, a Cloudflare account with Workers enabled, and an existing application that uses Clerk for authentication.
OAuth session data is stored temporarily in Cloudflare KV. MCP session state is managed in Durable Objects. All application data remains in your existing Clerk-powered application.
The server uses SSE (Server-Sent Events) transport and OAuth 2.0 authentication with Clerk. JWT tokens are used for API requests, and state parameters are protected with HMAC signatures.
The README does not list hard limits, but the template relies on Cloudflare Workers and Durable Objects – scale and performance depend on those platforms. OAuth sessions in KV expire automatically.
Automated codebase documentation for GitHub: searchable docs, MCP context for AI agents, doc drift detection, and Friday Cleanup PRs.
SSH MCP server for AI agents: remote commands, file transfer, log search and server audits through OpenSSH.
Extentos is a multi-vendor development platform for adding smart-glasses capabilities to existing iOS and Android apps. The simplest analogy is Stripe for smart glasses:
Nebelus is an enterprise agentic-AI platform for regulated industries. This MCP server exposes the Nebelus Construction API: ~48 tools that give an MCP client full agent build parity — create/update/probe agents, edit ag
Comments