Claude Desktop

Configure Claude Desktop with MCP servers and Developer profile to enable collaboration platform functionality. This process establishes core tool connections, memory system integration, and secure configuration management.

Setup

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

Initialization

Install Claude Desktop application:

brew install --cask claude

Run Claude Desktop once to initialize the application structure, then close it.

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 server 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

Activate the Developer profile, using the following project knowledge 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

Tip

Replace DEVELOPER with any of the predefined profiles matching the project collaboration scope (e.g. CREATIVE, ENGINEER, HUMANIST or RESEARCHER).

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:

rm -f ~/Library/Application\ Support/Claude/claude_desktop_config.json
ln -fs ~/github/claude/.claude/mcp.json \
   ~/Library/Application\ Support/Claude/claude_desktop_config.json

Note

Symlinks enable consistent configuration across multiple repository directories. Claude Desktop uses claude_desktop_config.json in the Application Support 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 Desktop configuration by testing core MCP server functionality and Developer profile methodology activation. This validation ensures proper integration before beginning collaborative work sessions.