Skip to content

ycli mcp

MCP server control (reads + writes).

Usage:

$ ycli mcp [OPTIONS] COMMAND [ARGS]...

Options:

  • --help: Show this message and exit.

Commands:

  • start: Run the MCP server (tools namespaced...
  • methods: List what a server with the same flags...

ycli mcp start

Run the MCP server (tools namespaced tracker_, wiki_, forms_, datalens_, status_*).

Usage:

$ ycli mcp start [OPTIONS]

Options:

  • --toolsets TEXT: Comma-separated toolsets to serve: tracker, wiki, forms, datalens, core, all (core = a curated everyday profile; all = every service, the default). status_get and schema_get are always served. [default: all]
  • --tools TEXT: Comma-separated extra tool names to serve beyond the toolsets.
  • --exclude-tools TEXT: Comma-separated tool names to hide.
  • --read-only: Serve only read tools (hide every write-tagged tool); wins over --tools.
  • --tool-search: List a search tool and a call proxy instead of the tools (BM25); status_get and schema_get stay.
  • --transport [stdio|http]: stdio (default): one local client, credentials from the environment or from --profile. http: Streamable HTTP for many users, each signed in through Yandex ID (needs YCLI__MCP__BASE_URL and your Yandex OAuth app; see https://ycli.savaznatnov.dev/how-to/self-host-over-http/). [default: stdio]
  • --host TEXT: HTTP only: listen address (YCLI__MCP__HOST).
  • --port INTEGER: HTTP only: listen port (YCLI__MCP__PORT).
  • -o, --format [auto|json|yaml|pretty|csv|markdown|ndjson|name]: Output format (auto = pretty on a TTY, JSON when piped).
  • -y, --yes: Do not ask before an operation that deletes data or grants access.
  • --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown. A secret in the body (a password, a token) is printed as ***.
  • --profile NAME: Use the credentials saved as this profile (YCLI_PROFILE); the environment's and .env's are then not read. ycli auth profiles lists them.
  • -F, --field TEXT: Set any field of the request body: key=value, key[sub]=value for a nested one (JSON-coerced; repeatable). key=@FILE (@- for stdin) gives the file's text as it is; a string that starts with @ goes in JSON quotes ('text="@ivan"'). A flag of the command wins over it. Objects merge; a list replaces the one below it. Give a secret from a file, not typed here: a command line stays in the shell history. Write that file with no line break at its end (printf %s 'secret' > file), or the break goes out with the secret.
  • --body-file FILE: A JSON object (YAML in a .yaml / .yml file) laid under the request body: -F and the command's flags win over it. Objects merge; a list is replaced, not added to. YAML guesses types (no, 1.10): quote a value meant as text.
  • --help: Show this message and exit.

ycli mcp methods

List what a server with the same flags exposes, one name per line: tools by default.

--kind prompts lists the prompts and --kind resources the resource addresses; a prompt or a resource is served only when the tools it is made of are.

Usage:

$ ycli mcp methods [OPTIONS]

Options:

  • --toolsets TEXT: Comma-separated toolsets to serve: tracker, wiki, forms, datalens, core, all (core = a curated everyday profile; all = every service, the default). status_get and schema_get are always served. [default: all]
  • --tools TEXT: Comma-separated extra tool names to serve beyond the toolsets.
  • --exclude-tools TEXT: Comma-separated tool names to hide.
  • --read-only: Serve only read tools (hide every write-tagged tool); wins over --tools.
  • --tool-search: List a search tool and a call proxy instead of the tools (BM25); status_get and schema_get stay.
  • --kind [tools|prompts|resources]: What to list: tools (default), prompts, or resources (addresses and templates). [default: tools]
  • -o, --format [auto|json|yaml|pretty|csv|markdown|ndjson|name]: Output format (auto = pretty on a TTY, JSON when piped).
  • -y, --yes: Do not ask before an operation that deletes data or grants access.
  • --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown. A secret in the body (a password, a token) is printed as ***.
  • --profile NAME: Use the credentials saved as this profile (YCLI_PROFILE); the environment's and .env's are then not read. ycli auth profiles lists them.
  • -F, --field TEXT: Set any field of the request body: key=value, key[sub]=value for a nested one (JSON-coerced; repeatable). key=@FILE (@- for stdin) gives the file's text as it is; a string that starts with @ goes in JSON quotes ('text="@ivan"'). A flag of the command wins over it. Objects merge; a list replaces the one below it. Give a secret from a file, not typed here: a command line stays in the shell history. Write that file with no line break at its end (printf %s 'secret' > file), or the break goes out with the secret.
  • --body-file FILE: A JSON object (YAML in a .yaml / .yml file) laid under the request body: -F and the command's flags win over it. Objects merge; a list is replaced, not added to. YAML guesses types (no, 1.10): quote a value meant as text.
  • --help: Show this message and exit.