AVELIN-MCP Services Documentation

This section provides complete business-facing documentation for AVELIN-MCP service actions and model-achievable workflows.

AVELIN-MCP is part of the Enterprise Platform pillar and executes actions through Cross-Model MoE intelligence — delivering agentic workflows up to 87% cheaper than premium alternatives by cascading through optimal tiers.

Coverage is based on implemented MCP actions for:

  • Google Calendar
  • Gmail
  • Google Contacts
  • Google Tasks

What You Will Find Here

  • Full per-service action catalogs with exact tool names
  • Business description of what each action does
  • Practical scenarios the model can execute with each service
  • Cross-service automation scenarios combining Calendar, Gmail, Contacts, and Tasks
  • Quick action reference for fast lookup

Documentation Map

Action Coverage Summary

ServiceAction Count
Google Calendar13
Gmail32
Google Contacts9
Google Tasks15
Total69

How to Use This Section

  1. Start with the service page that matches your immediate business workflow.
  2. Use the action descriptions to understand exactly what can be automated.
  3. Use per-service scenarios to design role-specific playbooks.
  4. Use cross-service scenarios to build end-to-end execution flows.

Frequently asked questions

What does AVELIN MCP connect to?

Gmail, Google Calendar, Google Contacts and Google Tasks, through the Model Context Protocol.

How are permissions handled?

Connections are OAuth-secured and limited to the permissions the person grants.

What can an assistant do through MCP?

Read and write in the connected services, from searching mail to creating events and tasks, and combine services in one workflow.

What does an MCP workflow cost?

MCP actions run on the AVELIN models, so the cost of a request depends on how many tool calls it takes. Prices are on the price list.