🔌 MCPs

MCP means Model Context ProtocolIt’s a standard that packages a tool in a way the model understands — including what actions are available, what each one does, and how to call them. Instead of Hermes guessing how to use the tool, it gets the ready-made "manual."

The best analogy: the API is exposed wiring — it works, but you need to know exactly where each wire goes. The MCP is the manual/instruction package around that wiring: a universal remote control with the buttons already labeled.

The key technical advantage: MCP is much more token-efficientThe model reads the manual once and already knows all the actions (draft an email, create an event, search for a file)—without having to re-explain the tool with every call. Fewer tokens, lower cost, more consistency.

The Granola MCP connects Hermes to your meetings. It plug-and-play: you add the MCP by name and authorize it in the browser via OAuth—no key to store. From then on, asking about meetings "just works".

Zapier MCP is the Swiss Army knife of Swiss Army knives: you starts servers that connect to apps, add whatever tools you want (e.g., "read email"), generates a token and adds it via an environment variable. This opens up thousands of integrations at once.

# gere o token no painel do Zapier, depois NO TERMINAL:
export ZAPIER_MCP_TOKEN="SEU_TOKEN_AQUI"

# NUNCA cole o token no chat — ele é indexado e vai pros backups
# o MCP lê a variável de ambiente

When setting up an email MCP, add tools for read-only ("read email," "draft"), but hold "send/reply to email" until you trust the workflow. People have already been burned by agents sending inappropriate emails. This is the principle of least privilege in practice.