Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/superradcompany/tool-cli/llms.txt

Use this file to discover all available pages before exploring further.

Scan a directory and report what tool-cli finds about the MCP server inside it — the runtime type (Node.js, Python, binary), transport (stdio or HTTP), entry point file, and suggested package name. Use this before running tool init on an existing project to confirm detection looks correct.

​
Synopsis

tool detect [PATH] [OPTIONS]

​
Options

​
path
string
Path to the project directory to analyze. Default: . (current directory).
​
-e, --entry
string
Override the detected entry point. Use this when auto-detection picks the wrong file.
​
--transport
string
Override the detected transport. One of stdio or http.
​
-n, --name
string
Override the detected package name.
​
--verify
boolean
After detection, start the server and send an MCP initialize request to confirm it responds correctly.
​
-y, --yes
boolean
Skip the confirmation prompt when using --verify.

​
Examples

# Analyze the current directory
tool detect

# Analyze a specific project
tool detect ./my-server

# Override the detected entry point
tool detect -e src/main.py

# Override the detected transport
tool detect --transport http

# Override the detected package name
tool detect -n custom-name

​
What it detects

tool detect inspects the directory and reports:
  • Type — node, python, or binary, inferred from project files (package.json, pyproject.toml, compiled artifacts, etc.)
  • Transport — stdio or http, inferred from source code patterns
  • Entry point — the main file that starts the server (e.g., src/index.js, server.py)
  • Package name — taken from package.json, pyproject.toml, or the directory name as a fallback
Run tool detect before tool init any time you are converting an existing project. If the output looks wrong, pass -e, --transport, or -n to correct it, then run tool init with the same overrides.
tool detect is read-only and never writes files. It is safe to run on any directory.

Build docs developers (and LLMs) love

Get started for freeTalk to us