Free Setup Tools for AI Developers

One-command setup scripts that configure MCP servers on your machine. Works on macOS, Linux, and Windows. Everything runs locally — zero data sent to us.

Supported platforms:
macOS.shLinux.shWindows.ps1

GitHub MCP Setup

Org-level access denied? spawn npx ENOENT?

Most Popular

Use GitHub repos, issues, and PRs directly from Claude, Cursor, or VS Code. Guides you through PAT creation with correct permissions.

Auto-detects Claude Desktop, Claude Code, Cursor, VS Code
Guides PAT creation with exact permissions needed
Verifies token works before configuring
Fixes 'spawn npx ENOENT' on Windows automatically
Backs up existing config before changes
View setup guide →
cB

Context Bharat MCP Setup

Your AI hallucinates Indian API code?

India-First

Get Razorpay, ONDC, Zerodha, UPI docs in your AI editor. Auto-configures for all MCP-compatible tools.

Indian API docs always up-to-date
Hindi + 5 regional languages
Free tier — no credit card needed
Works with Claude, Cursor, VS Code, Windsurf
+

MCP Doctor

MCP server not loading? No error message?

Coming Soon

Diagnoses and fixes the most common MCP issues: ENOENT errors, broken JSON configs, stale tokens, Node.js PATH problems.

Validates all MCP config files
Detects Node.js/NVM PATH issues
Tests MCP server connectivity
Checks token validity and permissions

Multi-Tool Config Sync

Maintaining 4 separate MCP configs?

Coming Soon

Keep MCP servers in sync across Claude Code, Cursor, VS Code, and Windsurf. Edit once, sync everywhere.

Detects all installed AI tools
One-command sync across all configs
Handles different config formats per tool
Dry-run mode to preview changes

Why free setup tools?

MCP is powerful but setup is painful. The #1 error developers face isspawn npx ENOENT — caused by Node.js PATH issues that differ across macOS, Linux, and Windows. Org-level PAT restrictions block GitHub MCP for most teams. JSON config files silently fail with no error message.

These scripts run entirely on your machine. No data is sent to Context Bharat. We built them because solving developer pain — even outside our core product — is the right thing to do.