MCP Inspector Development Guide
Description
> **Note:** Inspector V2 is under development to address architectural and UX improvements. During this time, V1 contributions should focus on **bug fixes and MCP spec compliance**. See [CONTRIBUTING.
Installation
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open the source below and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
Repository README
This is the README for modelcontextprotocol/inspector, shared by 2 entries
in this directory. It describes the repository, not this entry specifically.
MCP Inspector Development Guide
**Note:** Inspector V2 is under development to address architectural and UX improvements. During this time, V1 contributions should focus on **bug fixes and MCP spec compliance**. See [CONTRIBUTING.md](CONTRIBUTING.md) for more details.
Build Commands
- Build all:
npm run build - Build client:
npm run build-client - Build server:
npm run build-server - Development mode:
npm run dev(usenpm run dev:windowson Windows) - Format code:
npm run prettier-fix - Client lint:
cd client && npm run lint
Code Style Guidelines
- Use TypeScript with proper type annotations
- Follow React functional component patterns with hooks
- Use ES modules (import/export) not CommonJS
- Use Prettier for formatting (auto-formatted on commit)
- Follow existing naming conventions:
- camelCase for variables and functions
- PascalCase for component names and types
- kebab-case for file names
- Use async/await for asynchronous operations
- Implement proper error handling with try/catch blocks
- Use Tailwind CSS for styling in the client
- Keep components small and focused on a single responsibility
Project Organization
The project is organized as a monorepo with workspaces:
client/: React frontend with Vite, TypeScript and Tailwindserver/: Express backend with TypeScriptcli/: Command-line interface for testing and invoking MCP server methods directly
Related Agents
Gitnexus Test Ci Verifier
GitNexus test and CI reviewer. Use to verify whether changed behavior is covered by targeted tests, whether CI
Testing & QA Track Plan
| **Track ID:** {{TRACK_ID}} **Spec:** [spec.md](./spec.md) **Estimated Effort:** {{EFFORT_ESTIMATE}}... | - |
Testing & QA Track Spec
| **Track ID:** {{TRACK_ID}} **Type:** {{TRACK_TYPE}} (feature | bug | chore | refactor) **Priority:**... | -
Testing & QA Workflow
| 1. **plan.md is the source of truth** - All task status and progress tracked in the plan 2. **Test-D... | -
Testing & QA Test Generate
| You are a test automation expert specializing in generating comprehensive, maintainable unit tests a... | -
Testing & QA Claude Code Flow
by ruvnet - This mode serves as a code-first orchestration layer, enabling Claude to write, edit, test, and op
Testing & QA