Full MCP Support

Tools for Claude Code

Empower Anthropic's CLI agent with a curated collection of MCP tools. Add capabilities in seconds with native MCP integration built right into the runtime.

Quick Setup

Two ways to add MCP tools to Claude Code. Both work out of the box with zero extra configuration.

CLI Command Recommended

Add any MCP server with a single command. Claude Code registers it immediately and the tools become available in your next conversation.

Terminal 
# Add a tool from the ClineTools registry
claude mcp add secret-scanner npx @clinetools/secret-scanner

# Add a tool with environment variables
claude mcp add db-client npx @clinetools/db-client \
  --env DB_URL=postgresql://localhost:5432/mydb

# Add a local tool from a file path
claude mcp add my-tool node /path/to/my-server/index.js

# List all registered MCP servers
claude mcp list

# Remove a tool
claude mcp remove secret-scanner
1 Run the claude mcp add command
2 Start a new Claude Code session
3 Claude automatically discovers and uses the tools

Config File Advanced

Edit the Claude Code config file directly for more control. Useful when managing multiple tools or sharing configurations across machines.

~/.claude.json 
{
  "mcpServers": {
    "secret-scanner": {
      "command": "npx",
      "args": ["@clinetools/secret-scanner"]
    },
    "db-client": {
      "command": "npx",
      "args": ["@clinetools/db-client"],
      "env": {
        "DB_URL": "postgresql://localhost:5432/mydb"
      }
    }
  }
}
1 Open ~/.claude.json in your editor
2 Add entries to the mcpServers object
3 Restart Claude Code to load the new servers

Recommended Tool Stacks

Curated combinations of tools that work brilliantly together. Install an entire stack in one go.

Security Stack

Comprehensive security scanning for every commit. Catch secrets, detect prompt injection, and audit MCP server permissions before they become problems.

Secret Scanner Detect leaked keys & tokens
Prompt Detector Find prompt injection risks
MCP Auditor Verify server permissions
Install all three 
claude mcp add secret-scanner npx @clinetools/secret-scanner
claude mcp add prompt-detector npx @clinetools/prompt-detector
claude mcp add mcp-auditor npx @clinetools/mcp-auditor

Code Quality Stack

Keep your codebase clean and maintainable. Measure complexity, find dead code, and track type coverage across every change Claude makes.

Complexity Analyzer Cyclomatic complexity scoring
Dead Code Detector Find unused exports & functions
Type Coverage TypeScript coverage reports
Install all three 
claude mcp add complexity npx @clinetools/complexity-analyzer
claude mcp add dead-code npx @clinetools/dead-code-detector
claude mcp add type-coverage npx @clinetools/type-coverage

Full-Stack Dev Stack

Everything Claude needs to build, run, and debug full-stack applications. File management, version control, containers, and database access all in one stack.

Filesystem Read, write, search files
Git Version control operations
Docker Container management
PostgreSQL Database queries & schema
Install all four 
claude mcp add filesystem npx \
  @modelcontextprotocol/server-filesystem /path/to/project
claude mcp add git npx @modelcontextprotocol/server-git
claude mcp add docker npx @clinetools/docker-manager
claude mcp add postgres npx @clinetools/postgres-client \
  --env DB_URL=postgresql://localhost:5432/mydb

Claude Code-Specific Tips

Get the most out of MCP tools with these Claude Code-specific techniques and best practices.

Use the /mcp command

Inside a Claude Code session, type /mcp to see the status of all connected MCP servers. It shows which tools are available, which servers are running, and any connection errors.

$ /mcp

MCP Servers:
  secret-scanner (running) - 3 tools
  db-client (running) - 5 tools
  git (running) - 8 tools

Automatic Tool Discovery

Claude Code automatically discovers tools from all connected MCP servers. You do not need to tell Claude which tools are available. Just describe what you want to do and Claude will select the right tool.

You: Scan this project for leaked API keys

Claude: I'll use the secret-scanner tool to check...
[Using secret_scanner.scan_directory]

Set Preferences in CLAUDE.md

Use your project's CLAUDE.md file to tell Claude when and how to use specific tools. This creates consistent behavior across sessions and team members.

# CLAUDE.md

## Tool Preferences
- Always run secret-scanner before commits
- Use complexity-analyzer on new files
- Check type-coverage after TypeScript changes

Direct Tool Usage Explicitly

While Claude auto-discovers tools, you can also explicitly request specific tools. Useful when you want a particular tool rather than letting Claude choose automatically.

You: Use the MCP auditor to check the
permissions of all my MCP servers

[Using mcp_auditor.audit_all_servers]
Found 3 servers, analyzing permissions...

Project-Scoped Configuration

Place a .claude.json file in your project root to define MCP servers specific to that project. These are loaded in addition to your global configuration.

my-project/
  .claude.json   # project-scoped tools
  CLAUDE.md      # usage instructions
  src/
  package.json

Chain Tools Together

Claude Code can chain multiple MCP tools in a single task. Ask it to scan for secrets, then fix them, then verify the fix. Claude orchestrates the tools automatically.

You: Scan for secrets, remove any you find,
then verify the cleanup was complete

[secret_scanner.scan] Found 2 leaked keys
[filesystem.write] Replaced with env vars
[secret_scanner.scan] Clean - 0 issues

Ready to power up Claude Code?

Browse our full catalog to find the perfect tools for your workflow, or check out all compatible agents.

Browse Full Catalog View All Agents