Agent skill

claude-config

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.

View SKILL.md on GitHub Repository
Stars 26
Forks 0

Install this agent skill to your Project

npx add-skill https://github.com/outfitter-dev/agents/tree/main/plugins/outfitter/skills/claude-config

Metadata

Additional technical details for this skill

version
1.0.0
related skills 
[
    "codex-config",
    "claude-hooks",
    "claude-rules",
    "claude-plugins",
    "skills-dev"
]

SKILL.md

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

Recommended Agent Skills

Expand your agent's capabilities with these related and highly-rated skills.

outfitter-dev/agents

stack-feedback

Creates GitHub issues for problems discovered while using @outfitter/* packages. Use when finding bugs, missing features, unclear documentation, or improvement opportunities.

26 0
Explore
outfitter-dev/agents

stack-architecture

Design stack-based systems using @outfitter/* packages. Use when planning new projects, choosing packages, designing handler architecture, or when "architecture", "design", "structure", "plan handlers", or "error taxonomy" are mentioned.

26 0
Explore
outfitter-dev/agents

stack-templates

Templates for creating handlers, CLI commands, MCP tools, and daemon services following Outfitter Stack conventions. Use when scaffolding new components, creating handlers, adding commands, or when "create handler", "new command", "add tool", "scaffold", "template", or "daemon service" are mentioned.

26 0
Explore
outfitter-dev/agents

stack-audit

Scan codebase for Outfitter Stack adoption candidates. Identifies throw statements, console usage, hardcoded paths, and custom errors. Use when assessing adoption scope or checking readiness.

26 0
Explore
outfitter-dev/agents

stack-review

Audits code for Outfitter Stack compliance including Result types, error handling, logging patterns, and path safety. Use for pre-commit reviews, code quality checks, migration validation, or when "audit", "check compliance", "review stack", or "stack patterns" are mentioned.

26 0
Explore
outfitter-dev/agents

stack-patterns

Reference for Outfitter Stack patterns including Result types, Handler contract, Error taxonomy, and @outfitter/* package conventions. Use when learning the stack, looking up patterns, understanding packages, or when "Result", "Handler", "error taxonomy", "OutfitterError", "CLI output", "pagination", "MCP server", "MCP tool", "structured logging", "redaction", "test handler", "daemon", "IPC", or "@outfitter/*" are mentioned.

26 0
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results