Most setups reach this shape by stacking three or four servers. Here file operations, tree-sitter analysis, execution and web access come from one package, with a single workspace boundary governing all of them.
An MCP server for development work on a local machine, published previously as mcp-server-aidd. It covers file and directory operations, code analysis through tree-sitter across several languages, code execution, web fetching with HTML-to-markdown conversion, multi-engine web search, screenshots and image handling - all inside a workspace boundary you set.
- Files read, written, edited, copied, moved and deleted
- Directories created and listed, and a whole tree returned in one call
- A codebase mapped with tree-sitter across multiple languages
- Files found by name pattern, and file metadata read
- Images read into the conversation
- The workspace boundary read back, and moved when the work is somewhere else
- Code execution, web pages fetched as markdown, and multi-engine web search alongside the file tools
Uvx, and nothing else - run the package and point your client at it. It executes code and reaches the network, so set the workspace boundary before you give it work: one tool reports where it is pointed now, another moves it.
One command — uvx skydeckai-code