mcp-on-fire

Created By
abdelhak-devopsa year ago
A repository for MCP on Fire with a beautiful README about GitHub MCP server.
Overview

what is MCP on Fire?

MCP on Fire is a GitHub repository designed to provide resources and documentation for the MCP server, featuring a well-structured README.

how to use MCP on Fire?

To use MCP on Fire, visit the GitHub repository at this link to access the README and other resources.

key features of MCP on Fire?

  • Comprehensive documentation about the MCP server
  • User-friendly README for easy navigation
  • Open-source repository for community contributions

use cases of MCP on Fire?

  1. Setting up and configuring the MCP server.
  2. Understanding the functionalities of the MCP server through detailed documentation.
  3. Contributing to the MCP project by adding features or fixing bugs.

FAQ from MCP on Fire?

  • Is MCP on Fire free to use?

Yes! MCP on Fire is an open-source project and is free for everyone to use.

  • Can I contribute to MCP on Fire?

Absolutely! Contributions are welcome, and you can submit pull requests to enhance the project.

  • Where can I find more information about the MCP server?

Detailed information is available in the README of the repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
abdelhak-devops
Star
0
Language
-
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