DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to give Crush extra tools with MCP servers with Crush

Add an MCP server such as GitHub in crushrc so the agent can use more tools.

Short answer: Install Crush; then add an MCP server in crushrc with mcp add, type http and the server URL, as in the README GitHub example; keep tokens out of the file by reading them from a secret manager, as the README does with 1Password. All steps.

Credentials. MCP servers often need API tokens; read them from a secret manager instead of writing them into crushrc.

Who it is forA developer who wants Crush to read issues and PRs or call other services while coding.

The problemA coding agent limited to your files cannot see issues, docs or services your work depends on.

The outcomeCrush with MCP servers over http, stdio or sse, configured once per project or globally.

What you need first

  • A terminal on macOS, Linux, Windows, Android or BSD
  • An LLM provider: Charm's Hyper subscription, an API key for Anthropic, OpenAI, Gemini or OpenRouter, or a local server such as Ollama

Steps

  1. Install Crush
  2. Add an MCP server in crushrc with mcp add, type http and the server URL, as in the README GitHub example
  3. Keep tokens out of the file by reading them from a secret manager, as the README does with 1Password
  4. Put project config in ./.crushrc or global config in ~/.config/crush/crushrc
  5. Ask Crush to use the new tools in your session

Prompt for your agent

Add the GitHub MCP server to charmbracelet/crush in my global crushrc, reading the token from my secret manager instead of hard-coding it, then ask Crush to summarize the open issues labeled bug in <repo>.

Caveat.

Use this in your AI agent

Ask your agent

Using the Deduped MCP, get the setup steps for charmbracelet/crush and "Give Crush extra tools with MCP servers"

Add Deduped to Claude Code once

claude mcp add --transport http deduped https://dedupedai.com/mcp

Cursor, ChatGPT, others

Share: X LinkedIn Hacker News Email Copy link

Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer