Term MCP Deepseek

What OthmaneBlial/term_mcp_deepseek MCP server does

OthmaneBlial/term_mcp_deepseek MCP server lets MCP clients inspect a workspace and run policy-controlled terminal actions through a local service. Its design keeps model output advisory: text from DeepSeek does not execute directly. Instead, the server creates a versioned plan, applies policy, requests approval where required, runs a bounded process, and records the result.

The default inspect mode is intended for repository discovery. It blocks writes and project code, disables network access by default, and permits only the actions allowed by the configured policy. confirm and trusted modes broaden the permitted workflow, but the README notes that they are not an operating-system sandbox.

How it works

The service supports both HTTP and JSON-RPC over STDIO, using one dispatcher and tool catalog. The HTTP service exposes MCP calls at /mcp, along with session, event-stream, chat, and receipt endpoints. Protected HTTP routes use a bearer token. The web interface can build a low-risk plan, execute it, and display a receipt containing separate command, output, exit status, signal, permission, and signature information.

Execution includes pause, resume, cancellation, timeouts, output limits, process isolation, and workspace scoping. Receipts use HMAC signatures. A sharing-redaction operation removes command text, paths, arguments, and output before generating a new valid signature.

DeepSeek is used for advisory text through the chat path; it is not required for local MCP tools or the no-key inspection flow. The project also includes six schema-validated, inspect-only recipes for repository inspection, test discovery, log inventory, port configuration, and read-only boundary checks.

Setup and configuration

OthmaneBlial/term_mcp_deepseek MCP server requires macOS or Linux, Python 3.10–3.13, and pipx for the documented package installation path. Install the tagged repository with pipx, then run term-mcp serve from the workspace to start the HTTP service. The process prints a one-time bearer token for the local web interface.

A cloned checkout can be started with startup.sh; the script creates a virtual environment, installs the package, and delegates to the same term-mcp command. For MCP clients, use term-mcp stdio and set a narrow WORKSPACE_ROOT. The documented default is APPROVAL_MODE=inspect.

The command-line interface also provides health checks through doctor, guided no-key demos, receipt validation and display, recipe validation and execution, token generation, and version reporting. Docker support is available through the repository’s compose setup, which runs the service as UID/GID 10001 and mounts the example workspace read-only.

Limitations and notes

OthmaneBlial/term_mcp_deepseek MCP server is local software, not an operating-system sandbox. The documentation recommends using a disposable container or virtual machine for untrusted repositories when enabling broader command modes. Keep WORKSPACE_ROOT narrow, leave ALLOW_NETWORK=false unless network access is deliberate, and do not expose the HTTP service to an untrusted network.

The generated bearer token and in-memory sessions disappear when the process stops. HTTP routes such as /mcp, /sessions, /stream, and /chat require the bearer token, while health, the UI shell, demos, static assets, and the receipt schema are public. DeepSeek connectivity is optional for the local inspection workflow, so the server can operate without a DeepSeek API key.