/ 디렉터리 / 플레이그라운드 / ref-tools-mcp
● 커뮤니티 ref-tools ⚡ 바로 사용

ref-tools-mcp

제작: ref-tools · ref-tools/ref-tools-mcp

Help coding agents find the right docs fast — public libs, private repos, internal PDFs — without burning context on wrong pages.

ref-tools/ref-tools-mcp (by Ref) provides two tools: a focused documentation search across public web, GitHub repos, and your private resources, plus a markdown-returning URL reader. Requires a REF_API_KEY.

왜 쓰나요

핵심 기능

라이브 데모

실제 사용 모습

ref-tools.replay ▶ 준비됨
0/0

설치

클라이언트 선택

~/Library/Application Support/Claude/claude_desktop_config.json  · Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "ref-tools": {
      "command": "npx",
      "args": [
        "-y",
        "ref-tools-mcp"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop → Settings → Developer → Edit Config 열기. 저장 후 앱 재시작.

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "ref-tools": {
      "command": "npx",
      "args": [
        "-y",
        "ref-tools-mcp"
      ],
      "_inferred": true
    }
  }
}

Cursor는 Claude Desktop과 동일한 mcpServers 스키마 사용. 프로젝트 설정이 전역보다 우선.

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "ref-tools": {
      "command": "npx",
      "args": [
        "-y",
        "ref-tools-mcp"
      ],
      "_inferred": true
    }
  }
}

Cline 사이드바의 MCP Servers 아이콘 클릭 후 "Edit Configuration" 선택.

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "ref-tools": {
      "command": "npx",
      "args": [
        "-y",
        "ref-tools-mcp"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop과 같은 형식. Windsurf 재시작 후 적용.

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "ref-tools",
      "command": "npx",
      "args": [
        "-y",
        "ref-tools-mcp"
      ]
    }
  ]
}

Continue는 맵이 아닌 서버 오브젝트 배열 사용.

~/.config/zed/settings.json
{
  "context_servers": {
    "ref-tools": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "ref-tools-mcp"
        ]
      }
    }
  }
}

context_servers에 추가. 저장 시 Zed가 핫 리로드.

claude mcp add ref-tools -- npx -y ref-tools-mcp

한 줄 명령. claude mcp list로 확인, claude mcp remove로 제거.

사용 사례

실전 활용법: ref-tools-mcp

How to stop the agent from hallucinating library APIs

👤 Coding agent users ⏱ ~10 min beginner

언제 쓸까: Agent confidently writes code that doesn't match the current library version.

사전 조건
  • Ref account + REF_API_KEY — Sign up at ref.tools (or whatever current Ref signup URL is)
흐름
  1. Ask a question grounded in docs
    Use ref_search_documentation to find how to use Prisma raw SQL queries in v5, then write an example.✓ 복사됨
    → Search hits with URLs; code cites them
  2. Verify
    ref_read_url on the top hit to confirm the API shape.✓ 복사됨
    → Clean markdown of the doc page

결과: Code that compiles against the actual library version.

함정
  • Search returns outdated docs for deprecated v-X — Include the version in the query: 'Prisma v5 raw SQL'
함께 쓰기: github

How to search internal engineering docs / PDFs with an agent

👤 Platform teams with internal runbooks ⏱ ~15 min intermediate

언제 쓸까: Agent needs to follow company-specific patterns, not whatever StackOverflow says.

사전 조건
  • Ref private sources indexed — Upload repos/PDFs to your Ref workspace (see Ref docs)
흐름
  1. Scope search to private
    ref_search_documentation 'internal auth pattern' with private sources only.✓ 복사됨
    → Internal results only
  2. Read the runbook
    ref_read_url on the top internal result.✓ 복사됨
    → Clean text of the runbook

결과: Internal-standards-compliant output.

함정
  • Internal docs go stale — agent still cites them — Tell the agent to check 'last updated' metadata and flag old content

How to fetch arbitrary URLs as clean markdown

👤 Anyone doing research + summarization ⏱ ~5 min beginner

언제 쓸까: You want the article text without nav/ads/JS junk.

흐름
  1. Read the URL
    ref_read_url https://some-blog.com/post — give me clean markdown.✓ 복사됨
    → Body text as markdown
  2. Summarize
    Now give me a 5-bullet summary.✓ 복사됨
    → Summary

결과: Clean content, fast.

함께 쓰기: markdownify

조합

다른 MCP와 조합해 10배 효율

ref-tools + github

Ground a PR review with official docs citations

For the Prisma migration in PR #1234, use ref_search_documentation to verify each API matches v5 docs, then comment on the PR.✓ 복사됨
ref-tools + markdownify

Combine Ref's doc search with markdownify for local PDFs not in Ref

Search Ref for our internal auth guidance, then markdownify the additional /specs/auth-v3.pdf that isn't indexed yet.✓ 복사됨

도구

이 MCP가 노출하는 것

도구입력언제 호출비용
ref_search_documentation query: str, sources?: str[] Ground a library or internal-doc question 1 Ref API call
ref_read_url url: str Pull a page as clean markdown 1 Ref API call

비용 및 제한

운영 비용

API 쿼터
Per Ref plan tier
호출당 토큰
Search hits: 500-2000 tokens. URL reads: can be 5k-20k
금액
Ref is a paid service (free tier available); check current pricing
Search first, then read only the top hit — chained reads are expensive.

보안

권한, 시크릿, 파급범위

최소 스코프: REF_API_KEY stored in env
자격 증명 저장: REF_API_KEY env var
데이터 외부 송신: Queries go to Ref's service; it in turn hits public web and your indexed private sources
절대 부여 금지: Don't share your workspace key broadly; use per-user keys if Ref supports them

문제 해결

자주 발생하는 오류와 해결

401 Unauthorized

Missing or invalid REF_API_KEY.

확인: echo $REF_API_KEY
Search returns stale results

Private-source re-index may be delayed; force re-index from Ref dashboard.

ref_read_url returns empty

Some sites block scraping. Use webpage-to-markdown via markdownify as a fallback.

Quota exceeded

Upgrade Ref plan or space out search usage.

대안

ref-tools-mcp 다른 것과 비교

대안언제 쓰나단점/장점
Context7 MCPYou want free public-library docs retrievalNo private source indexing
Apple Docs MCP / pg-aiguideYou only care about a specific platform's docsScoped; not general-purpose

더 보기

리소스

📖 GitHub에서 공식 README 읽기

🐙 열린 이슈 보기

🔍 400+ MCP 서버 및 Skills 전체 보기