About Servers
Servers is an MCP server published by shuliakovsky in the Developer Tools category: mCP Servers.
Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.
Install
git clone https://github.com/shuliakovsky/mcp-serversThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Ask AI
Ask AI about Servers
Powered by Claude · Grounded in docs
Security checks
- ✓README presentThe repository ships documentation.
- ✓License declaredUsable under a stated license.
- !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.
3 checks have not been run yet.
README
MCP Servers: Exec & Go Tools
This repository MCP-compatible servers written in Go:
-
exec-mcp-server — executes arbitrary shell commands via bash -c. Extremely dangerous and should only be used in fully sandboxed environments.
-
go-tools-server — provides a restricted set of safe Go tooling commands (vet, test, build, fmt, tidy, verify).
Both servers communicate over stdin/stdout and implement the MCP protocol (initialize, tools/list, tools/call).
Repository structure: exec-server/main.go - MCP server that executes arbitrary shell commands go-tools-server/main.go - MCP server that runs restricted Go tooling commands
- Exec MCP Server
Warning: This server can execute any shell command. Use only in trusted or isolated environments.
Features:
- Provides a single tool: exec
- Executes arbitrary commands via bash -c
- Optional working directory (cwd)
- Returns stdout and stderr
- 120-second timeout
Tool schema: name: exec description: Execute arbitrary shell commands via bash -c input: cmd: string (required) cwd: string (optional)
Example call: { "name": "exec", "arguments": { "cmd": "ls -la", "cwd": "/tmp" } }
- Go Tools MCP Server
This server runs only whitelisted Go commands.
Supported actions: vet -> go vet ./... test -> go test -json ./... build -> go build -o /dev/null ./... fmt -> go fmt ./... tidy -> go mod tidy verify -> go mod verify
Example call: { "name": "go_tool", "arguments": { "action": "test", "cwd": "/path/to/project" } }
Restrictions:
- 60-second timeout
- Only predefined commands allowed
- Returns stdout and stderr
Build: cd exec-server go build -o exec-mcp-server
cd ../go-tools-server go build -o go-tools-server
Run: ./exec-mcp-server ./go-tools-server
Example MCP interaction: initialize: { "jsonrpc": "2.0", "id": 1, "method": "initialize", "params": {} }
list tools: { "jsonrpc": "2.0", "id": 2, "method": "tools/list" }
call tool: { "jsonrpc": "2.0", "id": 3, "method": "tools/call", "params": { "name": "exec", "arguments": { "cmd": "echo hello" } } }
Security notes:
- exec-server must never be used in production
- go-tools-server is safer but still requires a trusted environment
- neither server isolates processes or limits resource usage
License: MIT
README copy captured when this server was indexed; it may lag the repository. The original is authoritative.