MCPInstall

grepai-mcp-cursor

by yoanbernabeuAI & Agents

Integrate GrepAI with Cursor IDE via MCP. Use this skill to enable semantic code search in Cursor.

Installs
595
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/yoanbernabeu/grepai-skills --skill grepai-mcp-cursor
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads grepai-mcp-cursor automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

GrepAI MCP Integration with Cursor

This skill covers integrating GrepAI with Cursor IDE using the Model Context Protocol (MCP).

When to Use This Skill

  • Setting up GrepAI in Cursor
  • Enabling semantic search for Cursor AI
  • Configuring MCP for Cursor
  • Troubleshooting Cursor integration

What is Cursor?

Cursor is an AI-powered IDE that supports MCP for external tools. GrepAI integration gives Cursor's AI:

  • Semantic code search beyond simple text matching
  • Call graph analysis for understanding dependencies
  • Index-based code navigation

Prerequisites

  1. GrepAI installed
  2. Ollama running (or other embedding provider)
  3. Project indexed (grepai watch)
  4. Cursor IDE installed

Configuration

Step 1: Create MCP Config File

Create .cursor/mcp.json in your project root:

{
  "mcpServers": {
    "grepai": {
      "command": "grepai",
      "args": ["mcp-serve"]
    }
  }
}

Step 2: Restart Cursor

Close and reopen Cursor for the config to take effect.

Step 3: Verify

Ask Cursor's AI:

"Search the codebase for authentication"

Cursor should use the grepai_search tool.

Global Configuration

For GrepAI in all Cursor projects, use global config:

Location

  • macOS: ~/.cursor/mcp.json
  • Linux: ~/.cursor/mcp.json
  • Windows: %APPDATA%\Cursor\mcp.json

Content

{
  "mcpServers": {
    "grepai": {
      "command": "grepai",
      "args": ["mcp-serve"]
    }
  }
}

Per-Project Configuration

For project-specific settings:

{
  "mcpServers": {
    "grepai": {
      "command": "grepai",
      "args": ["mcp-serve"],
      "cwd": "/absolute/path/to/project"
    }
  }
}

Available Tools

Once configured, Cursor has access to:

ToolDescription
grepai_searchSemantic code search
grepai_trace_callersFind function callers
grepai_trace_calleesFind function callees
grepai_trace_graphBuild call graphs
grepai_index_statusCheck index health

Usage Examples

Finding Code

Ask Cursor:

"Find code that handles user login"

Cursor uses grepai_search to find semantically related code.

Understanding Dependencies

Ask Cursor:

"What functions call validateToken?"

Cursor uses grepai_trace_callers to show all callers.

Code Navigation

Ask Cursor:

"Show me the call graph for processPayment"

Cursor uses grepai_trace_graph to display dependencies.

Cursor Settings Integration

Enable MCP in Settings

  1. Open Cursor Settings (Cmd+, / Ctrl+,)
  2. Search for "MCP"
  3. Ensure MCP is enabled

Verify MCP Status

  1. Open Command Palette (Cmd+Shift+P / Ctrl+Shift+P)
  2. Search "MCP"
  3. Check connected servers

Windsurf Configuration

Windsurf uses the same MCP format as Cursor:

Location

Create .windsurf/mcp.json:

{
  "mcpServers": {
    "grepai": {
      "command": "grepai",
      "args": ["mcp-serve"]
    }
  }
}

Multiple Projects Setup

Option 1: Separate Configs

Each project has its own .cursor/mcp.json with appropriate cwd.

Option 2: Workspaces

# Create workspace
grepai workspace create dev
grepai workspace add dev /path/to/project1
grepai workspace add dev /path/to/project2

{
  "mcpServers": {
    "grepai": {
      "command": "grepai",
      "args": ["mcp-serve", "--workspace", "dev"]
    }
  }
}

Environment Variables

If GrepAI uses environment variables (like API keys):

{
  "mcpServers": {
    "grepai": {
      "command": "grepai",
      "args": ["mcp-serve"],
      "env": {
        "OPENAI_API_KEY": "sk-..."
      }
    }
  }
}

Better: Set environment variables in your shell profile instead.

Troubleshooting

MCP Not Recognized

❌ Problem: Cursor doesn't see GrepAI tools

✅ Solutions:

  1. Check file location: .cursor/mcp.json in project root
  2. Verify JSON syntax (no trailing commas)
  3. Restart Cursor completely
  4. Check grepai is in PATH

Search Returns Nothing

❌ Problem: Empty search results

✅ Solutions:

  1. Ensure index exists: grepai status
  2. Run grepai watch first
  3. Verify working directory

Connection Errors

❌ Problem: MCP connection failed

✅ Solutions:

  1. Test manually: grepai mcp-serve
  2. Check Ollama: curl http://localhost:11434/api/tags
  3. Look at Cursor's developer console for errors

Wrong Results

❌ Problem: Results from wrong project

✅ Solutions:

  1. Set explicit cwd in config
  2. Check you opened the right folder in Cursor
  3. Use grepai_index_status to verify

Performance Tips

  1. Background daemon: Keep grepai watch --background running
  2. Use compact mode: MCP tools use compact by default
  3. Limit results: AI will request appropriate limits
  4. Index regularly: Especially after git pull

Comparison: Cursor vs Claude Code

FeatureCursorClaude Code
Config location.cursor/mcp.json~/.claude/mcp.json
Setup commandManual JSONclaude mcp add
Project scopePer-project or globalGlobal
IDE integrationNativeTerminal

