MCP Configuration Reference FAQs

Question 1

Where are Claude Code MCP settings stored?

Accepted Answer

They can be stored in three locations: ~/.claude/settings.json for user-wide settings, .claude/settings.json for project-specific settings, or .claude/settings.local.json for gitignored local settings.

Question 2

How do I debug an MCP server that isn't starting?

Accepted Answer

You can launch Claude using the --debug flag to see initialization logs, or test the server command manually in your terminal using npx to check for execution errors.

Question 3

How do I skip permission prompts for specific MCP tools?

Accepted Answer

You can use the 'alwaysAllow' field within your mcpServers configuration object and list the specific tool names in an array.

Question 4

Can I use environment variables in my MCP configuration?

Accepted Answer

Yes, you can define direct values in the 'env' field or reference system environment variables using the ${VARIABLE_NAME} syntax.

Question 5

What is the difference between project and local settings?

Accepted Answer

.claude/settings.json is intended to be committed to version control and shared with a team, while .claude/settings.local.json is for private configurations and sensitive keys.

MCP Configuration Reference

About

Key Features

Use Cases

MCP Configuration Reference

About

Key Features

Use Cases