MCP Nexus Server

MCP Nexus Server provides a unified MCP endpoint that connects Tavily and Brave Search APIs, with admin controls, key rotation, and zero-cost deployment on Cloudflare Workers. This guide shows you how to use, install, and configure the MCP Nexus server for practical MCP workflows.

How to use

You can use MCP Nexus as your central MCP endpoint to access Tavily and Brave Search APIs through a single JSON-RPC interface. After deploying, you manage API keys and client tokens via the admin API, then configure your MCP client to send requests to the provided endpoint. Your client tokens authorize access, while Tavily and Brave keys authorize specific data sources.

How to install

Prerequisites you need before installing MCP Nexus: Node.js and npm, and a Cloudflare account with access to Workers.

# Install the Cloudflare Wrangler tool if you don\'t have it yet
npm install -g wrangler

Option A: One-Click Deploy This method creates a Cloudflare Workers project with a managed MCP Nexus server, and sets up required secrets automatically. Follow the prompts to authorize Cloudflare access and configure secrets.

Option B: Manual Deploy Clone the project, install dependencies, create a D1 database, and deploy with Wrangler. Use the included commands exactly as shown.

# Clone the repo
git clone https://github.com/ykq007/mcp-nexus.git
cd mcp-nexus/packages/worker

# Install dependencies
npm install

# Create D1 database
npx wrangler d1 create mcp-nexus-db
# Copy the database_id from output to wrangler.jsonc

# Set secrets
npx wrangler secret put ADMIN_API_TOKEN
npx wrangler secret put KEY_ENCRYPTION_SECRET

# Run migrations and deploy
npm run deploy

Post-deployment, you will add Tavily and Brave API keys, then create a client token for your MCP client.

Additional configuration and usage notes

MCP Nexus exposes an HTTP endpoint for clients to submit MCP requests. Use the MCP URL path /mcp for your RPC calls. Admin actions are available under the admin API endpoints to manage Tavily keys, Brave keys, and client tokens. The server stores data in D1 databases with encrypted keys and hashed client tokens for security.

Security considerations include encrypting stored API keys and rotating them as needed. You can manage admin access via an admin token and keep client tokens confidential. Regularly monitor usage logs through the admin API to detect unusual activity.

Troubleshooting and tips

If deployment fails, verify that Secrets ADMIN_API_TOKEN and KEY_ENCRYPTION_SECRET are correctly set and that the D1 database was created successfully. Check the deployment logs for any errors related to wrangler or the worker script.

When adding client keys or tokens, ensure you use the exact admin token in your Authorization header and provide valid JSON payloads. Save returned client tokens securely, as they are shown only once.

Tools available within MCP Nexus

MCP Nexus offers seven tools to interact with Tavily and Brave Search data sources.

Available tools

tavily_search

Search Tavily data using the MCP proxy and Tavily API integration.

tavily_extract

Extract structured data from Tavily responses for downstream processing.

tavily_crawl

Crawl Tavily sources to collect up-to-date information under MCP control.

tavily_map

Map Tavily results to standardized MCP data schemas.

tavily_research

Run Tavily-based research queries against the MCP endpoint.

brave_web_search

Perform Brave Web search via MCP proxy and route results to your client.

brave_local_search

Execute local Brave search tasks through the MCP server.