Skip to main content
Triplewave
Get started
Integrations

The Triplewave MCP connector.

Triplewave runs a remote MCP server over Streamable HTTP. Any compatible client can connect with OAuth or a workspace token, and it only sees the tools you approved.

SecurityCreate a workspace

Tools

Tools are grouped by what they touch: documents, brand, company and memory. The server registers only the tools the current connection may use.

  • Read: search and read documents, list templates, read company info, the brand kit and approved memory.
  • Write: create a document, replace validated blocks, update facts and design, and return preview links.
  • Not offered: PDF export, signer setup and email. Use the link back to the editor.

Sign-in and permissions

Triplewave publishes OAuth discovery, then asks the person connecting to choose a workspace and approve each permission. Access tokens are short-lived and issued for Triplewave only. Every call checks the connection, membership, expiry, revocation and workspace state. Admins can also create a workspace token for clients that can’t use OAuth.

  • A workspace token appears once. Store it like a password.
  • Revoke a connection anytime. Removing a member removes their access too.
  • Each connection is rate-limited, logged and protected against duplicate writes.

Document text can’t grant access

Triplewave treats document text as data. Nothing written in a document can widen a connection’s permissions or turn a preview into a sent email.

Limits

  • The connector isn’t a public API, and its tools can change.
  • Appearing in a chat app’s directory is separate from the connector working.

Sources

Keep reading.