Select and inspect
Choose a Docs, Slides, or Sheets template with Google Picker, then read summary or structural details before planning changes.
“Use these meeting notes to prepare a proposal in my Google template, then publish it after review.” Templify MCP gives compatible AI agents the Google file, publishing, and engagement operations needed to complete that workflow.
Optional integration. The Google Workspace add-on works without MCP.
Your agent host supplies the AI and any transcription. Templify performs explicit Google file, proposal publishing, and engagement-signal operations.
Source notesPaste meeting notes or provide source material to your agent.
Editable Google proposalThe agent copies or uploads a template and prepares a reviewable Google file.
Published proposalAfter review, publish a separate webpage with a PDF download.
Engagement signalsReview views, estimated active time, device, browser, and referrer data.
Paste this into Claude Code, Codex, or another compatible agent. It will detect the correct plugin and MCP workflow, preserve existing configuration, and stop when browser approval is required.
Set up Templify in this agent. Do what you can and guide me through anything that needs my input. 1. Identify this agent and version, then inspect existing plugins, MCP servers, and skills. Preserve existing configuration and avoid duplicates. 2. Install the Templify plugin using this agent's supported plugin or skill workflow from https://github.com/Doc-Failure/templify-agent-plugin. Check the installed client's help or current documentation before running commands. 3. Confirm that the plugin includes both Templify skills and its hosted MCP configuration. Do not copy credentials into chat, shell history, or repository files. 4. Reload or restart the agent only if required. On the first Google-dependent action, let me approve the Templify OAuth flow in my browser. 5. Verify that the Templify MCP tools and skills are discoverable, but do not create, upload, edit, deploy, or purchase anything during setup. When setup is complete, briefly report what succeeded and any action I must take. Then suggest a safe first test and ask for confirmation before using Google Drive.
The repository already includes this configuration. Compatible MCP clients can use the same endpoint directly.
{
"mcpServers": {
"templify": {
"type": "http",
"url": "https://api-3cfmtpoddq-uc.a.run.app/mcp"
}
}
}
The first Google-dependent tool opens a browser authorization flow using the drive.file scope. Templify acts only on files the connected account can access. Access can be revoked from Google Account permissions.
Each operation is exposed as an explicit MCP tool, so the agent can inspect before editing and keep the source file untouched.
Choose a Docs, Slides, or Sheets template with Google Picker, then read summary or structural details before planning changes.
Create a fresh editable Drive copy. The original source template is never modified by the proposal workflow.
Use Google batchUpdate operations to personalize Docs, Slides, or Sheets with agent-generated content.
Convert a local DOCX, PPTX, or XLSX into the corresponding editable Google file for continued work.
Publish a separately tracked proposal in scroll or book mode and return its public URL, PDF URL, expiry, and deployment ID.
On Pro, inspect views, unique visitors, views by day, time by page, devices, browsers, and top referrers.
Use the included skill and MCP together. Audio transcription, when available, is performed by your agent host — never by Templify.
Paste a transcript or attach a recording your agent host can transcribe. Templify never receives or transcribes the audio.
Supply an accessible file URL or use Google Picker. The agent inspects it, copies it, and edits only the copy.
Keep the editable Google file, then publish a separate web/PDF version when requested and inspect engagement later.
One Pro subscription covers the Workspace add-on and MCP when both use the same Google account. Free monthly actions and the 50-active-proposal cap are shared across both interfaces.
Shared across the add-on and MCP
One subscription for add-on and MCP
Selects the model, understands source material, transcribes audio when supported, writes proposal content, and decides which explicit tool call is required.
Selects, inspects, copies, uploads, and edits Google files; deploys separate web/PDF versions; enforces quota and expiry; and returns analytics.
No. Claude Code, Codex, or another compatible host supplies the model and reasoning. Templify exposes deterministic Google file, deployment, billing, and analytics operations.
No. Recordings stay with the host application. If the host cannot transcribe audio, the proposal skill asks for a transcript instead.
The proposal-from-conversation workflow inspects the source and creates a Drive copy before applying edits. The original template remains unchanged.
No. Each deployment is a separate public, tracked web/PDF version. The editable Google file remains in Drive.
Yes. Connect both interfaces with the same Google account. The plan, monthly usage, and limit of 50 active published proposals are shared.
They show page loads, estimated unique visitors, estimated active time, devices, browsers, and referrers. They do not verify recipient identity, prove reading or buying intent, or track reading after a PDF is downloaded.
Ask the connected agent to upgrade or manage the subscription. Templify returns a secure Stripe Checkout or customer portal link. Billing changes still require completion in the browser.
Install the plugin to get the MCP configuration and both Templify skills in one repository.