
Csv Mcp
io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.1Updated Oct 24, 2026
Parse, filter, and inspect CSV data locally. No network and no key.
Overview
Lets an assistant parse, filter and inspect CSV data locally, with no network access or API key required.
- What you can do
- This MCP server gives an assistant tools for working with CSV files on the local machine. According to its description, it can parse, filter and inspect CSV data. It runs as a local stdio process, so the data stays on the user's machine. The manifest does not list individual tool names.
- When to use it
- Useful when an assistant needs to read, narrow down or examine comma-separated data files during a local session, for example to answer questions about a spreadsheet export or check a dataset before further processing. It is a fit when the work should stay offline and no credentials should be involved. It is not intended for remote or shared data sources.},
- Requirements
- Runs as a local process over stdio, installed from the npm package @mrfentmen/csv-mcp, so Node.js and npm are needed. No authentication, environment variables or headers are declared, and the description states no network and no key are required. Desktop only; not available as a web executable.
Installation
In SourceWeft
- Open Csv Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v1.0.1LatestSep 22, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.