Dolphin MCP Pilot vs Filesystem

A side-by-side look at the Dolphin MCP Pilot and Filesystem MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Dolphin MCP Pilot logoDolphin MCP PilotData Platforms · Remote HTTP/SSEAI agent interface to Apache DolphinScheduler: 58 MCP tools for workflow orchestration & data ops.43FairAuth: not declaredFilesystem logoFilesystemFile Systems · Local subprocess (stdio)Secure file operations with configurable access controls.85ExcellentAuth: no auth required

Verdict: choose Dolphin MCP Pilot for data platforms work over a hosted endpoint; choose Filesystem for file systems as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Dolphin MCP Pilot logoChoose Dolphin MCP Pilot when

  • You need dedicated capabilities in the Data Platforms domain.
  • You prefer a remote HTTP/SSE transport.
Explore Dolphin MCP Pilot

Filesystem logoChoose Filesystem when

  • You need dedicated capabilities in the File Systems domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like path, head, tail.
Explore Filesystem

Feature & specification comparison

Rows where the two servers differ are marked.

SpecDolphin MCP Pilot logoDolphin MCP PilotFilesystem logoFilesystem
CategoryData PlatformsFile Systems
Quality signal43/100 · Fair85/100 · Excellent
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listing Verified
GitHub stars2091,546
Directory activity 0 views 0 installs 0 upvotes 11 views 0 installs 0 upvotes
ToolsNot listed17

Tools & capabilities

Dolphin MCP Pilot tools

No tool names declared yet. Check the project README from the listing page.

Filesystem tools 17

  • path
  • head
  • tail
  • paths
  • content
  • edits
  • oldText
  • newText
  • dryRun
  • sortBy
  • source
  • destination
  • +5 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Dolphin MCP Pilot

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "dolphin-mcp-pilot": {
      "url": "http://localhost:8001/mcp/"
    }
  }
}

Filesystem

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem"
      ]
    }
  }
}

Frequently asked questions

Dolphin MCP Pilot is categorized under Data Platforms and uses a remote HTTP/SSE transport. Filesystem belongs to File Systems and uses a local stdio subprocess. Pick Dolphin MCP Pilot for data platforms work and Filesystem for file systems.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Dolphin MCP Pilot has no declared pricing — check the project's own site. Filesystem is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add dolphin-mcp-pilot and filesystem as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Dolphin MCP Pilot has a quality signal of 43/100 (Fair) with 0 views, 0 installs and 20 GitHub stars. Filesystem has 85/100 (Excellent) with 11 views, 0 installs and 91,546 GitHub stars.