Agent Skills: Claude Config Management

This skill should be used when configuring Claude, setting up MCP servers, or when "settings.json", "claude_desktop_config", "MCP server", or "Claude config" are mentioned.

UncategorizedID: outfitter-dev/agents/claude-config

Install this agent skill to your local

pnpm dlx add-skill https://github.com/outfitter-dev/agents/tree/HEAD/plugins/outfitter/skills/claude-config

Skill Files

Browse the full folder contents for claude-config.

Download Skill

Loading file tree…

plugins/outfitter/skills/claude-config/SKILL.md

Skill Metadata

Name
claude-config
Description
This skill should be used when configuring Claude, setting up MCP servers, or when "settings.json", "claude_desktop_config", "MCP server", or "Claude config" are mentioned.

Claude Config Management

Manages configuration files for Claude Desktop and Claude Code, including MCP server setup, project settings, and developer options.

Configuration File Locations

Claude Desktop (macOS):

  • Config: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Logs: ~/Library/Logs/Claude/
  • Developer settings: ~/Library/Application Support/Claude/developer_settings.json

Claude Desktop (Windows):

  • Config: %APPDATA%\Claude\claude_desktop_config.json
  • Logs: %APPDATA%\Claude\Logs\

Claude Code (Project-specific):

  • Settings: .claude/settings.json
  • Plugin marketplace: .claude-plugin/marketplace.json

Claude Desktop Configuration

Basic Structure

{
  "mcpServers": {
    "server-name": {
      "command": "command-to-run",
      "args": ["arg1", "arg2"],
      "env": {
        "VAR_NAME": "value"
      }
    }
  }
}

Important Notes

  • Always use absolute paths - Working directory may be undefined
  • Windows paths: Use forward slashes or double backslashes
  • Restart required: Restart Claude Desktop after configuration changes
  • Environment variables: Limited by default (USER, HOME, PATH); set explicitly in env

Claude Code Project Settings

.claude/settings.json

{
  "enabledPlugins": ["plugin-name"],
  "extraKnownMarketplaces": {
    "team-tools": {
      "source": {
        "source": "github",
        "repo": "company/claude-plugins"
      }
    }
  }
}

Team Configuration

Automatically install marketplaces when team members trust the folder:

{
  "extraKnownMarketplaces": {
    "company-tools": {
      "source": {
        "source": "github",
        "repo": "company/plugins"
      }
    },
    "project-tools": {
      "source": {
        "source": "git",
        "url": "https://git.company.com/project-plugins.git"
      }
    }
  }
}

Quick Validation

# Validate JSON syntax
jq empty ~/Library/Application\ Support/Claude/claude_desktop_config.json
jq empty .claude/settings.json

# Check server names
jq -r '.mcpServers | keys[]' ~/Library/Application\ Support/Claude/claude_desktop_config.json

Quick Troubleshooting

If MCP server not loading:

  1. Validate JSON syntax
  2. Verify command paths are absolute
  3. Check environment variables are set
  4. Review logs: ~/Library/Logs/Claude/mcp*.log
  5. Restart Claude Desktop

References

Detailed documentation for specific scenarios:

  • MCP Patterns - Server configuration examples (Python, Node.js, environment variables)
  • Troubleshooting - Common issues, log locations, debugging tools
  • Workflows - Step-by-step guides for adding servers, team setup, migration

Next Steps

  • See EXAMPLES.md for real-world configuration examples