MCP or CLI?
Two ways to reach the same products. How to choose.
Orvio gives your agent two doors to the same files. Both need the same membership. Both serve only a product's latest release.
At a glance#
| Remote MCP | CLI | |
|---|---|---|
| What it is | A server your AI tool talks to | A command, orvio, in your terminal |
| You use it by | Asking your AI tool in plain words | Typing commands, or letting your agent run them |
| What you get | Pages, components, tokens and files, as the tool needs them | The whole release written into a folder |
| Sign-in | Your tool opens your browser once | orvio login opens your browser once |
| Best for | Taking inspiration, fetching one page or component, reading tokens | Starting a project from a product, scripts, offline work |
| Needs | An AI tool with remote MCP support | Node 20 or later |
Choose MCP when#
- You work inside an AI tool and want it to fetch only what it needs.
- You want one page, one component, or just the tokens.
- You want to ask in plain words and not leave the chat.
Choose the CLI when#
- You want the whole product in a folder, byte for byte.
- You want to work offline after the download.
- Your tool does not support remote MCP.
You can use both. Pull a product with the CLI, then point your agent at the folder. Use the same prompts without "Using Orvio". See the Prompt library.
What both guarantee#
- Latest release only. There is no way to ask for an older version.
- Read-only. Nothing you do changes the catalog.
- As authored. Files arrive byte for byte as the publisher wrote them, with a SHA-256 to check.
- Revocable. Remove any tool or device in Account › Integrations. See Approvals and revoking.
Where to go next#
Was this page clear? Yes · Not reallyEdit suggestions: support@orvio.design