- Home
- Skills
- Agents & Orchestration
- MCP Connector Setup Assistant
MCP Connector Setup Assistant
Configure and troubleshoot MCP connectors for Claude Desktop, Cursor, and VS Code.
$8.50
Works with the AI Agents you already use
MCP Connector Setup Assistant
Example session with this skill installed
I want to connect GitHub to Claude Desktop on Windows. I don't have an API key yet — walk me through it step by step.
- Read your context and instructions
- Compiled the mcp connector setup
MCP Setup Result: GitHub → Claude Desktop (Windows)
Summary
Got you set up: created a fine-grained Personal Access Token for GitHub and generated the exact claude_desktop_config.json file for Claude Desktop on Windows. Everything is paste-ready.
Step-by-Step Guide
1. Create Your GitHub PAT
- Go to https://github.com/settings/tokens
- Click "Generate new token" → "Fine-grained token" (recommended — more secure than classic tokens)
- Set Repository access to "Only select repositories" (or "All repositories" if you prefer)
- Add permissions: Contents (read-only), Metadata (read-only), Pull requests (read-write)
- Click "Generate token" at the bottom
- Copy the token immediately — it looks like
github_pat_xxxxxxxxxxxxxxxxxxxxxxxxxxxx_yyyyyyyyyy. You won't see it again.
2. Save the Config File
Create or edit this file: %APPDATA%\Claude\claude_desktop_config.json
Paste the following JSON exactly
{
"mcpServers": {
"github": {
"command": "npx",
"args": ["-y", "github-mcp-server"],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "PASTE_YOUR_TOKEN_HERE"
}
}
}
}
Replace PASTE_YOUR_TOKEN_HERE with your actual token from Step 1.
3. Activate
- Fully quit Claude Desktop (click the tray icon → Quit, don't just close the window)
- Reopen Claude Desktop
- Type "list open pull requests" in chat — if you get results, you're connected.
Likely Errors
| Error | Fix |
|---|---|
401 Unauthorized | Check the token isn't expired; regenerate and re-paste into config |
ETIMEDOUT | npx may hang behind proxy; run npm install -g github-mcp-server, then change "command" to "github-mcp-server" and remove the -y arg |
Cannot find module | Verify package: npx view github-mcp-server version |
| JSON parse error | Ensure no trailing commas; use the exact template above |
Security Notes
- Store the token in the config file only — never commit
%APPDATA%\Claude\claude_desktop_config.jsonto git - If the token is compromised, revoke at https://github.com/settings/tokens immediately
- Use fine-grained tokens with minimum required permissions, not full-admin classic tokens
Connects securely to your tools. The creator never sees your data.
About this skill
The problem
Setting up Model Context Protocol (MCP) servers is brittle. Developers struggle with inconsistent config file locations, missing environment variables, and opaque connection errors across different AI agents.
What it does
- Identifies the correct npm package or GitHub repository for official MCP servers.
- Locates the specific API key acquisition path for services like GitHub, Slack, Notion, and Exa.
- Generates host-specific configuration files for Claude Desktop, Cursor, VS Code, and Codex.
- Maps common runtime errors like 401s, ETIMEDOUT, and JSON parse failures to concrete fixes.
- Provides network troubleshooting for corporate proxies and restricted registries.
Frameworks & tools
Supports Claude Desktop (macOS/Windows), Cursor, VS Code, and Codex. Configures connectors for GitHub, Slack, Notion, Exa, Tavily, Playwright, and Postgres.
Why this beats prompting it yourself
Generic LLMs often hallucinate npm package names or environment variable keys, leading to silent config failures. This skill uses a verified reference table for official servers and knows the exact filesystem paths for every major agent host.
Use cases
- Connecting local filesystems or databases to Claude Desktop.
- Setting up GitHub and Notion tools for a team using Cursor.
- Troubleshooting "Cannot connect to MCP server" errors in VS Code.
- Configuring Playwright for automated browser testing via an AI agent.
Known limitations
Does not write custom MCP server logic from scratch. Enterprise-only platform permissions must be handled manually on the service provider side.
How to use
Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scanned
Verified clean 1 month ago
- Passed all security checks, Safe to install
Requires