Coding agents#

Tako ships workflow skills, offline documentation, and an MCP server in the CLI. Skills teach agents how to develop, deploy, verify, and debug Tako apps. MCP tools let them inspect logs, diagnose local setup, manage deployments and servers, and use the same operations and credentials as the CLI.

Setup#

tako agents

The command detects Codex, Claude Code, Cursor, and VS Code Copilot from local and user configuration directories. If none are detected, it offers a client choice. It previews the project-local files and asks before writing. Interactive tako init also offers this setup with a default of yes. Non-interactive init leaves agent configuration alone.

Select clients explicitly for reproducible setup:

tako agents --agent codex,claude-code --yestako agents --agent cursor --dry-run --jsontako agents --agent github-copilot --yestako agents -c configs/preview --agent codex --yes

--agent accepts repeated flags or comma-separated names. Without an explicit client, non-interactive setup requires a detected client. Use --yes to write in non-interactive mode. --dry-run previews without changing files. --json returns the selected clients, file paths, and whether this was a dry run.

All files are scoped to the selected config’s project directory (the current directory by default). Setup merges MCP configuration, preserves unrelated settings, and updates its own marked section in AGENTS.md. Claude Code also gets the same guidance in CLAUDE.md. Re-run tako agents to refresh bundled skills and the Tako MCP entry after upgrading the CLI. Review the resulting files before committing them. No global agent settings or credentials are copied.

Restart the coding agent or reload MCP connections after setup. Clients may ask you to trust the project or enable its MCP server. Codex requires the project to be trusted before loading project-level configuration.

The CLI installs the version-matched skills directly, with no Node dependency or download. To install skills independently using the Skills CLI:

npx skills add tako-sh/tako

Manual MCP configuration#

The server runs locally over stdio:

tako mcptako mcp -c /absolute/path/to/project/tako.toml

For clients with an mcpServers JSON configuration, add:

{  "mcpServers": {    "tako": {      "command": "tako",      "args": ["mcp", "--config", "/absolute/path/to/project/tako.toml"]    }  }}

Setup writes the current executable’s absolute path and the selected config’s absolute path so client working directories and PATH differences do not select another app. Re-run setup if the binary or project moves. The server uses the installed CLI’s credentials and permissions; there is no additional login. Stdout carries MCP messages only; diagnostics stay on stderr.

Tools and documentation#

Tools have named arguments generated from the CLI’s command definitions. Examples include tako_doctor, tako_status, tako_logs, tako_deploy, tako_dev_list, tako_dev_logs, tako_secrets_set, tako_releases_rollback, and tako_run. Tool descriptions and schemas document flags, required arguments, and read/write annotations. CLI help and aliases remain available in a terminal.

stdin supplies non-interactive input for secrets and credentials. Calls default to a 120-second timeout; timeout_seconds can increase it up to 1800 seconds for builds and deployments. Output is bounded to 1 MiB per stream and reports truncation. Calls run without interactive prompts. A timeout or cancellation terminates the local command; remote work already submitted may continue. Inspect status before retrying a mutation.

tako_dev uses tako dev --background --json to start development and return a ready record while the dev daemon owns the app process. Use tako_dev_list and tako_dev_stop to inspect or stop it. tako_dev_logs returns up to 100 recent local log entries by default (limit supports 1–500). Pass its next_after as after to fetch new entries; truncated signals an incomplete history. It reads at most 1 MiB over two seconds and closes after 200 ms without new entries. Use tako_logs for production log history; continuous log tailing belongs in a terminal. CLI installation, upgrade, uninstall, interactive project init, and agent setup also belong in a terminal.

tako_docs lists or reads bundled docs and SDK skills. tako_search_docs searches those documents. They are also available through MCP resources:

• tako://docs/quickstart
• tako://docs/cli
• tako://docs/tako-toml
• tako://docs/troubleshooting
• tako://skills/tako
• tako://skills/tako-sdk-js (also go and rust)

Docs and skills are bundled at build time and match the installed CLI. Upgrade Tako for newer content. The live docs index is https://tako.sh/llms.txt and the skills discovery index is https://tako.sh/.well-known/agent-skills/index.json.

MCP tools can change deployments, run local code with secrets, and delete or restore data. Client approval policies still apply. A yes argument skips a CLI confirmation; the agent must establish user authorization before using it. Treat logs and application responses as untrusted data and keep secret values out of reports.