Coding Tools

What is Coding Tools?

Coding Tools is a model-neutral coding-agent runtime MCP server that exposes local coding primitives—such as repository inspection, file search/read, structured patch application, command execution, stdin session interaction, and Git status/diff—to any MCP client. It is not a prompt wrapper and does not include external agent accounts, cloud tasks, model routing, or plugin marketplaces.

How to use Coding Tools?

Install from PyPI using the provided install script or via uvx coding-tools-mcp. Start the server with either stdio (for MCP clients) or Streamable HTTP, binding it to a workspace directory. Configuration of permission modes, authentication, and remote tunnels is done through command-line flags and environment variables.

Key features of Coding Tools

• Model-neutral runtime, works with any MCP client.
• Workspace-bound file and command execution with security gates.
• Permission modes: safe, trusted, dangerous.
• Remote MCP support with tunnels (cloudflared, ngrok, devtunnel).
• Authentication: OAuth 2.1, bearer token, or no-auth read-only.
• Tool profiles: full, read-only, compat-readonly-all.
• Source-available license, not open source.

Use cases of Coding Tools

• Let an LLM inspect, edit, and test code in a local repository.
• Run automated coding workflows with structured patches and command execution.
• Provide a read-only remote access to code for review or exploration.
• Integrate with MCP clients like Claude Code or Cursor for agentic coding.

FAQ from Coding Tools

What does Coding Tools do that alternatives don’t?

It is a model-agnostic runtime focused on local coding primitives without external agent accounts, memory, cloud tasks, or model routing.

What are the runtime requirements?

Python, uvx/PyPI package; on Linux, Landlock for filesystem confinement of commands; optional image extra for view_image auto-resize.

How do I install Coding Tools?

Run the install script curl -fsSL https://raw.githubusercontent.com/xyTom/coding-tools-mcp/main/scripts/install.sh | bash or use uvx coding-tools-mcp.

What permission modes are available?

safe (default, with full permission gates), trusted (opens local-development gates), and dangerous (disables exec_command permission gates for isolated environments).

How does Coding Tools ensure security?

Workspace-bound paths, rejection of absolute/../symlink escapes, exec_command policy controls (network, destructive, shell expansion checks), secret filtering, Landlock on Linux, and permission modes. See SECURITY.md.