Go server implementing Model Context Protocol (MCP) for executing shell commands.
If you want an AI assistant working directly with MCP Unix Shell, the mcp unix shell mcp server is the bridge. Go server implementing Model Context Protocol (MCP) for executing shell commands.
Go server implementing Model Context Protocol (MCP) for executing shell commands.
Once connected, the assistant can call these 7 tools directly:
execute_command — Execute a shell commandInput — - command (string): The command to executeOutput — - Command output with both stdout and stderrlist_recent_commands — List recently executed commandslist_allowed_commands — List all commands that the server is allowed to executeReturns — - List of allowed commands or "*" if all commands are allowedTools — The Tools tool exposed by this serverSetup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.
Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. MCP Unix Shell sits in that group, and the shape of its toolset — execute_command, Input, Output among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.
| Tool | What it does |
|---|---|
| execute_command | Execute a shell command |
| Input | - command (string): The command to execute |
| Output | - Command output with both stdout and stderr |
| list_recent_commands | List recently executed commands |
| list_allowed_commands | List all commands that the server is allowed to execute |
| Returns | - List of allowed commands or "*" if all commands are allowed |
| Tools | The Tools tool exposed by this server. |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.