Claude Code

Configure Claude Code with MCP servers and Developer profile to enable terminal-based collaboration platform functionality. Claude Code provides command-line access to systematic development methodologies, institutional memory, and temporal awareness for engineering workflows.

Setup

The collaboration platform requires four essential MCP servers to provide complete functionality through Claude Code’s terminal interface. These servers enable systematic development methodologies, institutional memory, and temporal awareness that transform Claude Code from generic assistance into specialized Developer profile partnership.

Initialization

Install Claude Code application:

npm install -g @anthropic-ai/claude-code

Configuration

Create the MCP servers configuration file:

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

Tip

This centralized configuration file supports both Claude Code and Claude Desktop applications, enabling consistent MCP servers setup.

Configure the following required MCP servers:

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

Note

Replace /Users/username/github/claude with actual local repository path and update the time MCP local-timezone argument value, as needed.

Activation

Create the CLAUDE.md file at repository root to activate the Developer profile, using the following project instructions:

# Project Instructions

On session start, Claude must:

1. Execute `memory:read_graph` to access memory system
2. Acknowledge temporal awareness
3. Load DEVELOPER profile as active framework

Secure Configuration

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

Symlink

Create a symlink to configuration file:

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

Note

Symlinks enable consistent configuration across multiple repository directories. Claude Code uses .mcp.json file in the working directory for MCP servers configuration.

Encryption

Install the ansible-vault utility:

brew install ansible

Encrypt configuration for version control:

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

Decrypt configuration, when needed:

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

Caution

Never commit unencrypted configuration files containing sensitive data. Use encryption tools like Ansible Vault, GPG, or your preferred method for files with API tokens or credentials.

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.

Core Functionality

Start Claude Code in your repository directory and test the following functionality:

cd ~/github/claude
claude

Test essential capabilities:

  1. Memory System - Verify the profile acknowledgment appears at session start
  2. Filesystem Access - Request file reading to test repository access
  3. Time Functions - Test temporal awareness with current time retrieval
  4. Sequential Thinking - Validate complex analysis workflows are available

Expected Output

Successful configuration produces profile acknowledgment:

Active profile: DEVELOPER | Thursday, July 10, 2025, 4:54 PM EDT

Terminal Workflows

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

Development Commands

  • Code Review - claude "Review this Pull Request for SOLID principles"
  • Debugging - claude "Debug this test failure with minimal fix approach"
  • Architecture - claude "Analyze this codebase structure for improvements"

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 packages are accessible from terminal
  4. Test individual MCP servers using direct invocation