Please enable JavaScript to view this site.

Navigation: Take Command

Take Command MCP Server: User Guide

Scroll Prev Top Next More



The Take Command MCP server lets a compatible AI assistant use local TCC help and, with your permission, request information or actions in Take Command. MCP stands for Model Context Protocol. The server is TCMcpServer.exe; your assistant starts it as a local program and communicates with it over standard input and output. It does not need a network listener or an API token for the Take Command connection.

 

Connecting the server does not authorize access to your tabs. Tab access requires profile permissions and visible approval in Take Command. Some actions can execute commands, send keystrokes, or record unredacted terminal output. Approve only requests you understand and trust.

 

Before you begin

 

•Install Take Command and an MCP-compatible client, such as Claude Code, Codex CLI, Gemini CLI, or Vibe CLI. Configure and sign in to the client separately, following its own instructions.

•Find the absolute path to the installed TCMcpServer.exe. For access to a Take Command window, use the signed server from a protected installation; the broker checks both the server and host installation and signatures.

•Start Take Command and open the tab you want to share. For terminal text and the action tools, use an eligible local, non-elevated ConPTY profile tab. Individual tools may impose additional restrictions.

 

Local TCC help and syntax tools do not require a Take Command tab or a broker approval. The client may send information it receives to its model provider; review the client's and provider's privacy policies before sharing anything.

 

Configure your client

 

Choose the instructions for your client. These examples use C:\Program Files\JPSoft\TCMD37\TCMcpServer.exe as an example; replace it with the actual installed path. Use a user-local configuration, not a machine-specific path committed to a repository. No server arguments, shell wrapper, URL, or credentials are required.

 

Claude Code

 

claude mcp add --scope user --transport stdio take-command -- "C:\Program Files\JPSoft\TCMD37\TCMcpServer.exe"
claude mcp get take-command

 

Codex CLI

 

codex mcp add take-command -- "C:\Program Files\JPSoft\TCMD37\TCMcpServer.exe"
codex mcp list

 

Alternatively, add this section to %USERPROFILE%\.codex\config.toml:

 

[mcp_servers.take-command]
command = 'C:\Program Files\JPSoft\TCMD37\TCMcpServer.exe'

 

Gemini CLI

 

Merge this entry into the existing mcpServers object in %USERPROFILE%\.gemini\settings.json. Do not replace unrelated settings.

 

{
  "mcpServers": {
 "take-command": {
   "command": "C:\\Program Files\\JPSoft\\TCMD37\\TCMcpServer.exe"
 }
  }
}

 

Leave the client's trust or automatic-approval setting disabled. Gemini may disable MCP servers in an untrusted workspace.

 

Vibe CLI

 

Add this entry to %USERPROFILE%\.vibe\config.toml:

 

[[mcp_servers]]
name = "take_command"
transport = "stdio"
command = 'C:\Program Files\JPSoft\TCMD37\TCMcpServer.exe'

 

Restart the client if needed and check its MCP status or server list. Client versions and configuration interfaces can change; consult the client's documentation if its commands differ. Do not enable blanket auto-approval of MCP tools. Client-side approval and Take Command's own approval are separate.

 

Choose profile permissions

 

In Take Command, open Settings, select Profiles, and select the profile used by the tab. Enable only the permissions you need. These policies are independent and default to off; enabling one makes the corresponding request eligible but does not approve a client or a request.

 

Profile setting

What it permits the assistant to request

Allow MCP metadata policy

Session metadata and the reusable terminal context. Every profile in a shared session list must permit metadata.

Allow MCP transcript policy

Approved command lifecycle summaries, such as completion status and duration, without command text or output.

Allow MCP terminal text policy (requires transcript policy)

Approved terminal text, selected text, and scrollback searches. Both transcript settings must be enabled.

Allow MCP index metadata policy

Approved repository-index summaries, tracked-file change estimates, and prompt-level command resolution.

Allow MCP review actions policy

Requests to open approved files in read-only review tabs.

Allow MCP recording control policy

Requests to start an output-only recording.

Allow MCP terminal input policy

Requests to type text, optionally including Enter, into an eligible tab.

Allow MCP command execution policy

Requests to run a command in a separate TCC process.

 

Apply the settings. Changing an MCP profile policy cancels pending or active broker access, so the client must reconnect and request approval again.

 

Connect and approve a request

 

1.Ask your assistant to use the Take Command MCP server. For example, ask it to explain a TCC command using local help, or to list available Take Command windows before requesting terminal access.

2.For tab access, the assistant selects a discovered Take Command window and requests registration. Inspect the client and window shown by Take Command; approve only if you recognize them.

3.If prompted to share sessions, inspect every listed session and profile before approving. A reusable context is tied to that client connection and its approved sessions. A session's active state does not by itself identify the currently selected tab.

4.For a transcript, repository, review, recording, input, or command request, inspect the separate card and its exact target and contents before approving. Deny anything unexpected. Some action cards delay the Approve button so you have time to read them.

 

For example, you can ask: "Use Take Command's local help to explain DIR," or "Show me the recent command completion information for the approved tab." The latter needs an open context, transcript policy, and a separate approval. The assistant chooses how to use the tools; the server does not silently grant access just because you asked the assistant.

 

