Claude Code

Claude Code setup enables terminal-based collaboration with specialized development capabilities through MCP server integration and Developer profile activation for systematic engineering workflows.

Setup

Terminal collaboration requires MCP server configuration that transforms Claude Code from generic assistance into specialized development partnership with persistent memory and systematic methodologies. The platform repository serves as the central workspace for managing all development projects, eliminating the need to configure individual repositories.

brew install --cask claude-code
claude config set -g autoUpdates false
claude config set -g installMethod global

curl -fsSL https://claude.ai/install.sh | bash

irm https://claude.ai/install.ps1 | iex

cd ~/github/claude/
vi ./.claude/mcp.json

{
  "mcpServers": {
    "claude": {
      "command": "claude",
      "args": [
        "mcp",
        "serve"
      ]
    },
    "documentation": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-memory"
      ],
      "env": {
        "MEMORY_FILE_PATH": "/Users/username/github/claude/.claude/data/graph.json"
      }
    },
    "memory": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-memory"
      ],
      "env": {
        "MEMORY_FILE_PATH": "/Users/username/github/claude/.claude/memory/graph.json"
      }
    },
    "time": {
      "command": "uvx",
      "args": [
        "mcp-server-time",
        "--local-timezone=America/New_York"
      ]
    }
  }
}

{
  "mcpServers": {
    "language-server": {
      "command": "npx",
      "args": [
        "-y",
        "@axivo/mcp-lsp"
      ],
      "env": {
        "LSP_FILE_PATH": "/Users/username/github/claude/.claude/lsp.json"
      }
    }
  }
}

Configuration

Production-grade deployment requires configuration management with version control integration and optional encryption for sensitive data. This approach enables team collaboration while protecting sensitive configuration data and maintaining professional development workflows.

Configuration Files

The platform configuration uses the mcp.json and settings.json files with user settings applied to all projects. A settings.local.json file can be used containing additional user settings, Claude Code will automatically create it if required.

• .claude/mcp.json - Git ignored platform MCP server definitions
• .claude/settings.json - Platform MCP server permissions and settings
• .claude/settings.local.json - Git ignored MCP server permissions and settings
• .mcp.json - Symlink to platform MCP server definitions used by Claude Code

ln -fs ~/github/claude/.claude/mcp.json ~/github/claude/.mcp.json

brew install ansible

cd ~/github/claude/.claude
ansible-vault encrypt ./mcp.json --output ./mcp.json.enc

cd ~/github/claude/.claude
ansible-vault decrypt ./mcp.json.enc --output ./mcp.json

Profile Validation

Verify Claude Code configuration by testing core MCP servers functionality and Developer profile methodology activation. This validation ensures proper terminal-based collaboration before beginning development workflows.

cd ~/github/claude
claude

Claude Code

Claude’s response to Please detail the profile methodology prompt.

Terminal Workflows

Claude Code integration with Developer profile enables systematic development methodologies directly in terminal environments.

cd ~/github/claude
claude

Memory Integration

Terminal sessions preserve context through conversation logs and institutional memory:

• Previous debugging sessions inform current problem-solving approaches
• Code review patterns build cumulative expertise across projects
• Architecture decisions reference documented constraints and rationale

Troubleshooting

Common Claude Code configuration issues and systematic resolution procedures help ensure reliable terminal-based collaboration.

Common Issues

• MCP servers not found - Verify .mcp.json file exists in working directory
• Memory file not found - Run memory builder to generate configuration file
• Filesystem access denied - Check repository path permissions
• Profile not acknowledging - Confirm CLAUDE.md file exists at repository root

Debugging Process

1. Check Claude Code output for MCP servers connection errors
2. Verify mcp.json file syntax and paths
3. Ensure NPX/UVX server packages are accessible from terminal
4. Test individual MCP servers using direct invocation
5. Inspect ~/Library/Logs/Claude logs

Verify the MCP server packages are accessible by running the following commands:

npx -y @modelcontextprotocol/server-memory
uvx mcp-server-time --help

Cache Cleanup

When MCP server loading fails due to cached package corruption or version conflicts, systematic cache clearing resolves most installation issues:

npm cache clean --force
uv cache clean

For persistent npx package loading errors, clear the complete execution cache:

rm -rf $(npm config get cache)/_npx/*