Reader Server

Created By
xinthinka year ago
Overview

what is Reader Server?

Reader Server is an MCP (Multi-Channel Publishing) server that exposes your Readwise Reader documents as resources, allowing for easy access and management of your reading materials.

how to use Reader Server?

To use Reader Server, set up the server by following the installation instructions on the GitHub repository, and then connect it to your Readwise Reader account to access your documents.

key features of Reader Server?

  • Exposes Readwise Reader documents as resources
  • Facilitates easy access to reading materials
  • Built with Python for flexibility and customization

use cases of Reader Server?

  1. Accessing and managing reading materials from Readwise in a centralized server.
  2. Integrating with other applications to enhance reading experiences.
  3. Automating the retrieval of reading resources for research purposes.

FAQ from Reader Server?

  • What is an MCP server?

An MCP server allows for the management and distribution of content across multiple channels, making it easier to access and utilize resources.

  • Is Reader Server free to use?

Yes! Reader Server is open-source and free to use for everyone.

  • What programming language is Reader Server built with?

Reader Server is built using Python.

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