dev-mcp-setup

Configure MCP servers in Claude settings.json and validate mcp__<server>__* tool discovery.

520|175|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/evolution-foundation/evo-nexus --skill dev-mcp-setup-evolution-foundation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-mcp-setup
Source: https://github.com/evolution-foundation/evo-nexus/tree/main/.claude/skills/dev-mcp-setup
Command: npx skills add https://github.com/evolution-foundation/evo-nexus --skill dev-mcp-setup-evolution-foundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you correctly set up and troubleshoot Model Context Protocol (MCP) servers so Claude Code can discover and use the right external tools within your workspace.

Core Features & Use Cases

  • MCP Server Configuration Guidance: Walks you through identifying which MCP server you need and adding it to the correct settings file with the required auth or environment variables.
  • Workspace Discovery & Verification: Explains how to restart Claude Code and confirm the new MCP tools appear with the expected tool-name prefix.
  • Diagnostics for Non-Responsive MCPs: Provides a practical checklist for spawn errors, missing environment variables, package installation, and independent server testing.

Use it when you’re adding a new MCP-backed integration (like GitHub or web search), setting up a fresh EvoNexus workspace with standard MCPs, or diagnosing why an MCP server fails to respond.

Quick Start

Use the dev-mcp-setup skill to configure the GitHub MCP by checking your current .claude/settings.json (or ~/.claude/settings.json), adding the required github MCP entry with your GITHUB_TOKEN, restarting Claude Code, and verifying the tools appear with the mcp__github__* prefix.

Frequently Asked Questions about dev-mcp-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure an MCP server in Claude Code?

To configure an MCP server in Claude Code, you need to edit the correct .claude/settings.json file, add the server entry with required auth and environment variables, then restart Claude Code to load the integration.

Why is my MCP server not showing up in Claude Code?

Your MCP server might not show up due to missing environment variables, incorrect settings.json placement, or package installation issues. Restart Claude Code and verify tools appear using the mcp__<server>__* naming pattern.

How do I add the GitHub MCP integration to my workspace?

To add the GitHub MCP integration, update your .claude/settings.json file with the github MCP entry, provide your GITHUB_TOKEN as an environment variable, restart Claude Code, and verify the mcp__github__* tools are discovered.

Do I need to restart Claude Code after updating settings.json for MCP?

Yes, you must restart Claude Code after updating the settings.json file. Restarting applies the new MCP server configuration and allows the workspace to discover and validate the newly added external tools.

What is the MCP tool naming pattern for discovered servers?

The MCP tool naming pattern for discovered servers follows the mcp__<server>__* format. After configuring and restarting, you validate tool discovery by checking that your external tools appear with this specific prefix.

How do I troubleshoot MCP spawn errors and non-responsive servers?

To troubleshoot MCP spawn errors and non-responsive servers, run through a diagnostic checklist covering missing environment variables, package installation status, and testing the server independently to isolate runtime failures.