MCP-demo-blog-analyzer

Created By
WaelDataReplya year ago
A quickstart to test MCP blog analyzer client and a webpage visitor server
Overview

what is MCP-demo-blog-analyzer?

MCP-demo-blog-analyzer is a quickstart project designed to test the MCP blog analyzer client and a webpage visitor server.

how to use MCP-demo-blog-analyzer?

To use this project, clone the repository from GitHub, set up the necessary environment, and run the provided server commands to start analyzing blog data and tracking webpage visitors.

key features of MCP-demo-blog-analyzer?

  • Quickstart setup for testing blog analysis
  • Integration with webpage visitor tracking
  • Easy to use client-server architecture

use cases of MCP-demo-blog-analyzer?

  1. Analyzing visitor data on a blog
  2. Testing the performance of blog content
  3. Gathering insights on user engagement with blog posts

FAQ from MCP-demo-blog-analyzer?

  • What is the purpose of this project?

The project serves as a testing ground for the MCP blog analyzer and visitor server functionalities.

  • Is there any documentation available?

Yes, the project includes a README file with setup instructions and usage guidelines.

  • Can I contribute to this project?

Yes! Contributions are welcome, and you can submit pull requests on GitHub.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
WaelDataReply
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)

2 days ago