Add instructions about disabling mcp

[mrubens]

Important

Adds instructions for disabling MCP features in mcp.md and updates rate-limits-costs.md with a related tip.

• Documentation:
  • Adds section "Disabling MCP Features" in mcp.md with instructions to disable MCP servers and server creation.
  • Updates rate-limits-costs.md to include a tip about disabling MCP to save tokens.

^{This description was created by for 20c34fa. It will automatically update as commits are pushed.}

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to 20c34fa in 1 minute and 20 seconds

More details

• Looked at 53 lines of code in 2 files
• Skipped 0 files when reviewing.
• Skipped posting 5 drafted comments based on config settings.

1. docs/advanced-usage/mcp.md:66

• Draft comment:
  Good addition for managing MCP features. Consider ensuring a newline at the end of the file for consistent formatting.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

2. docs/advanced-usage/rate-limits-costs.md:49

• Draft comment:
  Ensure the relative link disabling it in the MCP settings correctly points to the new section in mcp.md. This helps maintain accurate navigation between docs.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

3. docs/advanced-usage/mcp.md:66

• Draft comment:
  Clear instructions added for disabling MCP features are helpful. Consider adding a brief note about how disabling MCP may affect available functionalities, and if possible, reference the exact setting names as they appear in the UI for clarity.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

4. docs/advanced-usage/mcp.md:92

• Draft comment:
  Please ensure the file ends with a newline to conform to project style guidelines.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50%
  While having a trailing newline is a common convention, this is something that should be handled automatically by EditorConfig, Prettier, or similar tools rather than manual code review comments. According to our rules, we should not comment on things that should be handled by automated tools. Additionally, this is a very minor formatting issue that doesn't affect functionality.
  Perhaps maintaining consistent file formatting, even in documentation, is important for version control and diff readability?
  While file formatting consistency is important, it should be enforced through automated tools rather than manual review comments. This is exactly the kind of thing Prettier or EditorConfig should handle.
  Delete this comment as it addresses a minor formatting issue that should be handled by automated tools rather than manual review.

5. docs/advanced-usage/rate-limits-costs.md:49

• Draft comment:
  The added bullet regarding disabling MCP is clear and useful. Please verify that the link anchor './mcp#disabling-mcp-features' correctly navigates to the intended section in the MCP documentation.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

Workflow ID: wflow_HfOU45pV3kbBu7Lr

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.