From grepai
Use when you need to register or update the GrepAI MCP server in Claude Code, Cursor, or Windsurf
npx claudepluginhub jugrajsingh/skillgarden --plugin grepaiThis skill is limited to using the following tools:
Configure grepai as an MCP server for AI coding assistants. Supports multiple IDEs, scopes, and workspace modes.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
Configure grepai as an MCP server for AI coding assistants. Supports multiple IDEs, scopes, and workspace modes.
Check all possible MCP registration locations and grepai config:
# Check existing MCP registrations
claude mcp list 2>/dev/null
Glob: .mcp.json
Glob: .claude/mcp.json
Read: ~/.claude.json (look for mcpServers section)
Check for workspaces:
grepai workspace list 2>/dev/null
Check for local project config:
Glob: .grepai/config.yaml
Summarize findings before proceeding:
which grepaiAsk via AskUserQuestion:
Which IDE to configure?
○ Claude Code (Recommended)
○ Cursor
○ Windsurf
○ Generic .mcp.json
For Claude Code, ask via AskUserQuestion:
Where should the MCP server be registered?
○ Project .mcp.json (Recommended for teams — shareable via git)
○ User global (~/.claude.json — available in all sessions)
○ Project .claude/mcp.json (this project only, not shared)
For Cursor: config goes to .cursor/mcp.json (project-level).
For Windsurf: config goes to .windsurf/mcp.json (project-level).
For Generic: config goes to .mcp.json at project root.
Only ask this if workspaces were detected in step 1.
Ask via AskUserQuestion:
Workspace mode?
○ With --workspace {NAME} (Recommended — auto-searches all projects without extra params)
○ Without workspace (agent must pass workspace parameter manually)
○ No workspace (single project mode)
If workspace selected, show the available workspaces and let user pick:
Which workspace?
○ {ws1} ({N} projects)
○ {ws2} ({N} projects)
Determine grepai binary path (which grepai). For Claude Code: use claude mcp add with scope (user/project) and optional --workspace {NAME}. For Cursor/Windsurf/Generic: write JSON to IDE-specific .mcp.json file, merging into existing config if present.
See references/mcp-configs.md for claude mcp add commands, JSON templates (basic, workspace, explicit path), and IDE target file paths.
For project-level .mcp.json files that teams share, do NOT gitignore them.
For .claude/mcp.json (project-specific, not shared), check if .claude/ is in .gitignore. If not, suggest adding it.
For Claude Code:
claude mcp list
Confirm grepai appears in the list.
For file-based configs:
Read the written file to confirm it's valid JSON.
Note: The MCP server connects on next IDE session start, not immediately.
Print IDE, scope, config path, command, workspace status, exposed MCP tools, and verification command. See references/mcp-configs.md for the summary template.