go-mcp-file-server

A local Go-based MCP file-system server for querying and opening files via MCP (SSE endpoint), indexing files with SQLite and exposing MCP client remote calls (and optionally UI interactions).

Evaluated Apr 04, 2026 (17d ago)
Repo ↗ Infrastructure mcp file-system local-dev sqlite sse go
⚙ Agent Friendliness
38
/ 100
Can an agent use this?
🔒 Security
26
/ 100
Is it safe for agents?
⚡ Reliability
25
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
45
Documentation
35
Error Messages
0
Auth Simplicity
95
Rate Limits
0

🔒 Security

TLS Enforcement
10
Auth Strength
10
Scope Granularity
20
Dep. Hygiene
50
Secret Handling
50

Security details are not present in the provided README. TLS/auth are unknown; the example uses http://localhost:8888/sse which implies plaintext transport and likely no auth. Since it indexes local files and supports open operations, it should be verified for safe path handling (e.g., path traversal protections), least-privilege access, and appropriate network binding.

⚡ Reliability

Uptime/SLA
0
Version Stability
40
Breaking Changes
40
Error Recovery
20
AF Security Reliability

Best When

You want a local developer/desktop workflow where an MCP client can query and open files on the same machine (or a trusted LAN), and you control the server process and configuration.

Avoid When

You need robust security guarantees (authentication, authorization, and safe path handling) without further verification from the source code/docs; or you must expose the endpoint publicly.

Use Cases

  • Provide an AI/MCP client with a searchable view of local files
  • Enable agents to open/read files through an MCP tool interface
  • Index and browse a local directory tree for downstream processing

Not For

  • Serving untrusted remote users over the public internet without additional access controls
  • High-security environments requiring strong authz/authn and auditability (based on available info)
  • Large-scale enterprise file systems without documented performance/limits

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

OAuth: No Scopes: No

README provided does not mention authentication/authorization. Endpoint shown uses localhost SSE, suggesting no auth is configured or documented (needs confirmation from repo/code).

Pricing

Free tier: No
Requires CC: No

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • No documented auth/rate-limit/error semantics in provided README, so agents may need conservative retries and careful handling of failures.
  • Localhost SSE suggests the MCP client must run on the same host (or via trusted tunneling/LAN); remote deployment may require extra network/security setup.
  • Path traversal and safe file access constraints cannot be verified from README alone; agents should assume they may need explicit allowlists/constraints if supported.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for go-mcp-file-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered