Baseline MCP Server

Created By
yamanokua year ago
特定のWeb APIに関するBaselineの状況を提供するModel Context Protocolサーバー
Overview

What is Baseline MCP Server?

Baseline MCP Server is a Model Context Protocol server that provides the status of specific features related to the Baseline. It utilizes the Web Platform Dashboard API to retrieve the Baseline status of web API functionalities.

How to use Baseline MCP Server?

To use the Baseline MCP Server, set up the server in your local environment using Deno, and configure it in your MCP client settings (e.g., Claude Desktop or Visual Studio Code) to query web feature information.

Key features of Baseline MCP Server?

  • Functionality search using the Web Platform Dashboard API.
  • Provides Baseline status of features (widely, newly, limited, no_data).
  • Integration with various AI models via MCP.

Use cases of Baseline MCP Server?

  1. Checking the browser support status of web standards.
  2. Integrating with AI models for enhanced web feature analysis.
  3. Assisting developers in understanding the compatibility of web functionalities.

FAQ from Baseline MCP Server?

  • What is Baseline status?

Baseline status indicates the browser support level for web features: widely, newly, limited, or no_data.

  • How do I set up the server?

You can set up the server using Deno and configure it in your MCP client settings as shown in the documentation.

  • Is there a license for this project?

Yes, the Baseline MCP Server is licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
yamanoku
Star
31
Language
TypeScript
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