docs: add generic add-mcp setup instructions

[charliecreates]

Summary

• add a generic add-mcp setup section to README for non-Claude/Cursor clients
• add the new section to the README table of contents

Resolves #360

✨ PR Description

Purpose: Add documentation for generic MCP client setup using the add-mcp tool as an alternative to manual configuration.

Main changes:

• Added table of contents entry for "Other MCP Clients (via add-mcp)" section
• Documented add-mcp command with example showing hevy-mcp setup with environment variable configuration

Generated by LinearB AI and added by gitStream.
_{AI-generated content may contain inaccuracies. Please verify before using.
💡 Tip: You can customize your AI Description using Guidelines Learn how}

[gitstream-cm]

✨ PR Review

The PR adds a concise and useful section to the README for non-Claude/Cursor MCP clients. The TOC anchor is correctly formatted and the section is well-placed. One security concern with the example command is worth flagging.

1 issues detected:

🔒 Security - Passing secrets as inline command-line arguments exposes them in shell history and process listings. 🛠️

Details: The example command passes the API key inline as a command-line argument. This causes the secret to be stored in the user's shell history (e.g., ~/.bash_history, ~/.zsh_history) and can be visible in process listings (e.g., ps aux) for the duration of the command. Readers following this example literally may inadvertently expose their real API key.

File: README.md (130-130)

_{🛠️ A suggested code correction is included in the review comments.}

Generated by LinearB AI and added by gitStream.
_{AI-generated content may contain inaccuracies. Please verify before using.
💡 Tip: You can customize your AI Review using Guidelines Learn how}

[gitstream-cm]

🔒 Security - API Key Exposure: Revise the example to either omit the --env flag and instruct users to set the environment variable separately before running the command (e.g., export HEVY_API_KEY=your_api_key then npx add-mcp hevy-mcp), or use a clearly non-functional placeholder like YOUR_HEVY_API_KEY with a note warning against passing real keys directly on the command line.

Suggested change

	npx add-mcp hevy-mcp --env "HEVY_API_KEY=secret"
	export HEVY_API_KEY=your_api_key
	npx add-mcp hevy-mcp

Is this review accurate? Use 👍 or 👎 to rate it

If you want to tell us more, use /gs feedback e.g. /gs feedback this review doesn't make sense, I disagree, and it keeps repeating over and over

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 71.36%. Comparing base (e8a068c) to head (c4576a7).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #361   +/-   ##
=======================================
  Coverage   71.36%   71.36%           
=======================================
  Files          18       18           
  Lines         674      674           
  Branches      202      202           
=======================================
  Hits          481      481           
  Misses        110      110           
  Partials       83       83           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[greptile-apps]

Greptile Summary

• Adds a generic add-mcp setup section to README.md for MCP clients beyond Claude and Cursor.
• Adds the new setup path to the README table of contents.
• Documents an example command for configuring hevy-mcp with HEVY_API_KEY.

Confidence Score: 4/5

The README-only change is low risk, but the documented command should preserve the intended server name before merge.

The change is small and isolated to documentation, and the issue is limited to setup instructions rather than application runtime behavior.

README.md

T-Rex Logs

What T-Rex did

• I ran an isolated add-mcp harness with temporary HOME, XDG_CONFIG_HOME, and project directories to avoid altering real user config.
• The harness run showed the default, unnamed server key appeared as hevy in the generated .codex/config.toml under [mcp_servers.hevy].
• I re-ran the command with --name hevy-mcp and confirmed the generated config now contains [mcp_servers.hevy-mcp], aligning with the expected server key.
• I reviewed the README and confirmed a new Other MCP Clients via add-mcp section was added, including a TOC entry at line 20 and a heading anchored to #other-mcp-clients-via-add-mcp.
• I verified that the README's add-mcp link currently points to the old repository URL (https://github.com/neon-solutions/add-mcp) instead of the required https://github.com/delorenj/add-mcp.
• Artifacts documenting the harness and its outputs were captured as reproducibility artifacts.

_{Ran code and verified through T-Rex}

Comments Outside Diff (1)

1. General comment

   README links add-mcp to the wrong repository URL

   • Bug
     • The new generic MCP client setup section is present and its TOC anchor resolves, but the documented add-mcp repository URL does not match the requested contract. At head, README.md line 127 links [add-mcp] to https://github.com/neon-solutions/add-mcp; the validation contract requires https://github.com/delorenj/add-mcp to be present.
   • Cause
     • The README implementation used a different GitHub repository URL for the add-mcp link than the contract specified.
   • Fix
     • Change the add-mcp link target in README.md line 127 from https://github.com/neon-solutions/add-mcp to https://github.com/delorenj/add-mcp.

   _{Ran code and verified through T-Rex}

_{Reviews (1): Last reviewed commit: "docs: add add-mcp setup instructions to ..." | Re-trigger Greptile}

[greptile-apps]

Preserve server name

This command does not create the hevy-mcp entry described below it. add-mcp infers the server name as hevy for the hevy-mcp package, so users following this section get a different config key than the Claude and Cursor examples above. Passing --name hevy-mcp keeps the generated entry name consistent with the docs.

Suggested change

	```bash
	npx add-mcp hevy-mcp --env "HEVY_API_KEY=secret"
	```
	This bootstraps the `hevy-mcp` entry in your client config without manual JSON edits.
	```bash
	npx add-mcp hevy-mcp --name hevy-mcp --env "HEVY_API_KEY=secret"

This bootstraps the hevy-mcp entry in your client config without manual JSON edits.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

<details><summary><strong>Artifacts</strong></summary><br />

**[Repro: isolated add-mcp command harness](https://app.greptile.com/trex/artifacts/f1d87861-7ad4-4d19-833d-7c3afa6052e0)**

- Contains supporting evidence from the run (text/x-shellscript; charset=utf-8).

**[Repro: add-mcp output and generated config showing inferred and explicit server keys](https://app.greptile.com/trex/artifacts/6e67e97b-ca29-408c-a22a-9ecda6f4bc00)**

- Keeps the command output available without making the summary code-heavy.

<a href="https://app.greptile.com/trex/runs/11876853/artifacts?artifact=f1d87861-7ad4-4d19-833d-7c3afa6052e0"><picture><source media="(prefers-color-scheme: dark)" srcset="https://greptile-static-assets.s3.amazonaws.com/badges/ViewArtifactsDark.svg?v=1"><source media="(prefers-color-scheme: light)" srcset="https://greptile-static-assets.s3.amazonaws.com/badges/ViewArtifacts.svg?v=1"><img alt="View artifacts" src="https://greptile-static-assets.s3.amazonaws.com/badges/ViewArtifacts.svg?v=1" height="32"></picture></a>
</details>

<sub><a href="https://www.greptile.com/trex"><img alt="T-Rex" src="https://greptile-static-assets.s3.amazonaws.com/trex/trex_green.svg" height="14" align="absmiddle"></a> Ran code and verified through T-Rex</sub>