Model Context Protocol (MCP) Server + Clerk OAuth

This is a Model Context Protocol (MCP) server that supports remote MCP connections, with Clerk OAuth built-in.

You can deploy it to your own Cloudflare account, and after you create your own Clerk OAuth application, you'll have a fully functional remote MCP server that you can build off. Users will be able to connect to your MCP server by signing in with Clerk.

You can use this as a reference example for how to integrate other OAuth providers with an MCP server deployed to Cloudflare, using the workers-oauth-provider.

The MCP server (powered by Cloudflare Workers):

• Acts as OAuth Server to your MCP clients

• Acts as OAuth Client to your real OAuth server (in this case, Clerk)

Getting Started

Clone the repo directly & install dependencies: npm install.

Alternatively, you can use the command line below to get the remote MCP Server created on your local machine:

For Production

Create a new Clerk application and OAuth configuration:

1. Sign up or log in at Clerk Dashboard

2. Create a new application

3. Go to OAuth Applications and create a new OAuth application

4. Set the redirect URI to: https://mcp-clerk-oauth.<your-subdomain>.workers.dev/callback

5. Note your Client ID and Client Secret

6. Get your Secret Key from API Keys (starts with sk_live_)

7. Note your Frontend API URL (e.g., https://your-subdomain.clerk.accounts.dev)

Set secrets via Wrangler:

Set up a KV namespace

• Create the KV namespace: wrangler kv namespace create "OAUTH_KV"

• Update the Wrangler file with the KV ID

Deploy & Test

Deploy the MCP server to make it available on your workers.dev domain wrangler deploy

Test the remote server using Inspector:

Enter https://mcp-clerk-oauth.<your-subdomain>.workers.dev/mcp (or /sse for deprecated protocol) and hit connect. Once you go through the authentication flow, you'll see the Tools working:

You now have a remote MCP server deployed!

Access Control

This MCP server uses Clerk OAuth for authentication. All authenticated users can access basic tools like "add" and "userInfo".

The "generateImage" tool is restricted to specific roles using role-based access control (RBAC):

To set a user's role in Clerk Dashboard:

1. Go to Users → select a user

2. Click on Metadata tab

3. Under Public metadata, add: {"role": "admin"}

4. Save changes

Access the remote MCP server from Claude Desktop

Open Claude Desktop and navigate to Settings -> Developer -> Edit Config. This opens the configuration file that controls which MCP servers Claude can access.

Replace the content with the following configuration. Once you restart Claude Desktop, a browser window will open showing your OAuth login page. Complete the authentication flow to grant Claude access to your MCP server. After you grant access, the tools will become available for you to use.

Once the Tools (under 🔨) show up in the interface, you can ask Claude to use them. For example: "Could you use the math tool to add 23 and 19?". Claude should invoke the tool and show the result generated by the MCP server.

For Local Development

If you'd like to iterate and test your MCP server, you can do so in local development:

1. In Clerk Dashboard, update your OAuth application's redirect URI to include http://localhost:8788/callback

2. Copy .env.example to .env and fill in your Clerk credentials:

Develop & Test

Run the server locally to make it available at http://localhost:8788

To test the local server, enter http://localhost:8788/mcp (or /sse for deprecated protocol) into Inspector and hit connect. Once you follow the prompts, you'll be able to "List Tools".

Using Claude and other MCP Clients

When using Claude to connect to your remote MCP server, you may see some error messages. This is because Claude Desktop doesn't yet support remote MCP servers, so it sometimes gets confused. To verify whether the MCP server is connected, hover over the 🔨 icon in the bottom right corner of Claude's interface. You should see your tools available there.

Using Cursor and other MCP Clients

To connect Cursor with your MCP server, choose Type: "Command" and in the Command field, combine the command and args fields into one (e.g. npx mcp-remote https://<your-worker-name>.<your-subdomain>.workers.dev/sse).

Note that while Cursor supports HTTP+SSE servers, it doesn't support authentication, so you still need to use mcp-remote (and to use a STDIO server, not an HTTP one).

You can connect your MCP server to other MCP clients like Windsurf by opening the client's configuration file, adding the same JSON that was used for the Claude setup, and restarting the MCP client.

How does it work?

OAuth Provider

The OAuth Provider library serves as a complete OAuth 2.1 server implementation for Cloudflare Workers. It handles the complexities of the OAuth flow, including token issuance, validation, and management. In this project, it plays the dual role of:

• Authenticating MCP clients that connect to your server

• Managing the connection to Clerk's OAuth services

• Securely storing tokens and authentication state in KV storage

Durable MCP

Durable MCP extends the base MCP functionality with Cloudflare's Durable Objects, providing:

• Persistent state management for your MCP server

• Secure storage of authentication context between requests

• Access to authenticated user information via this.props

• Support for conditional tool availability based on user identity

MCP Remote

The MCP Remote library enables your server to expose tools that can be invoked by MCP clients like the Inspector. It:

• Defines the protocol for communication between clients and your server

• Provides a structured way to define tools

• Handles serialization and deserialization of requests and responses

• Maintains the Server-Sent Events (SSE) connection between clients and your server