claude-config_skill

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

TypeScript

25

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

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

EXAMPLES.md4.9 KB
SKILL.md3.2 KB

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

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.