Multi-Source Documentation MCP Server

--- category: integrations source: claude-code title: MCP Integration url: https://code.claude.com/docs/en/mcp --- ##### Build with Claude Code - [Subagents](/docs/en/sub-agents) - [Plugins](/docs/en/plugins) - [Agent Skills](/docs/en/skills) - [Output styles](/docs/en/output-styles) - [Hooks](/docs/en/hooks-guide) - [Headless mode](/docs/en/headless) - [GitHub Actions](/docs/en/github-actions) - [GitLab CI/CD](/docs/en/gitlab-ci-cd) - [Model Context Protocol (MCP)](/docs/en/mcp) - [Migrate to Claude Agent SDK](/docs/en/sdk/migration-guide) - [Troubleshooting](/docs/en/troubleshooting) On this page - [What you can do with MCP](#what-you-can-do-with-mcp) - [Popular MCP servers](#popular-mcp-servers) - [Installing MCP servers](#installing-mcp-servers) - [Option 1: Add a remote HTTP server](#option-1%3A-add-a-remote-http-server) - [Option 2: Add a remote SSE server](#option-2%3A-add-a-remote-sse-server) - [Option 3: Add a local stdio server](#option-3%3A-add-a-local-stdio-server) - [Managing your servers](#managing-your-servers) - [Plugin-provided MCP servers](#plugin-provided-mcp-servers) - [MCP installation scopes](#mcp-installation-scopes) - [Local scope](#local-scope) - [Project scope](#project-scope) - [User scope](#user-scope) - [Choosing the right scope](#choosing-the-right-scope) - [Scope hierarchy and precedence](#scope-hierarchy-and-precedence) - [Environment variable expansion in .mcp.json](#environment-variable-expansion-in-mcp-json) - [Practical examples](#practical-examples) - [Example: Monitor errors with Sentry](#example%3A-monitor-errors-with-sentry) - [Example: Connect to GitHub for code reviews](#example%3A-connect-to-github-for-code-reviews) - [Example: Query your PostgreSQL database](#example%3A-query-your-postgresql-database) - [Authenticate with remote MCP servers](#authenticate-with-remote-mcp-servers) - [Add MCP servers from JSON configuration](#add-mcp-servers-from-json-configuration) - [Import MCP servers from Claude Desktop](#import-mcp-servers-from-claude-desktop) - [Use Claude Code as an MCP server](#use-claude-code-as-an-mcp-server) - [MCP output limits and warnings](#mcp-output-limits-and-warnings) - [Use MCP resources](#use-mcp-resources) - [Reference MCP resources](#reference-mcp-resources) - [Use MCP prompts as slash commands](#use-mcp-prompts-as-slash-commands) - [Execute MCP prompts](#execute-mcp-prompts) - [Enterprise MCP configuration](#enterprise-mcp-configuration) - [Setting up enterprise MCP configuration](#setting-up-enterprise-mcp-configuration) - [Restricting MCP servers with allowlists and denylists](#restricting-mcp-servers-with-allowlists-and-denylists) Claude Code can connect to hundreds of external tools and data sources through the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/introduction), an open-source standard for AI-tool integrations. MCP servers give Claude Code access to your tools, databases, and APIs. ## [​](#what-you-can-do-with-mcp) What you can do with MCP With MCP servers connected, you can ask Claude Code to: - **Implement features from issue trackers**: “Add the feature described in JIRA issue ENG-4521 and create a PR on GitHub.” - **Analyze monitoring data**: “Check Sentry and Statsig to check the usage of the feature described in ENG-4521.” - **Query databases**: “Find emails of 10 random users who used feature ENG-4521, based on our Postgres database.” - **Integrate designs**: “Update our standard email template based on the new Figma designs that were posted in Slack” - **Automate workflows**: “Create Gmail drafts inviting these 10 users to a feedback session about the new feature.” ## [​](#popular-mcp-servers) Popular MCP servers Here are some commonly used MCP servers you can connect to Claude Code: Use third party MCP servers at your own risk - Anthropic has not verified the correctness or security of all these servers. Make sure you trust MCP servers you are installing. Be especially careful when using MCP servers that could fetch untrusted content, as these can expose you to prompt injection risk. ### Development & Testing Tools [**Sentry**](https://docs.sentry.io/product/sentry-mcp/) Monitor errors, debug production issuesCommand `claude mcp add --transport http sentry https://mcp.sentry.dev/mcp` [**Socket**](https://github.com/SocketDev/socket-mcp) Security analysis for dependenciesCommand `claude mcp add --transport http socket https://mcp.socket.dev/` [**Hugging Face**](https://huggingface.co/settings/mcp) Provides access to Hugging Face Hub information and Gradio AI ApplicationsCommand `claude mcp add --transport http hugging-face https://huggingface.co/mcp` [**Jam**](https://jam.dev/docs/debug-a-jam/mcp) Debug faster with AI agents that can access Jam recordings like video, console logs, network requests, and errorsCommand `claude mcp add --transport http jam https://mcp.jam.dev/mcp` ### Project Management & Documentation [**Asana**](https://developers.asana.com/docs/using-asanas-model-control-protocol-mcp-server) Interact with your Asana workspace to keep projects on trackCommand `claude mcp add --transport sse asana https://mcp.asana.com/sse` [**Atlassian**](https://www.atlassian.com/platform/remote-mcp-server) Manage your Jira tickets and Confluence docsCommand `claude mcp add --transport sse atlassian https://mcp.atlassian.com/v1/sse` [**ClickUp**](https://github.com/hauptsacheNet/clickup-mcp) Task management, project trackingCommand `claude mcp add --transport stdio clickup --env CLICKUP_API_KEY=YOUR_KEY --env CLICKUP_TEAM_ID=YOUR_ID -- npx -y @hauptsache.net/clickup-mcp` [**Intercom**](https://developers.intercom.com/docs/guides/mcp) Access real-time customer conversations, tickets, and user dataCommand `claude mcp add --transport http intercom https://mcp.intercom.com/mcp` [**Linear**](https://linear.app/docs/mcp) Integrate with Linear's issue tracking and project managementCommand `claude mcp add --transport http linear https://mcp.linear.app/mcp` [**Notion**](https://developers.notion.com/docs/mcp) Read docs, update pages, manage tasksCommand `claude mcp add --transport http notion https://mcp.notion.com/mcp` [**Box**](https://box.dev/guides/box-mcp/remote/) Ask questions about your enterprise content, get insights from unstructured data, automate content workflowsCommand `claude mcp add --transport http box https://mcp.box.com/` [**Fireflies**](https://guide.fireflies.ai/articles/8272956938-learn-about-the-fireflies-mcp-server-model-context-protocol) Extract valuable insights from meeting transcripts and summariesCommand `claude mcp add --transport http fireflies https://api.fireflies.ai/mcp` [**Monday**](https://developer.monday.com/apps/docs/mondaycom-mcp-integration) Manage monday.com boards by creating items, updating columns, assigning owners, setting timelines, adding CRM activities, and writing summariesCommand `claude mcp add --transport http monday https://mcp.monday.com/mcp` ### Databases & Data Management [**Airtable**](https://github.com/domdomegg/airtable-mcp-server) Read/write records, manage bases and tablesCommand `claude mcp add --transport stdio airtable --env AIRTABLE_API_KEY=YOUR_KEY -- npx -y airtable-mcp-server` [**Daloopa**](https://docs.daloopa.com/docs/daloopa-mcp) Supplies high quality fundamental financial data sourced from SEC Filings, investor presentationsCommand `claude mcp add --transport http daloopa https://mcp.daloopa.com/server/mcp` [**HubSpot**](https://developers.hubspot.com/mcp) Access and manage HubSpot CRM data by fetching contacts, companies, and deals, and creating and updating recordsCommand `claude mcp add --transport http hubspot https://mcp.hubspot.com/anthropic` ### Payments & Commerce [**PayPal**](https://www.paypal.ai/) Integrate PayPal commerce capabilities, payment processing, transaction managementCommand `claude mcp add --transport http paypal https://mcp.paypal.com/mcp` [**Plaid**](https://plaid.com/blog/plaid-mcp-ai-assistant-claude/) Analyze, troubleshoot, and optimize Plaid integrations. Banking data, financial account linkingCommand `claude mcp add --transport sse plaid https://api.dashboard.plaid.com/mcp/sse` [**Square**](https://developer.squareup.com/docs/mcp) Use an agent to build on Square APIs. Payments, inventory, orders, and moreCommand `claude mcp add --transport sse square https://mcp.squareup.com/sse` [**Stripe**](https://docs.stripe.com/mcp) Payment processing, subscription management, and financial transactionsCommand `claude mcp add --transport http stripe https://mcp.stripe.com` ### Design & Media [**Figma**](https://developers.figma.com) Generate better code by bringing in full Figma contextVisit developers.figma.com for local server setup.Command `claude mcp add --transport http figma-remote-mcp https://mcp.figma.com/mcp` [**Cloudinary**](https://cloudinary.com/documentation/cloudinary_llm_mcp#mcp_servers) Upload, manage, transform, and analyze your media assetsMultiple services available. See documentation for specific server URLs. [**invideo**](https://invideo.io/ai/mcp) Build video creation capabilities into your applicationsCommand `claude mcp add --transport sse invideo https://mcp.invideo.io/sse` [**Canva**](https://www.canva.dev/docs/connect/canva-mcp-server-setup/) Browse, summarize, autofill, and even generate new Canva designs directly from ClaudeCommand `claude mcp add --transport http canva https://mcp.canva.com/mcp` ### Infrastructure & DevOps [**Cloudflare**](https://developers.cloudflare.com/agents/model-context-protocol/mcp-servers-for-cloudflare/) Build applications, analyze traffic, monitor performance, and manage security settings through CloudflareMultiple services available. See documentation for specific server URLs. Claude Code can use the Cloudflare CLI if installed. [**Netlify**](https://docs.netlify.com/build/build-with-ai/netlify-mcp-server/) Create, deploy, and manage websites on Netlify. Control all aspects of your site from creating secrets to enforcing access controls to aggregating form submissionsCommand `claude mcp add --transport http netlify https://netlify-mcp.netlify.app/mcp` [**Stytch**](https://stytch.com/docs/workspace-management/stytch-mcp) Configure and manage Stytch authentication services, redirect URLs, email templates, and workspace settingsCommand `claude mcp add --transport http stytch http://mcp.stytch.dev/mcp` [**Vercel**](https://vercel.com/docs/mcp/vercel-mcp) Vercel's official MCP server, allowing you to search and navigate documentation, manage projects and deployments, and analyze deployment logs—all in one placeCommand `claude mcp add --transport http vercel https://mcp.vercel.com/` ### Automation & Integration [**Workato**](https://docs.workato.com/mcp.html) Access any application, workflows or data via Workato, made accessible for AIMCP servers are programmatically generated [**Zapier**](https://help.zapier.com/hc/en-us/articles/36265392843917) Connect to nearly 8,000 apps through Zapier's automation platformGenerate a user-specific URL at mcp.zapier.com **Need a specific integration?** [Find hundreds more MCP servers on GitHub](https://github.com/modelcontextprotocol/servers), or build your own using the [MCP SDK](https://modelcontextprotocol.io/quickstart/server). ## [​](#installing-mcp-servers) Installing MCP servers MCP servers can be configured in three different ways depending on your needs: ### [​](#option-1%3A-add-a-remote-http-server) Option 1: Add a remote HTTP server HTTP servers are the recommended option for connecting to remote MCP servers. This is the most widely supported transport for cloud-based services. Copy Ask AI ```shiki # Basic syntax claude mcp add --transport http <name> <url> # Real example: Connect to Notion claude mcp add --transport http notion https://mcp.notion.com/mcp # Example with Bearer token claude mcp add --transport http secure-api https://api.example.com/mcp \ --header "Authorization: Bearer your-token" ``` ### [​](#option-2%3A-add-a-remote-sse-server) Option 2: Add a remote SSE server The SSE (Server-Sent Events) transport is deprecated. Use HTTP servers instead, where available. Copy Ask AI ```shiki # Basic syntax claude mcp add --transport sse <name> <url> # Real example: Connect to Asana claude mcp add --transport sse asana https://mcp.asana.com/sse # Example with authentication header claude mcp add --transport sse private-api https://api.company.com/sse \ --header "X-API-Key: your-key-here" ``` ### [​](#option-3%3A-add-a-local-stdio-server) Option 3: Add a local stdio server Stdio servers run as local processes on your machine. They’re ideal for tools that need direct system access or custom scripts. Copy Ask AI ```shiki # Basic syntax claude mcp add --transport stdio <name> <command> [args...] # Real example: Add Airtable server claude mcp add --transport stdio airtable --env AIRTABLE_API_KEY=YOUR_KEY \ -- npx -y airtable-mcp-server ``` **Understanding the ”—” parameter:** The `--` (double dash) separates Claude’s own CLI flags from the command and arguments that get passed to the MCP server. Everything before `--` are options for Claude (like `--env`, `--scope`), and everything after `--` is the actual command to run the MCP server.For example: - `claude mcp add --transport stdio myserver -- npx server` → runs `npx server` - `claude mcp add --transport stdio myserver --env KEY=value -- python server.py --port 8080` → runs `python server.py --port 8080` with `KEY=value` in environment This prevents conflicts between Claude’s flags and the server’s flags. ### [​](#managing-your-servers) Managing your servers Once configured, you can manage your MCP servers with these commands: Copy Ask AI ```shiki # List all configured servers claude mcp list # Get details for a specific server claude mcp get github # Remove a server claude mcp remove github # (within Claude Code) Check server status /mcp ``` Tips: - Use the `--scope` flag to specify where the configuration is stored: - `local` (default): Available only to you in the current project (was called `project` in older versions) - `project`: Shared with everyone in the project via `.mcp.json` file - `user`: Available to you across all projects (was called `global` in older versions) - Set environment variables with `--env` flags (e.g., `--env KEY=value`) - Configure MCP server startup timeout using the MCP\_TIMEOUT environment variable (e.g., `MCP_TIMEOUT=10000 claude` sets a 10-second timeout) - Claude Code will display a warning when MCP tool output exceeds 10,000 tokens. To increase this limit, set the `MAX_MCP_OUTPUT_TOKENS` environment variable (e.g., `MAX_MCP_OUTPUT_TOKENS=50000`) - Use `/mcp` to authenticate with remote servers that require OAuth 2.0 authentication **Windows Users**: On native Windows (not WSL), local MCP servers that use `npx` require the `cmd /c` wrapper to ensure proper execution. Copy Ask AI ```shiki # This creates command="cmd" which Windows can execute claude mcp add --transport stdio my-server -- cmd /c npx -y @some/package ``` Without the `cmd /c` wrapper, you’ll encounter “Connection closed” errors because Windows cannot directly execute `npx`. (See the note above for an explanation of the `--` parameter.) ### [​](#plugin-provided-mcp-servers) Plugin-provided MCP servers [Plugins](/docs/en/plugins) can bundle MCP servers, automatically providing tools and integrations when the plugin is enabled. Plugin MCP servers work identically to user-configured servers. **How plugin MCP servers work**: - Plugins define MCP servers in `.mcp.json` at the plugin root or inline in `plugin.json` - When a plugin is enabled, its MCP servers start automatically - Plugin MCP tools appear alongside manually configured MCP tools - Plugin servers are managed through plugin installation (not `/mcp` commands) **Example plugin MCP configuration**: In `.mcp.json` at plugin root: Copy Ask AI ```shiki { "database-tools": { "command": "${CLAUDE_PLUGIN_ROOT}/servers/db-server", "args": ["--config", "${CLAUDE_PLUGIN_ROOT}/config.json"], "env": { "DB_URL": "${DB_URL}" } } } ``` Or inline in `plugin.json`: Copy Ask AI ```shiki { "name": "my-plugin", "mcpServers": { "plugin-api": { "command": "${CLAUDE_PLUGIN_ROOT}/servers/api-server", "args": ["--port", "8080"] } } } ``` **Plugin MCP features**: - **Automatic lifecycle**: Servers start when plugin enables, but you must restart Claude Code to apply MCP server changes (enabling or disabling) - **Environment variables**: Use `${CLAUDE_PLUGIN_ROOT}` for plugin-relative paths - **User environment access**: Access to same environment variables as manually configured servers - **Multiple transport types**: Support stdio, SSE, and HTTP transports (transport support may vary by server) **Viewing plugin MCP servers**: Copy Ask AI ```shiki # Within Claude Code, see all MCP servers including plugin ones /mcp ``` Plugin servers appear in the list with indicators showing they come from plugins. **Benefits of plugin MCP servers**: - **Bundled distribution**: Tools and servers packaged together - **Automatic setup**: No manual MCP configuration needed - **Team consistency**: Everyone gets the same tools when plugin is installed See the [plugin components reference](/docs/en/plugins-reference#mcp-servers) for details on bundling MCP servers with plugins. ## [​](#mcp-installation-scopes) MCP installation scopes MCP servers can be configured at three different scope levels, each serving distinct purposes for managing server accessibility and sharing. Understanding these scopes helps you determine the best way to configure servers for your specific needs. ### [​](#local-scope) Local scope Local-scoped servers represent the default configuration level and are stored in your project-specific user settings. These servers remain private to you and are only accessible when working within the current project directory. This scope is ideal for personal development servers, experimental configurations, or servers containing sensitive credentials that shouldn’t be shared. Copy Ask AI ```shiki # Add a local-scoped server (default) claude mcp add --transport http stripe https://mcp.stripe.com # Explicitly specify local scope claude mcp add --transport http stripe --scope local https://mcp.stripe.com ``` ### [​](#project-scope) Project scope Project-scoped servers enable team collaboration by storing configurations in a `.mcp.json` file at your project’s root directory. This file is designed to be checked into version control, ensuring all team members have access to the same MCP tools and services. When you add a project-scoped server, Claude Code automatically creates or updates this file with the appropriate configuration structure. Copy Ask AI ```shiki # Add a project-scoped server claude mcp add --transport http paypal --scope project https://mcp.paypal.com/mcp ``` The resulting `.mcp.json` file follows a standardized format: Copy Ask AI ```shiki { "mcpServers": { "shared-server": { "command": "/path/to/server", "args": [], "env": {} } } } ``` For security reasons, Claude Code prompts for approval before using project-scoped servers from `.mcp.json` files. If you need to reset these approval choices, use the `claude mcp reset-project-choices` command. ### [​](#user-scope) User scope User-scoped servers provide cross-project accessibility, making them available across all projects on your machine while remaining private to your user account. This scope works well for personal utility servers, development tools, or services you frequently use across different projects. Copy Ask AI ```shiki # Add a user server claude mcp add --transport http hubspot --scope user https://mcp.hubspot.com/anthropic ``` ### [​](#choosing-the-right-scope) Choosing the right scope Select your scope based on: - **Local scope**: Personal servers, experimental configurations, or sensitive credentials specific to one project - **Project scope**: Team-shared servers, project-specific tools, or services required for collaboration - **User scope**: Personal utilities needed across multiple projects, development tools, or frequently-used services ### [​](#scope-hierarchy-and-precedence) Scope hierarchy and precedence MCP server configurations follow a clear precedence hierarchy. When servers with the same name exist at multiple scopes, the system resolves conflicts by prioritizing local-scoped servers first, followed by project-scoped servers, and finally user-scoped servers. This design ensures that personal configurations can override shared ones when needed. ### [​](#environment-variable-expansion-in-mcp-json) Environment variable expansion in `.mcp.json` Claude Code supports environment variable expansion in `.mcp.json` files, allowing teams to share configurations while maintaining flexibility for machine-specific paths and sensitive values like API keys. **Supported syntax:** - `${VAR}` - Expands to the value of environment variable `VAR` - `${VAR:-default}` - Expands to `VAR` if set, otherwise uses `default` **Expansion locations:** Environment variables can be expanded in: - `command` - The server executable path - `args` - Command-line arguments - `env` - Environment variables passed to the server - `url` - For HTTP server types - `headers` - For HTTP server authentication **Example with variable expansion:** Copy Ask AI ```shiki { "mcpServers": { "api-server": { "type": "http", "url": "${API_BASE_URL:-https://api.example.com}/mcp", "headers": { "Authorization": "Bearer ${API_KEY}" } } } } ``` If a required environment variable is not set and has no default value, Claude Code will fail to parse the config. ## [​](#practical-examples) Practical examples ### [​](#example%3A-monitor-errors-with-sentry) Example: Monitor errors with Sentry Copy Ask AI ```shiki # 1. Add the Sentry MCP server claude mcp add --transport http sentry https://mcp.sentry.dev/mcp # 2. Use /mcp to authenticate with your Sentry account > /mcp # 3. Debug production issues > "What are the most common errors in the last 24 hours?" > "Show me the stack trace for error ID abc123" > "Which deployment introduced these new errors?" ``` ### [​](#example%3A-connect-to-github-for-code-reviews) Example: Connect to GitHub for code reviews Copy Ask AI ```shiki # 1. Add the GitHub MCP server claude mcp add --transport http github https://api.githubcopilot.com/mcp/ # 2. In Claude Code, authenticate if needed > /mcp # Select "Authenticate" for GitHub # 3. Now you can ask Claude to work with GitHub > "Review PR #456 and suggest improvements" > "Create a new issue for the bug we just found" > "Show me all open PRs assigned to me" ``` ### [​](#example%3A-query-your-postgresql-database) Example: Query your PostgreSQL database Copy Ask AI ```shiki # 1. Add the database server with your connection string claude mcp add --transport stdio db -- npx -y @bytebase/dbhub \ --dsn "postgresql://readonly:[email protected]:5432/analytics" # 2. Query your database naturally > "What's our total revenue this month?" > "Show me the schema for the orders table" > "Find customers who haven't made a purchase in 90 days" ``` ## [​](#authenticate-with-remote-mcp-servers) Authenticate with remote MCP servers Many cloud-based MCP servers require authentication. Claude Code supports OAuth 2.0 for secure connections. 1 Add the server that requires authentication For example: Copy Ask AI ```shiki claude mcp add --transport http sentry https://mcp.sentry.dev/mcp ``` 2 Use the /mcp command within Claude Code In Claude code, use the command: Copy Ask AI ```shiki > /mcp ``` Then follow the steps in your browser to login. Tips: - Authentication tokens are stored securely and refreshed automatically - Use “Clear authentication” in the `/mcp` menu to revoke access - If your browser doesn’t open automatically, copy the provided URL - OAuth authentication works with HTTP servers ## [​](#add-mcp-servers-from-json-configuration) Add MCP servers from JSON configuration If you have a JSON configuration for an MCP server, you can add it directly: 1 Add an MCP server from JSON Copy Ask AI ```shiki # Basic syntax claude mcp add-json <name> '<json>' # Example: Adding an HTTP server with JSON configuration claude mcp add-json weather-api '{"type":"http","url":"https://api.weather.com/mcp","headers":{"Authorization":"Bearer token"}}' # Example: Adding a stdio server with JSON configuration claude mcp add-json local-weather '{"type":"stdio","command":"/path/to/weather-cli","args":["--api-key","abc123"],"env":{"CACHE_DIR":"/tmp"}}' ``` 2 Verify the server was added Copy Ask AI ```shiki claude mcp get weather-api ``` Tips: - Make sure the JSON is properly escaped in your shell - The JSON must conform to the MCP server configuration schema - You can use `--scope user` to add the server to your user configuration instead of the project-specific one ## [​](#import-mcp-servers-from-claude-desktop) Import MCP servers from Claude Desktop If you’ve already configured MCP servers in Claude Desktop, you can import them: 1 Import servers from Claude Desktop Copy Ask AI ```shiki # Basic syntax claude mcp add-from-claude-desktop ``` 2 Select which servers to import After running the command, you’ll see an interactive dialog that allows you to select which servers you want to import. 3 Verify the servers were imported Copy Ask AI ```shiki claude mcp list ``` Tips: - This feature only works on macOS and Windows Subsystem for Linux (WSL) - It reads the Claude Desktop configuration file from its standard location on those platforms - Use the `--scope user` flag to add servers to your user configuration - Imported servers will have the same names as in Claude Desktop - If servers with the same names already exist, they will get a numerical suffix (e.g., `server_1`) ## [​](#use-claude-code-as-an-mcp-server) Use Claude Code as an MCP server You can use Claude Code itself as an MCP server that other applications can connect to: Copy Ask AI ```shiki # Start Claude as a stdio MCP server claude mcp serve ``` You can use this in Claude Desktop by adding this configuration to claude\_desktop\_config.json: Copy Ask AI ```shiki { "mcpServers": { "claude-code": { "type": "stdio", "command": "claude", "args": ["mcp", "serve"], "env": {} } } } ``` **Configuring the executable path**: The `command` field must reference the Claude Code executable. If the `claude` command is not in your system’s PATH, you’ll need to specify the full path to the executable.To find the full path: Copy Ask AI ```shiki which claude ``` Then use the full path in your configuration: Copy Ask AI ```shiki { "mcpServers": { "claude-code": { "type": "stdio", "command": "/full/path/to/claude", "args": ["mcp", "serve"], "env": {} } } } ``` Without the correct executable path, you’ll encounter errors like `spawn claude ENOENT`. Tips: - The server provides access to Claude’s tools like View, Edit, LS, etc. - In Claude Desktop, try asking Claude to read files in a directory, make edits, and more. - Note that this MCP server is simply exposing Claude Code’s tools to your MCP client, so your own client is responsible for implementing user confirmation for individual tool calls. ## [​](#mcp-output-limits-and-warnings) MCP output limits and warnings When MCP tools produce large outputs, Claude Code helps manage the token usage to prevent overwhelming your conversation context: - **Output warning threshold**: Claude Code displays a warning when any MCP tool output exceeds 10,000 tokens - **Configurable limit**: You can adjust the maximum allowed MCP output tokens using the `MAX_MCP_OUTPUT_TOKENS` environment variable - **Default limit**: The default maximum is 25,000 tokens To increase the limit for tools that produce large outputs: Copy Ask AI ```shiki # Set a higher limit for MCP tool outputs export MAX_MCP_OUTPUT_TOKENS=50000 claude ``` This is particularly useful when working with MCP servers that: - Query large datasets or databases - Generate detailed reports or documentation - Process extensive log files or debugging information If you frequently encounter output warnings with specific MCP servers, consider increasing the limit or configuring the server to paginate or filter its responses. ## [​](#use-mcp-resources) Use MCP resources MCP servers can expose resources that you can reference using @ mentions, similar to how you reference files. ### [​](#reference-mcp-resources) Reference MCP resources 1 List available resources Type `@` in your prompt to see available resources from all connected MCP servers. Resources appear alongside files in the autocomplete menu. 2 Reference a specific resource Use the format `@server:protocol://resource/path` to reference a resource: Copy Ask AI ```shiki > Can you analyze @github:issue://123 and suggest a fix? ``` Copy Ask AI ```shiki > Please review the API documentation at @docs:file://api/authentication ``` 3 Multiple resource references You can reference multiple resources in a single prompt: Copy Ask AI ```shiki > Compare @postgres:schema://users with @docs:file://database/user-model ``` Tips: - Resources are automatically fetched and included as attachments when referenced - Resource paths are fuzzy-searchable in the @ mention autocomplete - Claude Code automatically provides tools to list and read MCP resources when servers support them - Resources can contain any type of content that the MCP server provides (text, JSON, structured data, etc.) ## [​](#use-mcp-prompts-as-slash-commands) Use MCP prompts as slash commands MCP servers can expose prompts that become available as slash commands in Claude Code. ### [​](#execute-mcp-prompts) Execute MCP prompts 1 Discover available prompts Type `/` to see all available commands, including those from MCP servers. MCP prompts appear with the format `/mcp__servername__promptname`. 2 Execute a prompt without arguments Copy Ask AI ```shiki > /mcp__github__list_prs ``` 3 Execute a prompt with arguments Many prompts accept arguments. Pass them space-separated after the command: Copy Ask AI ```shiki > /mcp__github__pr_review 456 ``` Copy Ask AI ```shiki > /mcp__jira__create_issue "Bug in login flow" high ``` Tips: - MCP prompts are dynamically discovered from connected servers - Arguments are parsed based on the prompt’s defined parameters - Prompt results are injected directly into the conversation - Server and prompt names are normalized (spaces become underscores) ## [​](#enterprise-mcp-configuration) Enterprise MCP configuration For organizations that need centralized control over MCP servers, Claude Code supports enterprise-managed MCP configurations. This allows IT administrators to: - **Control which MCP servers employees can access**: Deploy a standardized set of approved MCP servers across the organization - **Prevent unauthorized MCP servers**: Optionally restrict users from adding their own MCP servers - **Disable MCP entirely**: Remove MCP functionality completely if needed ### [​](#setting-up-enterprise-mcp-configuration) Setting up enterprise MCP configuration System administrators can deploy an enterprise MCP configuration file alongside the managed settings file: - **macOS**: `/Library/Application Support/ClaudeCode/managed-mcp.json` - **Windows**: `C:\ProgramData\ClaudeCode\managed-mcp.json` - **Linux**: `/etc/claude-code/managed-mcp.json` The `managed-mcp.json` file uses the same format as a standard `.mcp.json` file: Copy Ask AI ```shiki { "mcpServers": { "github": { "type": "http", "url": "https://api.githubcopilot.com/mcp/" }, "sentry": { "type": "http", "url": "https://mcp.sentry.dev/mcp" }, "company-internal": { "type": "stdio", "command": "/usr/local/bin/company-mcp-server", "args": ["--config", "/etc/company/mcp-config.json"], "env": { "COMPANY_API_URL": "https://internal.company.com" } } } } ``` ### [​](#restricting-mcp-servers-with-allowlists-and-denylists) Restricting MCP servers with allowlists and denylists In addition to providing enterprise-managed servers, administrators can control which MCP servers users are allowed to configure using `allowedMcpServers` and `deniedMcpServers` in the `managed-settings.json` file: - **macOS**: `/Library/Application Support/ClaudeCode/managed-settings.json` - **Windows**: `C:\ProgramData\ClaudeCode\managed-settings.json` - **Linux**: `/etc/claude-code/managed-settings.json` Copy Ask AI ```shiki { "allowedMcpServers": [ { "serverName": "github" }, { "serverName": "sentry" }, { "serverName": "company-internal" } ], "deniedMcpServers": [ { "serverName": "filesystem" } ] } ``` **Allowlist behavior (`allowedMcpServers`)**: - `undefined` (default): No restrictions - users can configure any MCP server - Empty array `[]`: Complete lockdown - users cannot configure any MCP servers - List of server names: Users can only configure the specified servers **Denylist behavior (`deniedMcpServers`)**: - `undefined` (default): No servers are blocked - Empty array `[]`: No servers are blocked - List of server names: Specified servers are explicitly blocked across all scopes **Important notes**: - These restrictions apply to all scopes: user, project, local, and even enterprise servers from `managed-mcp.json` - **Denylist takes absolute precedence**: If a server appears in both lists, it will be blocked **Enterprise configuration precedence**: The enterprise MCP configuration has the highest precedence and cannot be overridden by user, local, or project configurations. [GitLab CI/CD](/docs/en/gitlab-ci-cd)[Migrate to Claude Agent SDK](/docs/en/sdk/migration-guide) ⌘I