MCP stdio adapter

Created By
jrderuitera year ago
Expose a remote MCP server (HTTP) as a local stdio MCP server.
Overview

what is MCP stdio adapter?

MCP stdio adapter is a tool that allows you to expose a remote MCP server (HTTP) as a local stdio MCP server, making it useful for applications that only support stdio, such as Zed.

how to use MCP stdio adapter?

To use the MCP stdio adapter, you can run the proxy from the command line by setting the SERVER_ADDRESS environment variable to your MCP server's address and executing the command. Alternatively, you can use Docker to run the adapter.

key features of MCP stdio adapter?

  • Exposes remote MCP servers as local stdio servers
  • Supports command line and Docker usage
  • Easy integration with applications like Zed

use cases of MCP stdio adapter?

  1. Connecting local applications to remote MCP servers.
  2. Facilitating development in environments that require stdio.
  3. Running remote server commands seamlessly in local editors.

FAQ from MCP stdio adapter?

  • Can I use this adapter with any remote MCP server?

Yes, as long as the server supports HTTP streaming.

  • Is there a Docker version available?

Yes, you can run the adapter using Docker with the provided commands.

  • How do I configure it in Zed?

You can add the context_servers entry in your Zed settings file as described in the documentation.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
jrderuiter
Star
0
Language
Dockerfile
License
-

Recommend Servers

View All
Voyei

6 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago