Adds Tasks & Files MCP Servers to the community servers list

[flesler]

Description

This pull request adds two new MCP servers to the community servers list:

1. Tasks MCP Server - An efficient task manager designed for LLM integration
2. Files MCP Server - Enables surgical code editing with symbol discovery

Server Details

• Server: New servers addition
• Changes to: Community servers list

Tasks MCP Server:

• Repository: https://github.com/flesler/mcp-tasks
• Ultra-efficient design with only 5 tools to reduce AI confusion
• Budget-optimized with batch operations and smart defaults
• Multi-format support (Markdown, JSON, YAML)
• Powerful search and filtering capabilities
• Auto WIP management and duplicate prevention

Files MCP Server:

• Repository: https://github.com/flesler/mcp-files
• Surgical code editing capabilities
• Symbol discovery across entire codebase
• Precise line-range editing with read_symbol + insert_text combo

Motivation and Context

These servers address common pain points in AI-assisted development:

Tasks Server solves:

• LLM confusion from too many task management tools
• Inefficient API usage in task operations
• Need for cross-format task file support
• Lack of intelligent task organization

Files Server solves:

• Difficulty finding symbols in large codebases
• Imprecise code editing leading to broken implementations
• Need for surgical precision in code modifications
• Inefficient search-and-replace workflows

How Has This Been Tested?

Both servers have been extensively tested with:

• Claude 3.5 Sonnet via Cursor IDE
• Multiple task management workflows (creation, search, filtering, status updates)
• Code editing scenarios including symbol discovery and precise modifications
• Multi-format file operations (Markdown, JSON, YAML)
• Large codebase navigation and editing

Breaking Changes

No breaking changes. These are new server additions that don't affect existing configurations.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Protocol Documentation
• My changes follows MCP security best practices
• I have updated the server's README accordingly
• I have tested this with an LLM client
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have documented all environment variables and configuration options

Additional context

Security Considerations:

• Tasks server is ultra-safe by default - AI cannot rewrite or delete tasks unless explicitly enabled
• Files server provides read-only symbol discovery and controlled write operations
• Both servers follow MCP security best practices with proper validation

Performance Optimizations:

• Tasks server uses batch operations to minimize LLM API calls
• Files server enables precise editing without full-file operations
• Both servers are designed to reduce token usage and improve response times

Design Philosophy:

• Minimal tool count to reduce AI confusion
• Type-safe implementations with full TypeScript support
• Real-time updates with automatic persistence
• Cross-platform compatibility

[olaservo]

Thanks for your contribution to the servers list. This has been merged in this combined PR: #2475

This is a new process we're trying out, so if you see any issues feel free to re-open the PR and tag me.