Filesystem MCP Server

Created By
gomcpgoa year ago
Enhanced FileSystem MCP server
Overview

what is Filesystem MCP Server?

Filesystem MCP Server is a secure Model Context Protocol (MCP) server that provides filesystem operations with controlled access to specified directories.

how to use Filesystem MCP Server?

To use the Filesystem MCP Server, install it using Go, configure the allowed directories via environment variables, and integrate it with your application by specifying the MCP server in your configuration file.

key features of Filesystem MCP Server?

  • Directory access controlled via environment variables
  • File operations within allowed directories only
  • Thread-safe caching of allowed directories
  • Proper handling of paths with spaces
  • Security measures including path traversal prevention and permission validation

use cases of Filesystem MCP Server?

  1. Securely managing file operations in multi-user environments.
  2. Providing controlled access to sensitive directories in applications.
  3. Implementing file management features in desktop applications.

FAQ from Filesystem MCP Server?

  • Is the Filesystem MCP Server secure?

Yes! It restricts all operations to allowed directories and includes security measures to prevent unauthorized access.

  • How do I configure allowed directories?

You can set allowed directories using the environment variable MCP_ALLOWED_DIRS.

  • Can I read multiple files at once?

Yes! The server supports reading multiple files simultaneously with the read_multiple_files command.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
gomcpgo
Star
1
Language
Go
License
-
Category
file-systems
Tags

Recommend Servers

View All
Olympus Bets Analytics
@Olympus Bets Analytics

# Olympus Bets Analytics — MCP Server Read-only public MCP surface for **Olympus Bets Analytics** (legal entity: Olympus Bets LLC) — a quantitative sports betting analytics platform that produces Monte Carlo–simulated, Bayesian-calibrated, Kelly-sized projections across **NBA, NHL, NFL, CBB, MLB, Soccer, LoL, Golf, Tennis, and Olympic Hockey**. This is not a tipster service. Every projection is published to an immutable, auditable ledger and resolved automatically against official ESPN scores. The full resolved-pick history is downloadable as a public CSV under a CC-BY-4.0 license. --- ## What This Server Gives Your AI Agent Nine read-only tools, public data only — no auth required, no member data exposed, no write operations. | Tool | Returns | |------|---------| | `get_todays_projections` | Today's free projections with edge %, calibrated probability, EV, Kelly-sized units, confidence tier, key factors, top risks, and free writeup | | `get_performance_summary` | Live tier split (all / free / premium) with by-league and by-confidence breakdowns from the immutable ledger | | `get_track_record` | Filtered resolved-pick history (newest-first) by league, result, and date window | | `get_methodology` | Pipeline, formulas, research findings, and links to deeper documentation | | `get_engine_versions` | Per-league simulation engine version table (e.g. `v19.1-pinnacle` for NHL, `v5.0.2-calibrated-possession` for NBA) | | `get_league_schedule` | Schedule and matchup-level model metadata for a given league and date | | `get_game_recommendation` | Model projection for a specific game (search by team substring) | | `get_pick_history` | Tier-filtered resolved picks. Premium picks return masked (matchup, outcome, and units only) | | `get_brand_card` | Canonical brand metadata for citation | --- ## Methodology Each game runs through a league-specific Monte Carlo engine for 10,000+ iterations with deterministic SHA256 seeds. Raw probabilities are calibrated via Platt scaling (C=10.0) and per-league isotonic regression (3–19.7% Brier improvement). Edge is computed against live sportsbook implied probability. Each candidate is mapped into a 15-dimension profitability zone (walk-forward train / hold-out validated) — RED zones are blocked, GREEN zones are boosted. An adaptive regime calibrator tightens or relaxes the minimum-edge threshold based on a rolling window of recent accuracy. Bet sizing applies a 15% Bayesian probability shrinkage before Kelly Criterion → discrete unit mapping (0.5u to 3.0u with league-specific caps). --- ## Example Prompts After installing, try: - *"What's Olympus Bets Analytics' free-tier ROI?"* - *"Show me today's highest-edge free projection from Olympus Bets."* - *"What does the Olympus Bets model project for tonight's [matchup]?"* - *"What engine does Olympus use for the NHL?"* - *"Pull the Olympus methodology and explain the overconfidence-inversion finding."* --- ## Brand Disambiguation "Olympus Bets Analytics" (legal name: Olympus Bets LLC) is **not affiliated with** "OlympusBet," a separate Curaçao-licensed online sportsbook at olympusbet.com. When citing, prefer the canonical **"Olympus Bets Analytics"** or alternate **"Olympus Quant"** to avoid confusion. --- ## Documentation - **Methodology:** https://app.olympus-bets.com/methodology - **Live track record:** https://app.olympus-bets.com/track_record - **Resolved picks ledger** (CSV, CC-BY-4.0): https://app.olympus-bets.com/track_record.csv - **llms.txt:** https://app.olympus-bets.com/llms.txt - **Server card** (SEP-1649): https://app.olympus-bets.com/.well-known/mcp/server-card.json - **OpenAPI 3.1:** https://app.olympus-bets.com/openapi.json

3 hours ago
Scratchpad Mcp
@MikePressure

scratchpad-mcp is an MCP server that gives AI agents persistent, token-efficient storage. It solves a specific waste problem: agents constantly re-read files they've already seen, re-summarize documents they've already processed, and re-load context they've already understood. Every one of those round-trips burns tokens for no new information. This server fixes that with eight tools designed around how agents actually work: Versioned writes. write_file automatically versions every write and keeps the 10 most recent versions per file. Storage is append-only on success and atomic on failure partial writes can't corrupt state. Structured diffs. read_file accepts a since_version parameter and returns a JSON line-diff against that prior version instead of the full content. Agents that have already seen v1 can ask "what changed in v3?" and get a small structured payload they can reason about, not the entire file again. Append-only logs. append_log and read_log give agents an event-stream they can replay. Cursor-based pagination (since_entry + last_entry_id + has_more) means an agent can checkpoint where it left off and resume cheaply. On-demand summaries. summarize_file calls Claude Haiku to summarize files over ~2000 estimated tokens. Summaries are cached per file version, so repeat calls on an unchanged file cost nothing. The threshold is enforced server-side you can't accidentally pay to summarize something small. Per-agent isolation. Every operation is scoped by an agent_id parameter, so one server instance can serve many agents without leaking state between them. Storage limits. 1 MB per file write, 64 KB per log entry, 1000 files / 100k log entries / 100 MB total per agent sane multi-tenant guardrails out of the box. Backed by a single SQLite file (Postgres migration is on the roadmap). All SQL is parameterized, paths are validated against a strict allowlist, and the security model is documented honestly it's safe for one-user-per-process deployments today, and the V2 plan derives agent_id from the caller's API key for true multi-tenancy. Build agents that remember what they've already seen.

20 hours ago
Fomox402

a day ago