Skills mcp-integration

🔌

mcp-integration

Name: mcp-integration
Author: anthropics

Safe 🌐 Network access🔑 Env variables⚙️ External commands

Add MCP servers to Claude Code plugins

Also available from: Joseph OBrien,Joseph OBrien,anthropics,davila7

External services and APIs cannot be directly accessed by Claude Code plugins. Model Context Protocol enables structured integration with databases, cloud services, and custom tools. Connect MCP servers to expose external capabilities as Claude Code tools.

Supports: Claude Codex Code(CC)

🥉 72 Bronze

Download the skill ZIP

Upload in Claude

Go to Settings → Capabilities → Skills → Upload skill

Toggle on and start using

Test it

Using "mcp-integration". Add MCP server for database access

Expected outcome:

Database MCP server configured in .mcp.json
Connection uses environment variables for credentials
Tools available: query, execute, list_tables, describe
Server connects on first tool use (lazy loading)

Using "mcp-integration". Connect to GitHub via MCP

Expected outcome:

SSE server configured for GitHub MCP endpoint
OAuth authentication flow handled automatically
Tools available: create_repo, list_issues, create_pull_request
Token stored securely by Claude Code

Using "mcp-integration". Build custom local MCP server

Expected outcome:

Python script registered as stdio MCP server
Environment variables passed for configuration
Custom tools appear with mcp__plugin prefix
Server managed by Claude Code process lifecycle

Security Audit

Safe

v5 • 1/17/2026

Official Anthropic documentation skill containing only markdown guides and JSON configuration examples. No executable code or scripts. All content promotes security best practices including HTTPS, environment variable usage, and proper credential handling.

Files scanned

2,242

Lines analyzed

findings

Total audits

Risk Factors

🌐 Network access (43)

🔑 Env variables (29)

examples/stdio-server.json:14 examples/stdio-server.json:14 examples/stdio-server.json:22 examples/stdio-server.json:22 references/authentication.md:185 references/authentication.md:185 references/authentication.md:187 references/authentication.md:187 references/authentication.md:197 references/authentication.md:199 references/authentication.md:210 references/authentication.md:212 references/authentication.md:218 references/authentication.md:220 references/authentication.md:115 references/authentication.md:116 references/authentication.md:154 references/authentication.md:509 references/authentication.md:515 references/server-types.md:32 references/server-types.md:30 references/server-types.md:30 references/server-types.md:259 SKILL.md:183 SKILL.md:281 SKILL.md:182 SKILL.md:182 SKILL.md:282 SKILL.md:282

⚙️ External commands (280)

Audited by: claude View Audit History →

Quality Score

Architecture

100

Maintainability

Content

Community

100

Security

Spec Compliance

What You Can Build

Build plugins with external service access

Create plugins that connect to databases, APIs, and cloud services using MCP configuration

Integrate infrastructure tools

Connect to cloud providers, CI/CD systems, and monitoring tools through MCP servers

Query databases from Claude Code

Run SQL queries and manage database operations using MCP database servers

Try These Prompts

Add local MCP server

Add an MCP stdio server to my plugin that provides file system access using npx @modelcontextprotocol/server-filesystem for paths in ${CLAUDE_PROJECT_DIR}

Configure cloud MCP server

Configure an MCP SSE server for Asana integration with OAuth authentication. Show the .mcp.json configuration and explain the OAuth flow

Build custom tools server

Create a custom MCP stdio server that exposes my Python script functions as Claude Code tools. Include environment variable configuration

Secure cloud integration

Set up secure HTTP MCP server connection to a production API with Bearer token authentication. Include environment variable best practices and error handling

Best Practices

Always use environment variables for tokens and API keys, never hardcode credentials in configuration files
Use HTTPS or WSS for all network connections to protect data in transit
Pre-allow only necessary MCP tools in commands using specific names instead of wildcards

Avoid

Hardcoding API tokens or credentials in .mcp.json or plugin.json files
Using HTTP instead of HTTPS for MCP server connections
Using wildcard tool permissions like mcp__plugin_*__* which grants excessive access

Frequently Asked Questions

What MCP server types are supported?

Four types: stdio for local processes, SSE for cloud services with OAuth, HTTP for REST APIs, and WebSocket for real-time streaming.

How many MCP servers can a plugin have?

Plugins can configure multiple MCP servers in .mcp.json. Each server adds its tools with unique prefixes.

How do I authenticate to MCP servers?

SSE servers use automatic OAuth. HTTP and WebSocket servers use token headers. Stdio servers pass credentials via environment variables.

Are MCP credentials stored securely?

OAuth tokens are encrypted and managed by Claude Code. API tokens must use environment variables never stored in plugin files.

Why are my MCP tools not showing up?

Check server configuration is valid JSON. Use /mcp command to verify connection. Restart Claude Code after config changes.

How does MCP differ from direct API calls?

MCP provides structured tool discovery, automatic schema handling, and standardized communication protocol. MCP tools appear as native Claude Code tools.