AttestWork demo tour · Part 1 of 6
The assistant is built in. Your AI connects too.
Every AttestWork engagement ships with a built-in assistant - open the file and it is already there, in context, no setup. Prefer the AI your firm already licenses? AttestWork speaks the Model Context Protocol (MCP): add one connector URL to Google Antigravity, Claude, ChatGPT, or Gemini Spark and it can read and draft inside your engagements. Either way: same tools, same guardrails, same audit log.
Illustrative engagement: Hudson & Vale CPAs, LLP (Albany, NY) auditing Riverbend Community Services, Inc. (Rochester, NY) - a NYS-funded nonprofit, GAAS audit, FYE December 31, 2025, with a NYS CFRDec25 Examination add-on. Fictional firm, client, and data.
AttestWork MCP server URL
https://attestwork.workpaperos.com/api/mcpAdd this URL in your AI product's remote MCP settings and sign in with your WorkpaperOS account. Authorize each AI product separately; its one AttestWork connection covers engagement tools and Files. File execution and network approvals depend on the AI client.
New - built in
The assistant is already inside the engagement
Before you connect anything, meet the AttestWork Assistant. It lives in every engagement as a chat panel - multiple chats with history, like the assistant your team already knows, standing inside the file. It detects where you are: open procedure P1 on Planning and it already has that section's procedures, what's documented in other areas, the risk assessment, and the engagement's indexed files. No connector, no setup.
Approval needed - sign-off
Mark P1 - Understanding the entity as Prepared (d.okafor).
The bot does the heavy lifting
- Knows where you are: the open procedure, that section's program, what's documented in other areas, the risk assessment, and the engagement's indexed files.
- Talks the approach through when you want to discuss - or writes straight into the procedure when you ask. Results land as tables first, drawn from the WPOS Template Library; when no template fits, it builds a clean table itself.
- Searches the engagement's indexed files, or works from the files you attach to a message. On WPOS Esign, it can study a signed engagement letter, file the PDF into the right engagement, or create a new engagement from the letter's own terms.
- Lets you pick the model - Gemini, Claude, GPT, or an open model - with live weekly and 5-hour usage meters in the panel. Every plan can use every model.
You stay in control
- Drafts stay drafts, and an edit to a signed-off procedure reopens it for review - exactly the rails the MCP connector runs on.
- Sign-offs, deletions, file moves, and creating an engagement always stop at an in-chat approval card. Nothing irreversible happens without a click from a person.
- Chats are yours: switch between them, delete them, start new ones - like the chat apps your team already knows.
AI is included with any app subscription. AI Core is $39/month (400 credits a week) and AI Advanced is $129/month (1,400 a week); pay-as-you-go is $10 for 250 credits, valid 12 months. Credits weight by model class - open 0.5, fast 1, standard 3, max 8 per message - and when a limit gets near, requests fall back to the fast default instead of stopping.
Five minutes, one URL
Add the connector where your AI lives
In your assistant's connector settings, paste the AttestWork MCP URL. The assistant discovers the OAuth configuration on its own - no keys to copy, no agents to install.
AttestWork MCP server URL
https://attestwork.workpaperos.com/api/mcpCopy this into Settings → Connectors in your assistant. It's live - you can test it with your own WorkpaperOS account today.
The bot does the heavy lifting
- Discovers the connector's OAuth setup automatically (OAuth 2.1 with PKCE, dynamic client registration).
- Sees the full attest toolset after authorization: engagements, procedures, files, PBC, workbooks, reports.
- Works from Google Antigravity, Claude, ChatGPT, or Gemini Spark - whichever your firm subscribes to, on your AI account.
You stay in control
- You sign in with your WorkpaperOS account - the assistant never sees your password.
- You choose which companies the connector may touch, per authorization.
- You can disconnect at any time from your assistant's settings, and revoke access from WorkpaperOS Settings.
Authorize antigravity-client
antigravity-client is requesting access to your WorkpaperOS Audit companies as d.okafor@hudsonvalecpas.com.
Companies to authorize
Hudson & Vale CPAs ✓
US · admin
Sample workspace
US · admin
Requested permissions
workpaperos:read
Read engagements, risk assessments, workpapers, and PBC requests.
workpaperos:write
Create and update audit documentation on your behalf.
Every authorized tool call is recorded. You can revoke this access at any time from Settings.
One connected workflow
Built in, connected, and working with original files
Use the built-in assistant or your own connected AI. File exchange is part of the existing MCP connection, not another storage account.
No setup
AttestWork Assistant
Built into every engagement, already in context. Works with nothing else connected - no connector, no cloud storage.
Any AI
MCP connector
Antigravity, Claude, ChatGPT, or Gemini Spark calling live tools on your engagement, plus the text of every indexed file - OCR'd scans included. Every call lands in the audit log.
Same connection
AttestWork Files
Download original PDFs, workbooks, Word documents, and images into a permitted analysis environment, then return generated files through signed HTTPS transfers. No folder mirror or extra Files connector.
Indexed search helps the AI locate evidence. When analysis needs the original, the same connection authorizes a direct file transfer - see the Files workflow. Your AI product's file and network permissions still apply.
AttestWork Files
Original files to your AI. Finished work back to your file room.
Connect AttestWork once in each AI product and authorize the companies it may access. The same MCP connection covers records, indexed document search, and file exchange: no second Files connector or desktop folder mirror. Your assistant can request the original Excel, PDF, Word, or image file, analyze it in a supported execution environment, and upload a generated file to the authorized engagement.
Works with ChatGPT, Claude, and Google Antigravity
The original-file download, analysis, and return-upload workflow has been successfully validated with all three. Claude and Google Antigravity have completed manual validation alongside ChatGPT. Use your existing product connection; no second Files connector is needed.
1 · Authorize
Sign in with your WorkpaperOS account through the product's MCP connector. Access remains company-scoped and revocable.
2 · Analyze originals
MCP obtains a short-lived download link. Original bytes travel over HTTPS outside the conversation's tool payload, with file identity and integrity information.
3 · Return the work
The assistant reserves an upload, transfers the file over HTTPS, and completes validation. Supported large-file uploads can resume; finalized files enter the app's indexing pipeline.
| Your AI | How file exchange runs |
|---|---|
| Gemini Spark | Connect through Custom apps for Spark using the same product MCP URL. Indexed data and tools are available through the authorized connection; original-file download, analysis, and return upload depend on Spark's available file-execution and HTTPS capabilities. |
| ChatGPT | Uses the supported attachment handoff or an authorized HTTPS transfer in its file-analysis environment. File access may require approval in the current chat. |
| Claude | Uses the shared transfer tools. Claude Code can transfer files from its permitted workspace; Claude web/Desktop chat requires an available file-execution environment and approved network access. |
| Google Antigravity | Uses the same remote MCP connection and HTTPS transfers from its permitted agent workspace. Terminal, file, and network permissions still apply. |
Connect Gemini Spark
Use Gemini Spark with AttestWork through the same MCP connection approach as ChatGPT and Claude. Ask for work on your authorized engagement; review the results and approve writes when prompted.
- In Gemini web, open Settings & help → Connected Apps → Custom apps for Spark → Add a custom app.
- Paste
, then follow the sign-in and authorization prompts for your WorkpaperOS account. - In Spark, type @ and select your connected app, then describe the task, company, and period.
Google currently requires Spark access, a personal Google Account, age 18+, US availability, English, and Keep Activity enabled. Check your firm's confidentiality policy and Google's data settings before connecting client information. Custom apps are for Spark, not ordinary Gemini chat. Original-file analysis and return uploads depend on Spark's available file and network capabilities.
Google's current Spark setup and eligibility requirementsProjects
Make each engagement a Project
Use a supported project or workspace in your chosen AI product for each engagement. Add the firm's templates, methodology, and appropriate prior-year workpapers to guide documentation. Uploaded project knowledge is a snapshot; use AttestWork Files through the connector to obtain current original documents and return completed work to the engagement.
| Project knowledge | What the AI does with it |
|---|---|
| 📄 H&V workpaper templates (.xlsx set) | studied - drafts match your formats |
| 📄 Riverbend FY2024 signed file (prior year) | studied - knows last year's approach |
| 📄 Firm methodology & tickmark legend | studied - uses your tickmarks |
| 📁 Engagement folder snapshot - PBC deliverables, prior workpapers | uploaded copies - refresh them when they change |
Connector: WorkpaperOS AttestWork (MCP). Project materials give the assistant context; request current file revisions through AttestWork Files before relying on an uploaded snapshot.
The bot does the heavy lifting
- Studies your in-house templates and prior-year workpapers, then drafts in your firm's style - not a generic one.
- Keeps the whole engagement in context: no re-explaining the client at the top of every chat.
- Requests original files through AttestWork Files and returns generated work through the same scoped connection, where the AI environment permits file execution and HTTPS access.
You stay in control
- Your templates, your prior files, your documentation style - the AI adapts to the firm, never the other way around.
- Projects live in the assistant your firm already licenses - no new tool to buy or learn.
- Remove a file from the project and it leaves the AI's context - you control exactly what it learns from.
First conversation
Then just talk to your files
Once connected, your engagement files are something your assistant can read and write - in the same chat where your team already works.
Updated walkthrough: connect your AI and exchange original files
Updated video walkthrough coming soon - follow the illustrated workflow above.
Screens on this page are illustrative: Hudson & Vale CPAs and Riverbend Community Services, Inc. are fictional.