Multi-File Reader MCP Server

Created By
strawgatea year ago
MCP Server for reading many files at the same time
Overview

What is Multi-File Reader MCP Server?

Multi-File Reader MCP Server is a FastMCP server designed to read the content of multiple files simultaneously, providing an efficient way to handle file operations.

How to use Multi-File Reader MCP Server?

To use the Multi-File Reader, add the specified configuration to your McpServer setup and ensure the read_files tool is included in your command arguments.

Key features of Multi-File Reader MCP Server?

  • read_files Tool: Reads multiple file paths and returns their content or error messages for unreadable files.
  • Progress Reporting: Provides real-time updates on the reading process.
  • Error Handling: Manages common file-related errors such as FileNotFoundError and PermissionError.

Use cases of Multi-File Reader MCP Server?

  1. Reading configuration files in bulk for applications.
  2. Processing logs from multiple sources for analysis.
  3. Extracting data from various text files for data aggregation.

FAQ from Multi-File Reader MCP Server?

  • Can the server read any file type?

Yes, as long as the file paths are correctly specified and accessible.

  • What happens if a file cannot be read?

The server will return an error message indicating the issue, such as FileNotFoundError or PermissionError.

  • Is there a limit to the number of files that can be read at once?

The limit depends on the server's configuration and available resources.

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