run-mcp-local

Run the everyrow HTTP MCP server locally with Docker Compose and Redis.

51|6|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/futuresearch/everyrow-sdk --skill run-mcp-local
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-mcp-local
Source: https://github.com/futuresearch/everyrow-sdk/tree/main/.claude/skills/run-mcp-local
Command: npx skills add https://github.com/futuresearch/everyrow-sdk --skill run-mcp-local

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a clear, repeatable workflow to run the everyrow HTTP MCP server locally, avoid port conflicts, and expose a development instance for OAuth-based clients that cannot reach localhost. It prevents common developer pitfalls like stale host processes shadowing container ports, missing environment variables, and misconfigured tunnel settings that break OAuth discovery.

Core Features & Use Cases

  • Local orchestration: Guides developers to start the MCP server and Redis with Docker Compose and local overrides.
  • Tunnel support: Explains how to expose the local server via Cloudflare tunnel for testing Claude.ai, Claude Desktop, and remote OAuth flows.
  • Debugging & verification: Covers pre-flight checks, log inspection, OAuth discovery validation, and teardown procedures.
  • Use case: Run a full local MCP environment to test OAuth redirects, verify tool discovery, or debug integration with Claude clients before deploying to staging.

Quick Start

From the repository root, run the Docker Compose local stack in everyrow-mcp/deploy with REDIS_PASSWORD and MCP_SERVER_URL set so the server and Redis come up and the health endpoint returns 200.

Frequently Asked Questions about run-mcp-local

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I start the everyrow MCP server locally with Docker Compose?

To start the MCP server locally, run the Docker Compose stack in everyrow-mcp/deploy with REDIS_PASSWORD and MCP_SERVER_URL set, ensuring the server and Redis containers start and the health endpoint returns 200.

How do I expose my local MCP server for OAuth testing with Claude.ai?

Expose the local MCP server for OAuth testing by configuring a Cloudflare tunnel with cloudflared, enabling TRUST_PROXY_HEADERS so remote Claude.ai clients can reach the localhost development instance.

Why does my local MCP server fail to start or bind to port 8000?

The local MCP server fails to start if port 8000 is occupied by stale host processes shadowing container ports; verify the port is free during pre-flight checks before launching Docker Compose.

What environment variables are required to run the MCP server and Redis locally?

Running the MCP server and Redis locally requires explicit REDIS_PASSWORD and MCP_SERVER_URL configuration in Docker Compose to ensure proper orchestration and server health verification.

Can I use this local MCP setup to debug tool discovery and OAuth redirects in Claude Desktop?

Yes, the local MCP environment supports debugging tool discovery and OAuth redirects by allowing you to inspect logs, validate OAuth discovery endpoints, and test integration with Claude Desktop before staging deployment.

What's the best way to inspect logs and troubleshoot the local MCP server startup?

Troubleshoot MCP server startup by inspecting Docker Compose logs, verifying environment variable configuration, checking port 8000 availability, and validating the health endpoint response during pre-flight checks.