Skip to content

docs(clients): add a Zed guide and make the HTTP-mode setup self-contained - #200

Open
adityamparikh wants to merge 1 commit into
apache:mainfrom
adityamparikh:docs/clients-zed-http
Open

adityamparikh wants to merge 1 commit into
apache:mainfrom
adityamparikh:docs/clients-zed-http

Conversation

@adityamparikh

Copy link
Copy Markdown
Contributor

Summary

Docs only. Three gaps in the client guides, fixed in both docs/clients/ and the site mirror under docs/site/content/pages/mcp/clients/:

  • Zed had no guide. New zed.md covers the settings form and settings.json for STDIO (JAR and Docker) and the remote-server entry for HTTP, plus the two things that bite in practice: the schema takes command/args/env with no source key (verified on Zed 1.16.2), and the 60 s start timeout that a first Docker pull can outrun. Listed in README.md, the client index and the site quick start.
  • HTTP Mode sections assumed the reader knew about security. Each now states that the transport is secured by default and answers 401 until an OAuth2 issuer is configured, and names HTTP_SECURITY_ENABLED=false for a local experiment with a pointer to the security docs.
  • Claude Desktop guide did not say why it uses mcp-remote. It now explains that custom connectors are contacted from Anthropic's cloud (help center), so a localhost URL is unreachable through the Connectors screen and would need a public HTTPS endpoint with OAuth2 on; the bridge runs locally and needs no tunnel.

Verification

🤖 Generated with Claude Code

https://claude.ai/code/session_01CiUHyyXLTo9ATdgg8eRFZJ

…ained

Zed was the one client with no guide; it now has one in docs/clients and in
the site tree, covering the settings form and settings.json for STDIO (JAR
and Docker) and the remote-server entry for HTTP, with the schema and
timeout notes that came out of using it.

Every HTTP Mode section now says that the transport is secured by default
and answers 401 until an issuer is configured, and names the
HTTP_SECURITY_ENABLED=false escape hatch for a local experiment, so a
first-time reader is not left guessing why their client cannot connect.

The Claude Desktop guides explain why the Connectors screen is the wrong
route for a local server: custom connectors are contacted from Anthropic's
cloud, so localhost is unreachable there; the mcp-remote bridge runs
locally and needs no tunnel.

README and the client index list Zed alongside the other clients.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CiUHyyXLTo9ATdgg8eRFZJ
Signed-off-by: Aditya Parikh <aditya.m.parikh@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant