Claude-skill-registry-data mcp-setup
MCP server configuration, troubleshooting, and Todoist REST API workarounds
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry-data
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry-data "$T" && mkdir -p ~/.claude/skills && cp -r "$T/data/mcp-setup-terrytong-git-astrabashcontrol-bac" ~/.claude/skills/majiayu000-claude-skill-registry-data-mcp-setup && rm -rf "$T"
manifest:
data/mcp-setup-terrytong-git-astrabashcontrol-bac/SKILL.mdsource content
MCP Server Configuration
Configuration Locations
- User-level config:
(required for VSCode extension)~/.claude/settings.json - Project-level config:
(may not be loaded by VSCode extension).mcp.json - Environment file:
(copy from project~/.claude/.env
).env
Important Setup Notes
-
Node.js Required: Install via
(needed for all MCP servers using npx)brew install node -
Use Full Paths: VSCode may not have Homebrew in PATH, so use
instead of just/opt/homebrew/bin/npxnpx -
No Variable Interpolation: The
syntax does NOT work in${VAR}
. You must hardcode actual token values.~/.claude/settings.json -
Restart Required: After changing
, fully quit VSCode (Cmd+Q) and reopen. A simple reload may not pick up changes.~/.claude/settings.json -
OAuth for Google Services: First run of gdrive/gcal will open browser for authentication. Tokens cached in
or similar.~/.mcp-gdrive/
MCP Server Packages
| Server | Package | Env Variable |
|---|---|---|
| todoist | | |
| notion | | |
| ccg-bot | | |
| astra-bot | | |
| gdrive | | (path to OAuth keys) |
| gcal | | (path to OAuth keys) |
| github | | |
Note: The gdrive package is
@isaacphi/mcp-gdrive, NOT @anthropic/mcp-gdrive (that one doesn't exist on npm).
Example ~/.claude/settings.json
{ "mcpServers": { "gdrive": { "command": "/opt/homebrew/bin/npx", "args": ["-y", "@isaacphi/mcp-gdrive"], "env": { "GOOGLE_OAUTH_CREDENTIALS": "/Users/terrytong/Documents/CCG/ToolProj/gcp-oauth.keys.json" } }, "todoist": { "command": "/opt/homebrew/bin/npx", "args": ["-y", "@abhiz123/todoist-mcp-server"], "env": { "TODOIST_API_TOKEN": "your-actual-token-here" } }, "notion": { "command": "/opt/homebrew/bin/npx", "args": ["-y", "@notionhq/notion-mcp-server"], "env": { "NOTION_TOKEN": "your-actual-token-here" } } } }
Troubleshooting MCP
| Error | Solution |
|---|---|
| "Failed to connect" | Check Node.js: |
| 401 Unauthorized | Tokens cached from old config. Fully restart VSCode |
| Package not found | Search npm: |
| OAuth issues | Run manually: |
Pre-install packages globally:
/opt/homebrew/bin/npm install -g @isaacphi/mcp-gdrive @abhiz123/todoist-mcp-server
Todoist REST API Workaround
The Todoist MCP tool often returns 401 errors. Use the REST API directly via curl instead:
# Create a task (source .env first to get TODOIST_API_TOKEN) source /Users/terrytong/Documents/CCG/ToolProj/.env && curl -s -X POST "https://api.todoist.com/rest/v2/tasks" \ -H "Authorization: Bearer $TODOIST_API_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "content": "Task title here", "project_id": "2363714490", "due_string": "today" }' # Delete a task source /Users/terrytong/Documents/CCG/ToolProj/.env && curl -s -X DELETE "https://api.todoist.com/rest/v2/tasks/{task_id}" \ -H "Authorization: Bearer $TODOIST_API_TOKEN" # Get tasks source /Users/terrytong/Documents/CCG/ToolProj/.env && curl -s "https://api.todoist.com/rest/v2/tasks?project_id=2363714490" \ -H "Authorization: Bearer $TODOIST_API_TOKEN"
Key: Always
source .env before curl commands since MCP servers don't pick up bash exports.