@botuyo/mcp
v0.7.0
Published
BotUyo MCP Server — create and manage AI agents via Model Context Protocol
Maintainers
Readme
@botuyo/mcp — BotUyo MCP Server
Create and manage BotUyo AI agents directly from your AI coding tools — no cloning, no building.
Quickstart
The fastest way — one command configures your editor and logs you in:
npx @botuyo/mcp setupIt auto-detects your editor (Cursor, VS Code / Antigravity, Claude Desktop), writes the MCP config, and walks you through authentication.
Manual setup
1. Add the BotUyo server to your MCP client config:
{
"mcpServers": {
"botuyo": {
"command": "npx",
"args": ["-y", "@botuyo/mcp"]
}
}
}No API key goes in the config — authentication is handled by the
auth/logincommands below. Some clients (Cursor, VS Code) use theserverskey instead ofmcpServers.
| Client | Config file |
|---|---|
| Cursor | .cursor/mcp.json |
| VS Code / Antigravity | .vscode/mcp.json |
| Claude Desktop | ~/.config/claude/claude_desktop_config.json (Windows: %AppData%\Claude\claude_desktop_config.json) |
| Windsurf | ~/.codeium/windsurf/mcp_config.json |
2. Authenticate once — saves a token to ~/.botuyo/credentials.json:
npx @botuyo/mcp auth # browser OAuth (recommended)
# or
npx @botuyo/mcp login # email + password in the terminalThe running MCP server picks up your session automatically — no restart needed. Tokens last 7 days; re-run auth or login to refresh.
Start building agents
Once connected, ask your AI assistant things like:
"Create a new agent called 'Soporte' for my tenant" "Update Mar's objective to focus on sales" "Add a welcomeStage that greets guests in Spanish" "Enable the EscalateToHuman and SearchKnowledgeBase tools on Mar" "Publish the agent"
CLI commands
npx @botuyo/mcp setup # Configure your editor + authenticate (recommended)
npx @botuyo/mcp auth # Login via browser (OAuth)
npx @botuyo/mcp login # Login via email + password
npx @botuyo/mcp tenants # List your tenants
npx @botuyo/mcp switch-tenant # Switch the active tenant
npx @botuyo/mcp whoami # Show the current session
npx @botuyo/mcp logout # Clear stored credentialsThe server resolves your JWT from BOTUYO_TOKEN, falling back to ~/.botuyo/credentials.json. The backend URL defaults to https://api.botuyo.com (override with BOTUYO_API_URL).
Available tools
The server exposes 41 tools. Read tools (list_*, get_*, export_*) need viewer+; write/publish tools need developer+ (see Roles).
Agents
| Tool | Description |
|---|---|
| list_agents | List all agents in the tenant |
| get_agent | Get an agent's full config (identity, stages, enabled tools) |
| get_agent_status | Channel connection status + admin link to connect missing channels |
| create_agent | Create a new agent |
| update_agent | Update identity (tone, language, objective, custom instructions) |
| delete_agent | Soft-delete an agent (irreversible; requires explicit confirmation) |
| publish_agent | Publish or unpublish an agent (live vs draft) |
| example_agent | Return a fully documented example agent config (read-only reference) |
Agent families
A family is one logical agent with a shared base config plus multiple variants (each variant stores only its overrides and is materialized into a real agent) — ideal for a single assistant offered in several levels or flavors.
| Tool | Description |
|---|---|
| list_agent_families | List agent families in the tenant |
| get_agent_family | Get a family's shared base + all its variants |
| create_agent_family | Create a family with a shared base and an initial set of variants |
| update_family_base | Replace the shared base (re-materializes every variant) |
| add_family_variant | Add a new variant (materialized into a draft agent) |
| update_family_variant | Update a variant's label / overrides / handoff targets / order |
| remove_family_variant | Remove a variant (cannot remove the entry variant) |
| publish_agent_family | Publish the family and all its member agents |
| delete_agent_family | Delete a family and all its agents (irreversible; requires confirmation) |
| export_agent_family | Export a portable family JSON (base + variants) to a local file |
| import_agent_family | Replace a family's base + variants from JSON (full replace) |
Conversation flow
| Tool | Description |
|---|---|
| upsert_stage | Create or update a named stage in the agent's conversation graph |
Tools & capabilities
| Tool | Description |
|---|---|
| list_available_tools | List tools available to your tenant (core + custom) |
| update_enabled_tools | Enable/disable tools on an agent |
| get_tools_catalog | Full tool catalog with metadata (configurable, multi-instance, schema, required integrations) |
| configure_agent_tool | Create/update a tool's config on an agent (single or multi-instance) |
| list_tool_configs | List an agent's tool configs, grouped |
| get_tool_config | View the full config of a specific tool on an agent |
| remove_tool_config | Remove a tool's configuration |
Knowledge base
| Tool | Description |
|---|---|
| list_knowledge_documents | List knowledge base documents |
| ingest_knowledge_url | Ingest a URL into the knowledge base |
| associate_knowledge_to_agent | Link knowledge document IDs to an agent |
| delete_knowledge_document | Delete a knowledge document and all its chunks |
Templates
| Tool | Description |
|---|---|
| list_templates | List agent templates by industry |
| create_from_template | Create a new agent from a template |
Import / export
| Tool | Description |
|---|---|
| export_agent_json | Export an agent's full config as editable JSON |
| import_agent_json | Replace an agent's full config from JSON (full overwrite) |
Avatar & media
| Tool | Description |
|---|---|
| list_avatars | List the free 3D avatars in the catalog |
| select_avatar | Set a 3D avatar for an agent (catalog ID or custom .glb/.vrm URL) |
| upload_agent_media | Upload a local image to the CDN as an agent's avatar/logo |
Versioning
| Tool | Description |
|---|---|
| list_agent_versions | List an agent's saved version snapshots |
| restore_agent_version | Roll back an agent to a previous version |
Account
| Tool | Description |
|---|---|
| switch_tenant | Switch the active tenant for the session |
Roles
| Role | Read | Write | Publish |
|---|---|---|---|
| owner | ✅ | ✅ | ✅ |
| admin | ✅ | ✅ | ✅ |
| developer | ✅ | ✅ | ✅ |
| viewer | ✅ | ❌ | ❌ |
Channel Integrations
Connecting channels (WhatsApp, Instagram, Telegram, Web) must be done from admin.botuyo.com — they require interactive flows (QR scans, OAuth, etc.).
Use get_agent_status to check which channels are connected. It returns a direct link to the admin panel for any missing channel.
Build from source
git clone https://github.com/MarcoAR1/botuyo-mcp.git
cd botuyo-mcp
npm install
npm run buildTest with MCP Inspector
Authenticate first (npx @botuyo/mcp login), then run:
npm run inspectContributing
We welcome contributions! See CONTRIBUTING.md for guidelines.
Please note that this project follows a Code of Conduct.
Security
To report a vulnerability, see SECURITY.md.
License
MIT © BotUyo
