MCP-servers

Created By
rascal-3a year ago
This is "a" version focued on enabling to web browsing from Claude app of model context procol projects.
Overview

what is MCP-servers?

MCP-servers is a project focused on enabling web browsing capabilities from the Claude app, enhancing its functionality for users.

how to use MCP-servers?

To use MCP-servers, integrate it with the Claude app, allowing users to access web browsing features directly within the app interface.

key features of MCP-servers?

  • Seamless integration with the Claude app for web browsing
  • Enhanced user experience with direct access to web content
  • Support for various web functionalities within the app

use cases of MCP-servers?

  1. Accessing online resources and information directly from the Claude app.
  2. Enabling users to browse the internet while using the Claude app for other tasks.
  3. Improving productivity by combining web browsing with app functionalities.

FAQ from MCP-servers?

  • Is MCP-servers compatible with all versions of the Claude app?

Yes! MCP-servers is designed to work with all current versions of the Claude app.

  • How do I report issues with MCP-servers?

You can report issues by creating an issue on the GitHub repository.

  • Is there any cost associated with using MCP-servers?

No, MCP-servers is free to use.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
rascal-3
Star
0
Language
JavaScript
License
MIT license
Tags

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)

20 hours ago
Gpt Scrambler

2 days ago