Skill

mcp-env-setup

Use when MCP servers fail due to missing .env, authentication errors, or env var issues. Provides tips for MCP environment setup when .env may be missing or incomplete.

Install

npx claudepluginhub randypitcherii/rpw-agent-marketplace --plugin rpw-building

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Tips for setting up MCP server environments when `.env` may be missing or incomplete.

SKILL.md

Similar Skills

skill-lookup

Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.

prompts.chat

159.9k

prompt-lookup

Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.

prompts.chat

159.9k

MCP Integration

6 files

Guides MCP server integration in Claude Code plugins via .mcp.json or plugin.json configs for stdio, SSE, HTTP types, enabling external services as tools.

plugin-dev

83.2k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitApr 6, 2026

Actions

View Source View Plugin View on GitHub View README

MCP Environment Setup

Tips for setting up MCP server environments when .env may be missing or incomplete.

When to Use

MCP server fails with auth/credential errors

.env file is missing or not found

User asks how to configure MCP servers

Cursor/Claude Desktop reports MCP connection failures

Setup Checklist

Locate .env.example — every MCP server in this repo ships one. Copy it:

cp .env.example .env

Fill required variables — open .env and replace placeholders with real values. Never commit .env.

Verify .env location — run_mcp.py typically loads from the server directory. Ensure .env is in the same directory as run_mcp.py or that the launcher's working directory is correct.

Check Cursor MCP config — Cursor reads MCP config from settings. Ensure:

Paths use ${CLAUDE_PLUGIN_ROOT} or equivalent so they resolve on the user's machine
No secrets in the config; credentials come from .env at runtime

Test manually — from the MCP server directory:

uv run python run_mcp.py

If it fails, the error usually indicates which env var is missing.

Common Issues

Symptom

Likely cause

Fix

"API key not found"

.env missing or wrong path

Copy .env.example to .env, fill values

"Invalid credentials"

Wrong or expired token

Re-auth (e.g. sf org login web for Salesforce, OAuth for Google)

"Module not found"

Dependencies not installed

uv sync in the MCP server directory

MCP shows "disconnected"

Config path wrong

Use ${CLAUDE_PLUGIN_ROOT} placeholders

No Hardcoded Paths

Never hardcode machine-specific paths (e.g. /Users/foo/...) in MCP config. Use ${CLAUDE_PLUGIN_ROOT} or env-driven placeholders so configs work across machines.