MCP Advisor

Created By
olaservoa year ago
MCP Server to assist LLMs and humans on Model Context Protocol spec compliance and understanding
Overview

What is MCP Advisor?

MCP Advisor is an MCP server designed to assist both LLMs (Large Language Models) and humans in understanding and complying with the Model Context Protocol (MCP) specification. It provides comprehensive access to the MCP specification through prompts and resources.

How to use MCP Advisor?

To use MCP Advisor, you can install it as a dependency in your project or globally for command-line access. Configuration is required to integrate it with applications like Claude Desktop.

Key features of MCP Advisor?

  • Provides detailed explanations of MCP topics with full documentation context.
  • Access to various sections of the MCP specification, including complete schema and architecture.
  • Caches specification content locally to improve performance and reduce API calls.

Use cases of MCP Advisor?

  1. Assisting developers in understanding the Model Context Protocol.
  2. Providing precise spec information for LLMs in applications.
  3. Serving as a reliable resource for compliance with MCP specifications.

FAQ from MCP Advisor?

  • What is the Model Context Protocol?

The Model Context Protocol is a specification that defines how models should interact and share context.

  • How do I install MCP Advisor?

You can install it using npm with the command npm install mcp-advisor.

  • Can MCP Advisor be used with other LLMs?

Yes, MCP Advisor is designed to work with various LLMs and can be integrated into different applications.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
olaservo
Star
1
Language
JavaScript
License
MIT 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