adityamparikh opened a new pull request, #200:
URL: https://github.com/apache/solr-mcp/pull/200

   ### 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](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp)),
 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
   - `./gradlew build` on Java 25: 403 tests, 0 failures, 7 skipped (the OTLP 
suite, skipped on `main` until #198).
   - `./gradlew rat spotlessCheck` green on the final tree.
   - Zed instructions exercised against a running server in HTTP mode on the 
#196/#197 branches.
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   
   https://claude.ai/code/session_01CiUHyyXLTo9ATdgg8eRFZJ
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to