Files
opencode-primer/mcp-servers/grep.md
Wesam Abousaid d75be39290 feat(mcp-servers): walkthroughs for Playwright, Context7, Sentry, Grep
Each walkthrough follows the same template: when to reach for it, setup
(verbatim opencode.json snippet), example prompts, capabilities and
limitations, gotchas, resources.

- playwright.md: browser automation — visual iteration loop, e2e
  scaffolding, bug repro from a URL
- context7.md: live, version-pinned library docs piped into the prompt,
  with the "resolve first, query second" pattern
- sentry.md: errors / traces / releases via OAuth (DCR), with the
  error-to-root-cause pattern
- grep.md: code search across public GitHub via the Vercel-hosted MCP

README.md ranks "when to add a server" against the cost of the extra
tokens it puts in the model's context every turn, with a tools-map
example for disabling chatty MCP tools per agent.

All endpoint URLs and package names link-checked at commit time.
2026-05-18 20:00:21 +02:00

2.4 KiB

Grep MCP (by Vercel)

Code search across public GitHub. Useful for "how do real codebases use X?" research without leaving OpenCode.

When to reach for it

  • Researching idiomatic usage of an API or pattern
  • Finding examples of a library you're new to
  • Comparing implementations across major open-source projects
  • Pre-deciding between two patterns by seeing which is more common

Setup

No API key needed for the public endpoint.

Add to opencode.json:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "gh_grep": {
      "type": "remote",
      "url": "https://mcp.grep.app"
    }
  }
}

Restart OpenCode. Verify:

opencode mcp list

Example prompts

use gh_grep to search for "useTransition" usage in React 19 codebases.
Find the 3 most common patterns and summarize when each is used.
search github via gh_grep for examples of "drizzle-orm" with
"transaction" — show me how production codebases structure transactions
use gh_grep to find how big public Tailwind v4 projects organize their
theme tokens. Pull 3 examples I can browse.

What it can do

  • Regex / literal search across public GitHub
  • Filter by language, repo, file path
  • Return code snippets with surrounding context
  • Pagination through large result sets

What it won't do

  • Search private repos (only public)
  • Replace GitHub's own search for finding issues or PRs (use the GitHub MCP for those)
  • Grade code quality — you'll see code that's wrong as often as code that's right

Patterns

Compare two patterns

use gh_grep to count occurrences of `useFormState` vs `useActionState`
in production React codebases (Next.js 15+). Report the ratio and the
top 5 examples for each.

Validate an approach

I'm thinking of using event sourcing for our audit log. Use gh_grep to
find production codebases doing this in TypeScript, and tell me what
patterns they share. Skip the "hello world" projects.

Gotchas

  • Public only — anything behind a private repo is invisible.
  • Quality varies — half of GitHub is half-finished side projects. Filter by repo popularity or maintainer when possible.
  • No semantic search — it's literal/regex, not "code that does X". Be precise in your queries.

Resources