Skip to content
Browse documentation
cli

MCP and coding agents

Give your coding agent access to selected docs, project checks, and approved tools.

Connect your coding agent

Give your coding agent access to selected docs, project checks, and reviewed tools. MCP lets the agent call Smoothie directly instead of parsing terminal commands. You choose what it can access when you configure the connection.

text
You describe a task
Your coding agent calls Smoothie
Smoothie returns context or the result of an approved tool call

Your agent launches Smoothie as a foreground stdio process. There is no hosted server URL or daemon. Starting mcp serve in a separate terminal does not connect your agent.

What your agent can do

Base sessionDiscover search_capabilities. Without selected sources or tools, its catalog is empty.
--source or --frameworkSearch selected skills/docs and read_reference. Reading text does not execute it.
--projectList available native checks with list_verification_tasks; do not run them.
--project with --frameworkInspect the exact configured root with project_context and project_check.
Explicit tool grantsCall selected tools. Upstream sessions also offer connection_status.

The agent finds built-in controls through tools/list. Its call arguments cannot expand the configured access. For message formats and paged reads, see the MCP protocol reference.

To find and call tools, follow Context and tool discovery.

Add tool access

The default context connection has no execution grants. Enable only the tools you need through Tools and permissions. You can also connect external MCP tools.

Start with Connect a coding agent. Skills supply instructions, not permission. Your agent's own shell/file access stays separate, and retrieved text may reach its model provider.