mcpField
A
Armavita Quo Mcp

Armavita Quo Mcp

Local
github.com/EfrainTorresCommunication2Updated 35w ago

About Armavita Quo Mcp

Armavita Quo Mcp is a local-first MCP server for Quo API workflows, aimed at users automating communications through stdio. It provides tools for messages, calls, contacts, users, phone numbers, and webhooks.

Key features

  1. 01Send and retrieve messages
  2. 02Manage contacts
  3. 03Query calls and voicemail
  4. 04Look up numbers and users
  5. 05List webhooks
  6. 06Paginated queries

Use cases

  1. 01Send or retrieve Quo messages
  2. 02Create and update contact records
  3. 03Retrieve call recordings or transcripts
  4. 04Read large result sets using pagination

MCP support

The server exposes Quo API tools to MCP clients over local stdio. It uses QUO_API_KEY for API calls.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

armavita-quo-mcp

ArmaVita Quo MCP hero image

Brought to you by ArmaVita.com

Need a custom implementation? Contact us.

armavita-quo-mcp is a local-first MCP server for Quo API workflows (messaging, calls, contacts, users, phone numbers, and webhooks).

  • MCP transport: local stdio
  • Runtime: Node.js 18+
  • Auth: QUO_API_KEY
  • License: AGPL-3.0-only

Install

npm install

Run

bash ./run.sh

run.sh verifies Node/npm, installs dependencies if needed, then starts the MCP server.

Required Environment Variable

  • QUO_API_KEY: Quo API key used for all API calls.

Optional:

  • QUO_HTTP_TIMEOUT_MS: request timeout in milliseconds (default: 30000).

Quick MCP Client Config

Use this pattern in your MCP client config:

{
  "mcpServers": {
    "armavita-quo-mcp": {
      "command": "bash",
      "args": ["/absolute/path/to/armavita-quo-mcp/run.sh"],
      "env": {
        "QUO_API_KEY": "YOUR_QUO_API_KEY"
      }
    }
  }
}

If your client launches from this folder, you can use:

{
  "mcpServers": {
    "armavita-quo-mcp": {
      "command": "bash",
      "args": ["./run.sh"],
      "env": {
        "QUO_API_KEY": "YOUR_QUO_API_KEY"
      }
    }
  }
}

Tool Coverage

  • Messages: send_text, list_messages, get_message
  • Conversations: list_conversations
  • Contacts: create_contact, list_contacts, get_contact, update_contact, delete_contact, get_contact_custom_fields
  • Calls: list_calls, get_call, get_call_recordings, get_call_summary, get_call_transcription, get_voicemail
  • Phone numbers: list_phone_numbers, get_phone_number
  • Users: list_users, get_user
  • Webhooks: list_webhooks

Pagination

  • List endpoints expose Quo pagination parameters such as maxResults and pageToken.
  • Preserve and pass forward returned page tokens to continue pagination.

Usage Notes

  • Use E.164 format for phone numbers where required (for example +18325551234).
  • update_contact requires at least one field to update.
  • API failures are returned from Quo status and response details, with secrets redacted in server error paths.

Security

  • Never commit real QUO_API_KEY values.
  • Keep credentials in client/server env config, not in source files.
  • Use separate keys for dev/staging/prod.

Docs

Scope

  • This repository is an OSS local MCP server.
  • Transport mode is local stdio only.
  • Tool aliases are intentionally not exposed.

Development

Syntax check:

npm run check

Start directly:

npm start

License

GNU Affero General Public License v3.0 (AGPLv3). See LICENSE.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.