Ve Next.js

You run an MCP (Model Context Protocol) server built on Next.js with integrated Clerk authentication and per-user API keys. This setup lets authorized users sign in, manage their own API keys, and perform MCP requests securely with fine-grained access control.

How to use

You interact with the server using an MCP client that sends authenticated requests to the server’s API endpoint. Sign in with a Clerk-managed account to access the dashboard where you create and manage your API keys. When you have a valid key, include it in your requests as a Bearer token in the Authorization header.

Key advantages include user-isolated API keys, scoped permissions, and the ability to manage access per user. Use the dashboard to generate keys for MCP access, revoke keys as needed, and monitor active keys and their permissions.

How to install

Prerequisites: you need Node.js installed on your system to run the server in development mode.

Follow these steps to set up locally:

# Step 1: Clone the project
git clone [repository-url]

# Step 2: Enter the project directory
cd ve-nextjs-mcp-server

# Step 3: Install dependencies
npm install

# Step 4: Configure Clerk
# Create Clerk account and application, disable sign-ups, and copy environment variables to .env.local

Security and access control

Security is built around sign-in-only access, admin-controlled user management, and user-isolated API keys. Keys are scoped to a user and can be restricted by permissions to ensure only intended actions are allowed.

To safeguard your credentials, keep your API keys secret and rotate keys periodically. Use the dashboard to revoke compromised keys and review active permissions.

Usage example pattern

After you have an API key, you make requests to the MCP endpoint by including your key in the Authorization header as a Bearer token. Use the server’s API to perform MCP actions that your key is authorized for.

Notes on access and endpoints

The server exposes an MCP endpoint at the HTTP API path you use to send authenticated requests. You can access the local dashboard at the standard development URL once the server is running.

Available tools

Authentication

Clerk-based sign-in controls access to the dashboard and API, ensuring only authorized users can obtain and manage API keys.

API Key Management

Users can create, view, and revoke per-user API keys from the dashboard, with keys scoped to user permissions.

MCP Endpoint

The server provides an MCP HTTP endpoint for authenticated RPC-style requests initiated by MCP clients.