Get the FREE Ultimate OpenClaw Setup Guide →

pls-ignore-remote

MCP server from swyxio/pls-ignore-remote-mcp-server

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio swyxio-pls-ignore-remote-mcp-server npx nx dev remote-mcp-server

How to use

This MCP server provides a remote Model Context Protocol (MCP) API hosted via Cloudflare Workers with built-in OAuth login. It exposes an SSE endpoint at /sse that you can connect to with MCP tools (for example, the MCP Inspector) to discover, list, and invoke defined tools. You can run the server locally for development and testing, or deploy it to Cloudflare Workers for remote access. To connect Claude Desktop or other clients, point them to the server’s /sse endpoint and follow the prompts to authenticate and call tools. The server is designed to work with the MCP Inspector for exploration and with Claude Desktop for integrating tools into prompts, enabling remote tool usage over HTTP/SSE.

How to install

Prerequisites:

  • Node.js and npm/yarn installed
  • Git installed
  • Access to the repository (as needed for setup) or the ability to run npx-based commands

Local development (quick start):

  1. Clone the repository if needed:
  • git clone <repository-url>
  1. Install dependencies:
  • npm install
  1. Run the server locally (MCP development server):
  • npx nx dev remote-mcp-server
  1. Open the MCP UI or connect via MCP Inspector to the SSE endpoint at http://localhost:8787/sse

Deploy to Cloudflare Workers (summary):

  1. Create an OAuth KV namespace if required:
  • wrangler kv namespace create OAUTH_KV
  1. Add the KV namespace ID to wrangler.jsonc as instructed by the project docs

  2. Deploy the project:

  • npm run deploy

Notes:

  • The README suggests you can start a local instance using npx nx dev remote-mcp-server and connect tools via SSE at /sse.
  • If you plan to test with Claude Desktop, prepare the Claude config to point to the /sse endpoint of your local or remote server.

Additional notes

Tips and tips:

  • If you run into authentication issues, try clearing local MCP auth data: rm -rf ~/.mcp-auth
  • For debugging, you can directly test the SSE endpoint with commands like curl http://localhost:8787/sse to ensure the stream is active
  • When switching between local and remote deployments, update the Claude Desktop configuration to point to the correct /sse URL (local http://localhost:8787/sse vs. remote workers.dev URL)
  • The README demonstrates usage with the MCP Inspector and Claude Desktop; ensure your environment has access to npx and the required tools (e.g., mcp-remote) when wiring up clients
  • If you encounter port conflicts, verify that port 8787 (local) and the deployed Worker port ranges are available in your environment

Related MCP Servers

Sponsor this space

Reach thousands of developers