io.github.bytedance/mcp-server-filesystem
MCP server · bytedance
- On your machine
io.github.bytedance/mcp-server-filesystem is an MCP server published by bytedance. Marketplaces we read that list it: 1 (Official MCP Registry). We first saw it on 2026-10-11 and have recorded no change since. As of our marketplace pass on 2026-10-11.
MCP server for filesystem access
- Marketplaces
- 1
- Where it runs
- On your machine
@agent-infra/mcp-server-filesystem - Largest published figure
- 39 233 Stars (GitHub) · Official MCP Registry
- First seen
- 2026-10-11
- Last change
- None recorded
- Verified mark
- Not marked
Where it is published
| Marketplace | Status | Version | Figures | Verified | First seen |
|---|---|---|---|---|---|
| Official MCP Registry (Open the registry record) | Listed | 1.0.0 | Forks (GitHub): 3 974 Stars (GitHub): 39 233 |
Not marked |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
What it can do
Runs on your machine: the AI tool starts this npm package locally: @agent-infra/mcp-server-filesystem
None of the marketplaces we read publishes its tools or the settings it asks for.
What changed
Nothing has moved on this plugin since we started watching it.
The publisher
bytedance · Repository: github.com/bytedance/ui-tars-desktop
Similar plugins
Its marketplaces publish too short a description to compare this plugin with others by meaning.
Is this your plugin?
Prove you maintain it with a file in its repository, a file on your domain or a DNS record. You get alerts when a marketplace lists it, drops it, changes its verified mark or what it asks for, and can put its remote endpoint on monitoring as a web service.
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.