Ref MCP

Created By
ref-toolsa year ago
Overview

what is Ref MCP?

Ref MCP is a ModelContextProtocol server that provides AI coding tools or agents with access to documentation for APIs, services, libraries, and more, ensuring they stay updated in a fast and token-efficient manner.

how to use Ref MCP?

To use Ref MCP, set it up as an MCP server either via the streamable-http server or the local stdio server. You can run it using the command npx ref-tools-mcp with the necessary API key.

key features of Ref MCP?

  • Access to comprehensive documentation for various technical platforms.
  • Tools for searching documentation and reading web pages.
  • Support for streamable HTTP servers for efficient data handling.

use cases of Ref MCP?

  1. Providing AI agents with up-to-date API documentation.
  2. Assisting developers in finding specific technical information quickly.
  3. Enabling seamless integration of documentation access in coding tools.

FAQ from Ref MCP?

  • What is the purpose of Ref MCP?

Ref MCP serves as a centralized documentation server for AI tools, enhancing their ability to access and utilize technical information.

  • How do I set up Ref MCP?

You can set it up using either the streamable-http server or the legacy stdio server by following the provided setup instructions.

  • Is there a visual tool for testing Ref MCP?

Yes, the MCP Inspector tool provides a visual interface for testing and monitoring interactions with the MCP server.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ref-tools
Star
3
Language
TypeScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago