ClaudeHack

#mcp

6 hacks

  1. 1.
    Use /usage to find which MCP tools and skills burn budget(code.claude.com)

    Inspect `/usage` (alias `/cost`) for per-skill, subagent, and MCP breakdowns, then cut the expensive outliers.

    0.00 points·14 hours ago·Usage & Limits·easy·discuss
  2. 2.
    Drive your local Claude Code session from your phone(code.claude.com)

    Run claude remote-control on your machine, then connect from the Claude mobile app to approve builds, poke CI failures, and keep coding with full local tools.

    0.00 points·14 hours ago·Terminal / Productivity / Cost Optimization·easy·discuss
  3. 3.
    Use /context to see what is eating your window(code.claude.com)

    Run /context to break down token consumers—CLAUDE.md, MCP tools, conversation—and prune the expensive ones.

    0.00 points·14 hours ago·Context Management·easy·discuss
  4. 4.
    Wire GitHub MCP so Claude can read issues while coding(code.claude.com)

    Add the GitHub MCP server so Claude can cross-reference issues, PRs, and repo state without leaving the session.

    0.00 points·14 hours ago·Git & GitHub / Pull Requests·medium·discuss
  5. 5.
    Run /doctor to trim duplicate CLAUDE.md and unused MCP cost(code.claude.com)

    Use the bundled /doctor skill to find duplicate local memory, unused MCP/plugins, and slow hooks eating budget.

    0.00 points·14 hours ago·Usage & Limits·easy·discuss
  6. 6.
    Disable unused MCP servers to reclaim startup tokens(code.claude.com)

    Turn off MCP servers unrelated to the current project—their tool schemas still consume context at session start.

    0.00 points·14 hours ago·MCP / Agents·easy·discuss