🇮🇹 IT

AI agent for PEC Aruba

Connect PEC Aruba to your AI agent through the WorkAist MCP server. IT certified email (PEC)

In 60 seconds

The WorkAist PEC Aruba connector is a production-grade Model Context Protocol (MCP) server. AI agents can read and write PEC Aruba data — email, e signature — through one consistent interface. Open-source under AGPL-3.0, self-hosted, with reversible PII redaction at the LLM boundary.

Authentication & setup

The PEC Aruba connector authenticates via HTTP Basic auth.

Username + password / app password

For self-hosted or legacy services. Use an app password when the provider supports them.

Frequently paired with PEC Aruba

FAQ

Can a WorkAist AI agent really automate PEC Aruba end-to-end?

Yes. The connector exposes read and write tools through Model Context Protocol. AI agents call them through plain-language instructions in a CLAUDE.md file — no glue code.

How does this differ from using the PEC Aruba API directly?

The connector adds permission isolation, audit logging, cost tracking per agent, and reversible PII redaction at the LLM boundary. It also presents PEC Aruba as part of a unified Knowledge Graph alongside your other tools.

What does it cost?

WorkAist is open-source under AGPL-3.0 and self-hosted, so the connector itself is free. You pay only for PEC Aruba's own API costs (if any) and the LLM tokens your agent consumes.

Is my PEC Aruba data sent to a third party?

No. WorkAist runs in your own infrastructure. Data flows from PEC Aruba → your WorkAist instance → the LLM you choose. Sensitive fields can be tokenized before reaching the LLM.

What if PEC Aruba changes its API?

The connector is versioned and published openly. When PEC Aruba ships breaking changes, we bump the connector version and the marketplace UI surfaces the upgrade as a one-click apply.

Source code on GitHub · Licensed under AGPL-3.0 · Self-hosted, your data stays yours.