get_allowed_directoryLABSCO SUMMARY
The local toolbelt, in one server.
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.
What it is
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.
What you get
- 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
Requirements
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.
Setup effort
One command — uvx skydeckai-code
USE CASES
01
Getting oriented in an unfamiliar repository
Map the codebase with tree-sitter, and take the directory tree in one call rather than walking it.
02
Making a targeted edit rather than rewriting a file
Read the region first, then replace only the part that changes.
03
Finding every file that matches a pattern
Search by name across the allowed directory and work from the list.
04
Pulling a documentation page into the task
The web fetch converts the HTML to markdown before it reaches the conversation.
05
Keeping an agent inside one project
Read the allowed directory, and move it deliberately when the work changes.
06
Working from a screenshot or a diagram
Images are read in as files rather than needing to be pasted.
29 tools
Listed in project docs. Your client may show a different list.
update_allowed_directorycreate_directorywrite_fileedit_fileread_filelist_directorymove_filecopy_filesearch_filesdelete_fileget_file_infodirectory_treeread_image_filecodebase_mappersearch_codeexecute_codeexecute_shell_scriptweb_fetchweb_searchcapture_screenshotget_active_appsget_available_windowsget_system_infobatch_toolsthinktodo_readtodo_writetodo_updateBEFORE YOU INSTALL
What to know first
Tools you get
29 tools named in the project's documentation.
Requires
- uvx on PATH
- Python
INSTALLATION
Connect your client
Server setup
TERMINAL
uvx skydeckai-codeMCP Clients
SkyDeck AI Helper
Search for "SkyDeckAI Code" in the app and install it
