Interactive REPL for testing Model Context Protocol (MCP) servers
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"repl-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# MCP REPL [](https://pypi.org/project/repl-mcp/) [](https://github.com/kkokosa/repl-mcp/blob/main/LICENSE) [](https://pypi.org/project/repl-mcp/) Interactive REPL for testing Model Context Protocol (MCP) servers.  ## Features - List and inspect tools, prompts, and resources - Call tools with JSON or interactive parameter input - Tab autocompletion for commands and tool names - Command history (arrow keys) - Rich terminal UI with syntax highlighting ## Installation ### Option 1: Install from PyPI (Recommended) ```bash # Using uv (fast, Rust-based) uv tool install repl-mcp # Using pipx pipx install repl-mcp # Using pip pip install repl-mcp ``` ### Option 2: Run directly without installing ```bash # Using uvx uvx repl-mcp -c "npx mcp-remote https://mcp.atlassian.com/v1/mcp" ``` ### Option 3: Development Setup ```bash git clone https://github.com/kkokosa/repl-mcp.git cd repl-mcp pip install -e . ``` ## Usage > [!NOTE] > `mcp-remote` sidenote - Some MCP servers (like Atlassian) use OAuth for authentication and don't support direct HTTP connections. The `mcp-remote` MCP bridges this gap by handling OAuth flows locally and/or converting HTTP-based MCP servers to stdio transport. Beware that for OAuth-based servers, `mcp-remote` needs to receive the OAuth callback. If you're running in an environment without a public URL (like WSL or a remote server), you'll need a tunneling tool like [ngrok](https://ngrok.com/) to expose the callback endpoint. ### Stdio Transport (command-based) ```bash # Remote MCP server via mcp-remote repl-mcp -c "npx mcp-remote https://mcp.atlassian.com/v1/mcp" # Local Python MCP server repl-mcp -c "python my_mcp_server.py" # Using uvx repl-mcp -c "uvx mcp-server-sqlite --db-path test.db" ``` ### HTTP Transport (UR…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.