Any MCP client, one server URL.
Triplewave runs a remote MCP server at one URL. Clients that support OAuth sign in and ask for permissions. The rest use a workspace token that an admin creates.
Connect your client.
Any client that can reach a remote MCP server over Streamable HTTP can connect. There’s nothing to install: Triplewave has no local server and doesn’t use the older SSE transport.
Server URL
https://triplewave.co/api/mcpYour workspace’s Connectors page shows the same URL.
With OAuth sign-in
Most current clients work this way, Claude and ChatGPT included.
- 1
Add a remote server with the URL above. If the client asks for a transport, choose HTTP.
- 2
Connect. The client finds Triplewave’s sign-in through OAuth discovery and opens it in your browser.
- 3
Sign in, pick one workspace and choose permissions. The client’s tokens work for that workspace only.
With a workspace token
For clients that can’t complete OAuth. Only workspace owners and admins can create one.
- 1
In Triplewave, open Connectors, Advanced: manual access token.
- 2
Choose the permissions, then Create token. Copy it straight away: it starts with
twc_and appears once. - 3
Send it with every request as
Authorization: Bearer twc_…. It lasts 30 days.
The tools, by permission.
A connection sees only the tools its permissions allow. Clients read this list from the server, so nobody types these names by hand.
| Tool | Permission |
|---|---|
| Reading | |
Find documents by title or textsearch_documents | Documents |
Open a document with its facts and designget_document | Documents |
Browse templates, as a gallery where the app can show onelist_templates | Documents |
Get a preview link for the latest versionrender_document_preview | Documents |
Read colors, fonts, letterhead and voiceget_brand_kit | Brand kit |
Read addresses, tax and bank detailsget_company_info | Company info |
Read notes you approved for connected appsget_memory | Connector memory |
| Editing | |
Start a document from a template or a briefcreate_document | Document editing |
Rewrite the body of a draftreplace_document_blocks | Document editing |
Add or change parties, dates, amounts and other factsupdate_document_facts | Document editing |
Change the page, type, header, footer or colorsupdate_document_design | Document editing and Brand kit |
Sign-in and permissions
Triplewave publishes standard OAuth discovery, so a client finds the sign-in on its own. The person connecting picks one workspace and approves each permission. Access tokens last 15 minutes and work only for Triplewave. Every call checks the connection, the person’s membership, expiry and revocation.
- 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.
What stays in the editor
PDF export, signer setup and signature emails aren’t offered as tools. Results that touch a document link to it in the Triplewave editor, where you finish.
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
- Model Context Protocol documentation (opens in a new tab) · Model Context Protocol
- MCP authorization specification (opens in a new tab) · Model Context Protocol
- MCP TypeScript server guide (opens in a new tab) · Model Context Protocol