File Context Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is File Context Server?

File Context Server is a Model Context Protocol (MCP) server designed to provide file system context to Large Language Models (LLMs), enabling them to read, search, and analyze code files with advanced caching and real-time file watching capabilities.

how to use File Context Server?

To use the File Context Server, install it via npm and start the server using the command npx file-context-server. You can then utilize various tools to list files, read file contents, search for patterns, and analyze code quality.

key features of File Context Server?

  • File Operations: Read file contents, list files with metadata, real-time file watching, and support for multiple encodings.
  • Code Analysis: Calculate cyclomatic complexity, extract dependencies, and analyze comments with quality metrics.
  • Smart Caching: Implement LRU caching, automatic cache invalidation, and performance metrics.
  • Advanced Search: Support for regex pattern matching, context-aware results, and multi-pattern searches.

use cases of File Context Server?

  1. Assisting LLMs in code comprehension and analysis.
  2. Enabling efficient code searching and retrieval in large codebases.
  3. Providing insights into code quality and complexity for developers.

FAQ from File Context Server?

  • Can File Context Server handle large codebases?

Yes! It is designed to efficiently manage and analyze large code files with advanced caching mechanisms.

  • Is there a limit on the file size that can be processed?

Yes, the maximum file size is configurable, and you can set it according to your needs.

  • How can I contribute to the project?

Contributions are welcome! Please refer to the Contributing Guide in the repository for details.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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