Best Practices

  1. Version control: Add .cursor/mcp.json to git (without secrets)
  2. Team setup: Document MCP config in README
  3. Keep index fresh: Run watch daemon
  4. Test locally: Verify grepai mcp-serve works first
  5. Use workspaces: For multi-project setups

Removing Integration

Delete .cursor/mcp.json and restart Cursor.

Or remove just GrepAI:

{
  "mcpServers": {
    // Remove grepai entry
  }
}

Output Format

Successful Cursor setup:

✅ GrepAI MCP Integration for Cursor

   Config: .cursor/mcp.json
   Server: grepai mcp-serve
   Status: Ready

   Available tools:
   - grepai_search
   - grepai_trace_callers
   - grepai_trace_callees
   - grepai_trace_graph
   - grepai_index_status

   Cursor AI can now search your code semantically!

   Test: Ask Cursor "search for authentication code"

FAQ

What does the grepai-mcp-cursor skill do?

Integrate GrepAI with Cursor IDE via MCP. Use this skill to enable semantic code search in Cursor.

How do I install grepai-mcp-cursor?

Run npx skills add https://github.com/yoanbernabeu/grepai-skills --skill grepai-mcp-cursor in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/grepai-mcp-cursor/ (personal) or .claude/skills/grepai-mcp-cursor/ (project).

Which AI agents can use grepai-mcp-cursor?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is grepai-mcp-cursor safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains grepai-mcp-cursor?

It is published by yoanbernabeu in yoanbernabeu/grepai-skills. It has 595 recorded installs.

More from yoanbernabeu/grepai-skills

View all →

grepai-search-basics

yoanbernabeu/grepai-skills

Basic semantic code search with GrepAI. Use this skill to learn fundamental search commands and concepts.

Education & Science908 installs

grepai-search-advanced

yoanbernabeu/grepai-skills

Advanced search options in GrepAI. Use this skill for JSON output, compact mode, and AI agent integration.

AI & Agents828 installs

grepai-trace-graph

yoanbernabeu/grepai-skills

Build complete call graphs with GrepAI trace. Use this skill for recursive dependency analysis.

805 installs

grepai-ollama-setup

yoanbernabeu/grepai-skills

Install and configure Ollama for local embeddings with GrepAI. Use this skill when setting up private, local embedding generation.

AI & Agents799 installs

grepai-trace-callers

yoanbernabeu/grepai-skills

Find function callers with GrepAI trace. Use this skill to discover what code calls a specific function.

787 installs

grepai-search-tips

yoanbernabeu/grepai-skills

Tips and best practices for effective GrepAI searches. Use this skill to improve search result quality.

Code Quality & Workflow781 installs

Popular ai & agents skills

View category →

google-agents-cli-publish

google/agents-cli

This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini", "publish to Gemini" (formerly Gemini Enterprise), or needs guidance on the agents-cli publish gemini command. Also use when the user wants to "manage agents in Agent Registry", "list/update/delete registered agents", or "register an MCP server". Covers ADK vs A2A registration modes, programmatic and interactive usage, flag reference, auto-detection from deployment metadata, Agent Registry fleet management, and troubleshooting. Part of the agents-cli skills suite. Do NOT use for deployment (use google-agents-cli-deploy).

AI & Agents513.9K installs

google-agents-cli-eval

google/agents-cli

This skill should be used when the user wants to "run an evaluation", "evaluate my agent", "evaluate my ADK agent", "write an eval dataset", "analyze eval failures", "compare eval results", "optimize agent", or needs guidance on the Gemini platform eval methodology and the Quality Flywheel. Covers eval metrics, dataset schema, LLM-as-judge scoring, and common failure causes. Applies to any agents-cli project, whatever framework the agent is written in. Do NOT use for agent API code patterns (ADK: use google-agents-cli-adk-code), deployment (use google-agents-cli-deploy), or project scaffolding (use google-agents-cli-scaffold).

AI & Agents513.5K installs

skill-creator

anthropics/skills

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

OfficialAI & Agents416.4K installs

codex-pet

prime-skills/runcomfy-agent-skills

Codex Pet generator on RunComfy. Build a Codex-compatible Codex Pet spritesheet.webp + pet.json from a single reference image, drop it into ${CODEXHOME:-$HOME/.codex}/pets/ / and Codex picks it up as a custom Codex Pet next to the 8 built-ins. This skill produces the exact Codex Pet atlas Codex expects (1536x1872 PNG/WebP, 8 cols x 9 rows, 192x208 cells, 9 animation states — idle, running-right, running-left, waving, jumping, failed, waiting, running, review). Calls OpenAI GPT Image 2 edit ONCE via the local RunComfy CLI as runcomfy run openai/gpt-image-2/edit to produce a canonical Codex Pet pose, then assembles all 9 animation rows programmatically with ImageMagick micro-transforms — no Codex Pro, no $imagegen, no OPENAIAPIKEY required, only RUNCOMFYTOKEN. Triggers on "codex pet", "create codex pet", "make codex pet", "hatch codex pet", "/hatch image", "desktop pet codex", "codex pets", "spritesheet.webp", or any explicit ask to build a custom pet for OpenAI Codex.

AI & Agents402.1K installs

full-output-enforcement

leonxlnx/taste-skill

Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.

AI & Agents401K installs

executing-plans

obra/superpowers

Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available

AI & Agents245.7K installs