Let agents use tools through the CLI

Let agents use the CLI for native integration work. Skip unnecessary tool schema overhead.

Get startedBook a demo
metorial - zsh

Why the CLI

An interface agents already know

For integration work that fits the command line, the CLI is faster to reason about and cheaper to run than a full MCP tool surface.

  1. 01

    A CLI-native interface

    Agents use commands, flags, and help text they already understand, with no new tool schema to learn before they can act.

  2. 02

    Fewer tokens

    No large tool schema sits in context. Agents call commands directly and look up help only when they need it.

  3. 03

    Easy setup

    Install, sign in, and connect a provider in minutes, then run the same workflow locally, in scripts, or in CI.

Built for production

CLI speed, Metorial control

Raw CLI access is fast, but it is not enough for production agents. Metorial keeps CLI-driven integration work governed by identity, access policies, tracing, and Protoguard before anything reaches your systems.

Identity and access built in

CLI workflows stay tied to the same people, groups, agents, providers, and tools you govern across Metorial.

Every action is traceable

Metorial records who asked, which agent acted, what command ran, and how each provider request was handled.

Protected before it reaches systems

Protoguard reviews risky requests and policy decisions before CLI-driven agent work touches connected integrations.

Give agents a governed CLI path to your integrations

See how Metorial CLI lets agents use command-line workflows while identity, access control, tracing, and Protoguard stay in force. Book a demo or read the docs.

Book a demoRead the docs

Frequently asked questions

Common questions about CLI.

  1. What is the CLI?
    The CLI is the command-line interface for Metorial. It lets developers and AI agents connect providers, run integration workflows, test tools, and deploy governed access from the terminal, alongside the Metorial API and official SDKs.
  2. For command-shaped workflows, a CLI can keep agents close to interfaces they already understand: commands, flags, help text, scripts, and readable output. Metorial adds the enterprise controls raw CLI access usually lacks, including access policies, tracing, and tokenless auth.
  3. Yes. Use MCP when you want protocol-native integrations, dynamic tool discovery, or custom servers. Use the CLI when the workflow is better expressed as commands and automation. Both can live under the same Metorial governance model through custom MCP, providers, and policies.
  4. Yes. Metorial records the agent, user, provider, tool, request, response, deploy, and policy decision behind CLI-driven activity, so security and platform teams can review what happened through audit logs and observability.
  5. CLI workflows follow the same policies and access control as the rest of Metorial. You can scope access by user, group, agent, provider, and tool, then block actions that fall outside policy before they reach connected systems.
  6. Yes. Teams can sign in with existing SSO and SAML, and the CLI uses tokenless auth so scripts and CI do not need long-lived provider credentials.
  7. Protoguard reviews agent messages and tool requests, watches for risky provider changes, and blocks anything outside your policies before it reaches the systems your CLI workflows connect to.

Explore CLI

See what CLI can do, in detail.

Metorial API

Infrastructure

Everything in Metorial can be done through the API, from integrations and access control to identities, skills, and Magic MCP, with SDKs for Node, Python, and Go.

Custom MCP

Connectivity

Connect your own integrations and internal systems to AI agents by building them as custom MCP servers. Metorial hosts, scales, and secures them, with the same access control, tracing, and isolation as every other provider.

Continuous Deployment

Connectivity

Metorial deploys your custom MCP servers automatically from GitHub, GitLab, Azure DevOps, and Bitbucket. You ship them using the git workflow you already have.

Providers

Connectivity

Providers are the reusable toolkits and integrations agents use in Metorial. Build or connect one once, govern it centrally, and make it available to the teams and agents allowed to use it.

Tokenless Auth

Identity

Tokenless auth lets agents and people reach integrations based on identity instead of API keys. There are no secrets to share, rotate, or leak.

Policies + Access Control

Governance

Metorial gives you granular, role-based access control over users, agents, and admins, with policies across skills, integrations, and agents, built on your existing identity.

SAML

Identity

SAML lets your people sign in once with your identity provider and access the MCP servers and skills their role allows, fully integrated with Metorial's access control.

Audit Logs

Observability

Metorial records every interaction with the platform. Security and compliance teams have a complete, filterable history of what people, AI agents, and machine users did across your integrations and skills.

Provider Versions

Governance

Metorial version-controls every integration and skill, tracking changes to tools, configs, and specs. You can see what changed, pin versions, or update automatically.

Observability

Observability

Metorial logs every MCP message, tool call, and execution in real time, giving you one place to monitor errors, performance, and usage across all your agents and integrations.