cli
Package manager for AI agent tools. Search, install, and call 223+ APIs and CLIs from your terminal.
Links
README
From the repo.
clictl
A package manager for AI agents. Install any API, MCP server, or website as a CLI command. Your agent discovers it automatically.
Website: clictl.dev | Spec: clictl.dev/spec | Browse tools: clictl.dev/browse
Install
macOS / Linux:
curl -fsSL https://download.clictl.dev/install.sh | bash
Windows (PowerShell):
irm https://download.clictl.dev/install.ps1 | iex
Homebrew:
brew tap clictl/clictl
brew install clictl
What it does
You write a YAML spec describing an API. clictl install turns it into a CLI command and registers it as an MCP server. Both you and your agent use the same tool, the same way.
clictl install github
clictl run github repo-issues --owner octocat --repo hello-world
There are 220+ tools in the registry. Every install creates a skill file your agent reads and an MCP server entry, with no background processes or Docker containers.
Key commands
clictl search <query> # find tools in the registry
clictl install <tool> # install a tool (skill + MCP)
clictl install group <name> # install all tools in a group
clictl run <tool> <action> # run a tool action
clictl mcp-serve [tools...] # serve tools via MCP
clictl vault set <name> <value> # store a secret in the encrypted vault
See docs/cli-reference.md for the full command reference.
Security
Secrets live in an encrypted vault, not env vars or config files. MCP subprocesses run in OS-level sandboxes with env scrubbing and filesystem isolation. Published specs are signed and checksummed.
Details: docs/security.md | docs/securing-secrets.md
Spec format
A spec is a YAML file with four required fields. Each action defines its own URL, method, and auth.
spec: "1.0"
name: acme-platform
protocol: http
description: Acme Platform API
version: "2.0"
server:
url: https://api.acme.com/v2
auth:
env: ACME_KEY
header: "Authorization: Bearer ${ACME_KEY}"
actions:
- name: list-users
description: List all users
path: /users
Full spec reference: clictl.dev/spec | JSON Schema: clictl.dev/spec/1.0/schema.json
Documentation
Getting started | CLI reference | Spec format | Transforms | Code mode | MCP | Security | Memory | clictl.dev/docs
Contributing
Contributions are welcome. Please open an issue to discuss your idea before submitting a pull request.
git clone https://github.com/clictl/cli.git && cd cli
go build ./... && go test ./...
See CONTRIBUTING.md for details.
License
Apache License 2.0. See LICENSE for details.
clictl is a Soap Bucket LLC project. SOAPBUCKET and clictl are trademarks of Soap Bucket LLC.
Collected info
- ★ 0 stars
- Language: Go
- Source updated: 4/12/2026
Config for your environment
Replace {MCP_ENDPOINT_URL} with this MCP’s endpoint URL (from its repo or docs above). No API key — you connect directly.
Tool
OS
Config file: ~/.cursor/mcp.json
{
"mcpServers": {
"mcp-server": {
"url": "{MCP_ENDPOINT_URL}"
}
}
}Paste into mcpServers in the config file. Restart Cursor after saving.
If this MCP is also published on mcpchannel.ai, you can subscribe from Browse and use the gateway config there instead.