Usage Guide

Common patterns and best practices for using the AIRS MCP Filesystem Server.

Basic Operations

Reading Files

# In Claude Desktop
"Read the contents of my README.md file"

Claude will use the read_file tool to access and display the file contents.

Writing Files

"Create a new file called notes.txt with 'Hello World'"

This triggers the write_file tool with approval workflow.

Listing Directories

"Show me all files in my Documents folder"

Uses the list_directory tool to browse filesystem.

Common Workflows

Code Analysis

"Analyze all TypeScript files in my project for potential bugs"

The server will: 1. List files matching **/*.ts 2. Read each TypeScript file 3. Analyze code patterns 4. Report findings

Documentation Generation

"Create API documentation from my source code comments"

Workflow: 1. Read source files 2. Extract documentation 3. Generate markdown files 4. Write to docs directory

Project Setup

"Create a new Next.js project structure"

The server will: 1. Create directory structure 2. Generate configuration files 3. Set up initial templates

Security Patterns

Safe File Access

Always configure allowed paths:

[security.filesystem]
allowed_paths = [
    "~/projects/**/*",
    "~/Documents/**/*"
]

Approval Workflows

Enable approval for sensitive operations:

[security.operations]
write_requires_policy = true
delete_requires_explicit_allow = true

Advanced Patterns

See Examples & Use Cases for detailed examples.

See Integration Guide for ecosystem integration.