What is the purpose of this CLI?
It provides a command‑line abstraction that unifies access to Arcee AI, TESS, and MCP APIs without reimplementing them, making it easier to interact with all three from one tool.
@diegofornalha
Basic information
Servidor MCP para integração com a API TESS, permitindo utilizar agentes TESS via protocolo MCP
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
A command-line interface (CLI) that integrates third‑party APIs – Arcee AI, TESS, and the official Model Context Protocol SDK (@sdk‑mcp) – into a unified abstraction layer. It follows Clean Architecture and Domain‑Driven Design (DDD) and does not reimplement the underlying services; it provides a standardized way to access them.
Install the project (no explicit install command in README), then invoke commands such as arcee mcp-tools listar, arcee mcp-tools executar tool1 '{"param1":"valor1"}', arcee tess listar, arcee chat "sua pergunta", and arcee generate "prompt". Configuration details are not documented in the README; the CLI consumes the APIs of TESS‑MCP, Arcee AI, and MCP via their respective endpoints.
It provides a command‑line abstraction that unifies access to Arcee AI, TESS, and MCP APIs without reimplementing them, making it easier to interact with all three from one tool.
No. It consumes the official MCP SDK ( @ sdk‑mcp ) and the TESS APIs as external services. The CLI is only a client; all protocol logic remains in those services.
It follows Clean Architecture with Domain‑Driven Design, organised into domain (interfaces, services), application (use cases), infrastructure (clients/adapters), and user interface (CLI commands) layers.
Adapters decouple the domain from external APIs, translate data formats, and implement the Ports & Adapters pattern. They also maintain backward compatibility while the internal implementation evolves.
The project uses @ sdk‑mcp (the official MCP Node.js SDK), interacts with Arcee AI and TESS REST APIs, and runs as a Python CLI (commands invoked via `arcee`). Specific runtime versions are not listed in the README.

Verified distributed compute for humans, applications, and agents. Submit Blender, Octane, and video workloads, route them across qualified GPUs, track asynchronous execution, download finished artifacts, and verify FARP
CronWatch records every run of your scheduled jobs in your own database, and speaks up when one is missed, fails, gets stuck, runs slow or costs too much. CronWatch is free and open-source.
Query your team's drift, vulnerability, and migration data from any AI assistant. Vibgrate MCP connects Cursor, Claude, ChatGPT, Windsurf, or VS Code to Vibgrate Cloud: 51 tools for DriftScores, CVEs and EOL runtimes, up

directree MCP server — query the honest software directory from any AI assistant

Official Porkbun MCP server, maintained by Porkbun. Check domain availability and pricing, register, renew and transfer domains, and manage DNS records, nameservers, URL forwarding, glue records, DNSSEC and domain contac
Comments