Only one MCP client can be registered with a Take Command window at a time. Context handles are specific to their server process and connection, expire, and cannot be reused after revocation or disconnect. If a context expires or is closed, restart the MCP server through the client and approve a new connection.

 

What the assistant can request

 

TCC information

 

Without tab access, the assistant can look up installed TCC help, check whether a name is a registered internal command, and examine command-line source structure. These tools do not execute the command. Syntax analysis is not the same as evaluating expansions or resolving a live prompt's aliases and paths. Live command resolution is a separate, approved request for an eligible idle tab and may disclose a resolved executable or batch-file path.

 

Terminal information

 

Approved metadata identifies session kind, state, and whether it is read-only; it does not include titles, profile names, paths, or terminal text. Approved command lifecycle information reports bounded row ranges, completion state, exit code, and duration, but not command names or output. An incomplete block does not prove a command is still running.

 

Terminal text and search requests require both transcript permissions and a fresh approval showing the text to be shared. Results are bounded, limited to printable ASCII, and filtered using heuristics. The filter can miss secrets; review the displayed text yourself before approving. Searches can withhold unsafe windows or omit older output, so a missing result does not prove that the text never appeared. Output, resizing, selection changes, or other changes while a request is pending can cause it to be refused.

 

Repository information and review tabs

 

With index metadata enabled, an approved request can return counts from the Git index or an estimate of changed tracked files. The host shows the directory and, when applicable, the paths to be shared. This is not a full Git status or diff: untracked files and staged changes are not evaluated, and timestamp-based comparisons can miss changes. The host uses the .git directory directly in the tab's reported directory; it does not search parent directories for a repository.

 

With review actions enabled, the assistant can request up to eight files to be opened as read-only review tabs. Inspect the directory, paths, and sizes in the approval card. The client receives the number opened, not file contents. Unsafe, changed, unsupported, or oversized files are refused.

 

Actions with additional risk

 

•Recording: A separately approved request starts a new output-only recording in %LOCALAPPDATA%\JPSoft\McpRecordings. It stops at 8 MiB or 10 minutes, whichever comes first. The card shows the exact path. Terminal output is not redacted and can include secrets in clear text, even though keyboard input is not recorded. The client is not given the path or contents by this tool. Existing recordings are not overwritten.

•Terminal input: The card shows the text and whether Enter will be sent. Input goes to whatever is receiving input in the tab: Enter can run a shell command, and text can be submitted to a password prompt. The input tool does not return terminal output.

•Command execution: The approved command runs as your user in a separate, non-interactive TCC process, not in the tab. The card shows the command, resolved command heads, and working directory. TCC can expand variables and functions; the child uses Take Command's environment and normal TCC startup, not the tab's environment. Treat approval as arbitrary code execution with your permissions. Output returned to the assistant is not redacted. The run stops after 10 seconds, and output can be truncated. A denied or lost response after execution does not undo effects the command already caused.

 

Recording, input, and command execution require their own default-off policies and a new approval for each request. They do not support SSH, serial, replay, or elevated tabs. Input and command execution also require a live, writable tab; command execution requires an idle prompt and rejects unsupported command forms, aliases, and unsafe or unresolved paths. The review card can disclose details locally even when those details are not returned to the client.

 

Activity and revocation

 

Open Tools > MCP Activity or use MCP Activity on the Tools ribbon to see broker and connection status and recent local activity. The history is bounded, in memory, and records event information and response sizes rather than terminal content. Revoke access cancels a pending approval or closes an active connection. You can also deny an individual card or close the client. Revocation prevents further use of that connection; it does not reverse an action that has already occurred or erase information already returned.

 

Signing, local access checks, and consent do not isolate Take Command from other processes running as your Windows user. Use a trusted account and workstation, and do not approve requests containing sensitive information you do not want the client or its provider to receive.

 

Troubleshooting

 

Problem

What to check

The client cannot start the server

Verify the absolute executable path and the client's stdio configuration. Check the client's MCP status and logs.

Local help is unavailable

Install Take Command help. For a nonstandard installation, set TCMCP_HELP_ROOT in the server process environment to the help\CMDebug\html directory.

No Take Command window is discovered

Start the signed host from a protected installation, use the signed installed server, and check MCP Activity. An unsigned development build is not sufficient for broker access.

Registration or sharing is refused

Check that another client is not already registered, that every listed profile permits metadata, and that you approved the correct window and sessions in time. Reconnect with a fresh server process after denial or closure.

A specific request is refused

Check its separate profile policy, eligibility, and approval card. A busy tab, changed session, selection, text, directory, policy, or expired context can invalidate a request. Some unsafe requests are refused before a card appears.

A command is refused

Use an eligible local non-elevated ConPTY tab at an idle prompt. Unsupported command forms, alias-resolved heads, non-default parsing settings, and unsafe paths may be refused.

Information is missing or incomplete

Results are bounded. Searches may withhold text; repository results do not include untracked files or a full diff; command output may be truncated.

 

For tool names, response shapes, detailed restrictions, and developer notes, see MCP Server technical documentation.