home / skills / outfitter-dev / agents / claude-config

This skill helps you configure Claude Desktop and Code by managing MCP servers and project settings with clear file paths and validation.

npx playbooks add skill outfitter-dev/agents --skill claude-config

Review the files below or copy the command above to add this skill to your agents.

Files (5)
SKILL.md
3.2 KB
---
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.
metadata:
  version: "1.0.0"
  related-skills:
    - codex-config
    - claude-hooks
    - claude-rules
    - claude-plugins
    - skills-dev
---

# 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

```json
{
  "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

```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:

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

## Quick Validation

```bash
# 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](references/mcp-patterns.md)** - Server configuration examples (Python, Node.js, environment variables)
- **[Troubleshooting](references/troubleshooting.md)** - Common issues, log locations, debugging tools
- **[Workflows](references/workflows.md)** - Step-by-step guides for adding servers, team setup, migration

## Next Steps

- See [EXAMPLES.md](EXAMPLES.md) for real-world configuration examples

Overview

This skill manages Claude configuration files and MCP server definitions for Claude Desktop and Claude Code. It helps locate, validate, and edit settings like claude_desktop_config.json, .claude/settings.json, and developer options across macOS and Windows. Use it to ensure MCP servers run correctly and team plugin marketplaces are recognized.

How this skill works

The skill inspects known config file locations, validates JSON syntax, and parses mcpServers and plugin marketplace entries. It checks for absolute paths, required environment variables, and common platform path issues, and it points to relevant logs and restart steps when changes are made. It can list configured server names and highlight obvious misconfigurations for quicker troubleshooting.

When to use it

  • Adding or editing an MCP server entry in claude_desktop_config.json
  • Configuring project-level plugins or extraKnownMarketplaces in .claude/settings.json
  • Troubleshooting an MCP server that fails to start or connect
  • Preparing a team folder so marketplaces auto-install when trusted
  • Validating JSON syntax and verifying absolute command paths after edits

Best practices

  • Always use absolute paths for commands and working directories to avoid undefined cwd issues
  • On Windows, prefer forward slashes or double backslashes in paths to avoid escape problems
  • Explicitly set needed environment variables under env since defaults are limited
  • Restart Claude Desktop after any config change to ensure new settings load
  • Validate JSON with a tool like jq before restarting to prevent parsing errors

Example use cases

  • Add a new MCP server entry with a command, args, and env block to run a Python agent
  • Enable a team plugin marketplace in .claude/settings.json so teammates get plugins when the folder is trusted
  • Run a quick jq validation on claude_desktop_config.json after manual edits to catch syntax errors
  • Diagnose a server load failure by checking absolute command paths and relevant mcp*.log files
  • Migrate project plugin repos by adding git or GitHub sources to extraKnownMarketplaces

FAQ

Where are the main config files located?

Claude Desktop stores config and logs in platform-specific locations (macOS: ~/Library/Application Support/Claude; Windows: %APPDATA%\Claude) and Claude Code uses .claude/settings.json per project.

Why must I use absolute paths?

Claude may start with an undefined working directory; absolute paths ensure the runtime can find commands and scripts reliably.

What environment variables are available by default?

Defaults are limited (USER, HOME, PATH); set additional variables explicitly in the env section of an mcpServers entry.