Filesystem MCP Server

Go server implementing Model Context Protocol (MCP) for filesystem operations.

Features

• Read/write files
• Create/list/delete directories
• Move files/directories
• Search files
• Get file metadata

Note: The server will only allow operations within directories specified via args.

API

Resources

• file://system: File system operations interface

Tools

• read_file
• Read complete contents of a file
• Input: path (string)

• Reads complete file contents with UTF-8 encoding

• read_multiple_files

• Read multiple files simultaneously
• Input: paths (string[])

• Failed reads won't stop the entire operation

• write_file

• Create new file or overwrite existing (exercise caution with this)

• Inputs:

  • path (string): File location
  • content (string): File content

• create_directory

• Create new directory or ensure it exists
• Input: path (string)
• Creates parent directories if needed

• Succeeds silently if directory exists

• list_directory

• List directory contents with [FILE] or [DIR] prefixes

• Input: path (string)

• move_file

• Move or rename files and directories
• Inputs:
  • source (string)
  • destination (string)

• Fails if destination exists

• search_files

• Recursively search for files/directories
• Inputs:
  • path (string): Starting directory
  • pattern (string): Search pattern
• Case-insensitive matching

• Returns full paths to matches

• get_file_info

• Get detailed file/directory metadata
• Input: path (string)

• Returns:

  • Size
  • Creation time
  • Modified time
  • Access time
  • Type (file/directory)
  • Permissions

• list_allowed_directories

• List all directories the server is allowed to access
• No input required
• Returns:
  • Directories that this server can read/write from

Usage with Claude Desktop

Install the server bash go install github.com/mark3labs/mcp-filesystem-server

Add this to your claude_desktop_config.json:

{ "mcpServers": { "filesystem": { "command": "mcp-filesystem-server", "args": [ "/Users/username/Desktop", "/path/to/other/allowed/dir" ] } } }

License

This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.

WIKIPEDIA: XMLHttpRequest (XHR) is an API in the form of a JavaScript object whose methods transmit HTTP requests from a web browser to a web server. The methods allow a browser-based application to send requests to the server after page loading is complete, and receive information back. XMLHttpRequest is a component of Ajax programming. Prior to Ajax, hyperlinks and form submissions were the primary mechanisms for interacting with the server, often replacing the current page with another one.

== History == The concept behind XMLHttpRequest was conceived in 2000 by the developers of Microsoft Outlook. The concept was then implemented within the Internet Explorer 5 browser (1999). However, the original syntax did not use the XMLHttpRequest identifier. Instead, the developers used the identifiers ActiveXObject("Msxml2.XMLHTTP") and ActiveXObject("Microsoft.XMLHTTP"). As of Internet Explorer 7 (2006), all browsers support the XMLHttpRequest identifier. The XMLHttpRequest identifier is now the de facto standard in all the major browsers, including Mozilla's Gecko layout engine (2002), Safari 1.2 (2004) and Opera 8.0 (2005).

=== Standards === The World Wide Web Consortium (W3C) published a Working Draft specification for the XMLHttpRequest object on April 5, 2006. On February 25, 2008, the W3C published the Working Draft Level 2 specification. Level 2 added methods to monitor event progress, allow cross-site requests, and handle byte streams. At the end of 2011, the Level 2 specification was absorbed into the original specification. At the end of 2012, the WHATWG took over development and maintains a living document using Web IDL.

== Usage == Generally, sending a request with XMLHttpRequest has several programming steps.

Create an XMLHttpRequest object by calling a constructor: Call the "open" method to specify the request type, identify the relevant resource, and select synchronous or asynchronous operation: For an asynchronous request, set a listener that will be notified when the request's state changes: Initiate the request by calling the "send" method: Respond to state changes in the event listener. If the server sends response data, by default it is captured in the "responseText" property. When the object stops processing the response, it changes to state 4, the "done" state. Aside from these general steps, XMLHttpRequest has many options to control how the request is sent and how the response is processed. Custom header fields can be added to the request to indicate how the server should fulfill it, and data can be uploaded to the server by providing it in the "send" call. The response can be parsed from the JSON format into a readily usable JavaScript object, or processed gradually as it arrives rather than waiting for the entire text. The request can be aborted prematurely or set to fail if not completed in a specified amount of time.

== Cross-domain requests ==

In the early development of the World Wide Web, it was found possible to brea