mcp-configurer

Configure and audit approved MCP servers across AI client platforms.

Updated May 27, 2026
One-click install
npx skills add https://github.com/rauffatali/my-research-copilot --skill mcp-configurer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-configurer
Source: https://github.com/rauffatali/my-research-copilot/tree/main/.agents/skills/mcp-configurer
Command: npx skills add https://github.com/rauffatali/my-research-copilot --skill mcp-configurer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents misconfigured or inconsistent MCP server setups across Codex, Cursor, Claude Code, Gemini CLI, and Antigravity so your approved tools are always available with the correct transports and auth wiring.

Core Features & Use Cases

  • Standardized approved server set: Enforces usage of the approved MCP servers (context7, github, huggingface, playwright) to avoid drift.
  • Client-specific configuration guidance: Shows where and how to update each client’s config files (and which command/transport shape to use).
  • Safe auth env wiring: Documents which environment variables to wire for bearer auth (e.g., GITHUB_PERSONAL_ACCESS_TOKEN, HF_TOKEN) without embedding secrets.

Quick Start

Ask the skill to audit your target client’s MCP configuration and ensure only the approved MCP servers (context7, github, huggingface, playwright) are configured with the right transports and auth environment variables.

Frequently Asked Questions about mcp-configurer

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

FAQPage Schema
How do I keep MCP server configurations consistent across multiple AI clients?

MCP client setup involves editing platform-specific configuration files to wire approved servers with correct transports and bearer auth environment variables, preventing tool access drift or authentication failures during development.

How do I configure bearer auth for GitHub and HuggingFace MCP servers?

To configure bearer auth for GitHub and HuggingFace MCP servers, wire environment variables like GITHUB_PERSONAL_ACCESS_TOKEN and HF_TOKEN into your client's MCP configuration without embedding the secrets directly in the config files.

Does this MCP configuration approach work with Cursor, Claude Code, and Gemini CLI?

Yes, this MCP configuration approach works with Cursor, Claude Code, and Gemini CLI by applying client-specific file paths and transport settings to maintain consistent tool access across all supported platforms.

What are the approved MCP servers I should configure for my AI coding tools?

The approved MCP servers you should configure for your AI coding tools are context7, github, huggingface, and playwright, which are standardized to avoid configuration drift across different client environments.

Why are my MCP servers not showing up correctly after editing client config files?

MCP servers may not show up correctly if the client-specific file paths or transport settings are wrong, or if bearer auth environment variables are missing, which prevents consistent tool access and proper authentication.