Toolcape connects a company’s existing AI to its systems through one MCP entry point, with account connections, group and individual permissions, and audit logs. This documentation describes a product prototype; it is not evidence that a live server or account is connected.
Google Docs: Google’s text documents, such as proposals, minutes and project plans.
API connection · AI uses Toolcape through MCP
Provider sign-in (OAuth). Confirm whether the configured connection acts as the user or uses application permissions.
- Read: Read the contents of a document
- Create: Create a new text document
- Change: Edit document text and formatting
Drive finds and organizes the file. Docs reads and edits the document structure. They are separate services.
1. IT configures the provider app, API and requested scopes.
2. Provider sign-in (OAuth). Confirm whether the configured connection acts as the user or uses application permissions.
3. Make the service available in Toolcape. Set Everyone, group and individual rules for the actions actually needed. Adding a service does not grant access.
4. Connect the approved AI client to the actual Toolcape MCP address and sign in. Start with a harmless read-only task and check the audit log.
For personal delegated access, the provider account, approved app scopes and Toolcape rules must all permit the action. Shared accounts and application permissions may have other limits. Toolcape combines Everyone and group grants; a personal exception replaces inherited access for that service. Reading can disclose confidential information. Sharing, sending and deletion need separate consideration.
First discover which tools the connected Toolcape server actually exposes. If it offers search → describe → execute, find the relevant operation, inspect its input schema and permissions, then call it with validated inputs. Tool names vary by server; do not invent names, arguments, URLs or successful outcomes. Without connected tools, give setup guidance instead of claiming to perform actions.
Catalog snapshot: 16 September 2026. Verify the current schema before calling.
- docsDocumentsGet — Get Documents
GET https://docs.googleapis.com/v1/documents/{documentId}
https://developers.google.com/workspace/docs/
- docsDocumentsBatchUpdate — Batch Documents Update
POST https://docs.googleapis.com/v1/documents/{documentId}:batchUpdate
https://developers.google.com/workspace/docs/
- docsDocumentsCreate — Create Documents
POST https://docs.googleapis.com/v1/documents
https://developers.google.com/workspace/docs/
Read the meeting minutes and list the decisions.
Check the account, expired authorization, app approval, provider scopes and Toolcape permissions. Share only redacted errors with support. Never paste passwords, tokens or client secrets into an AI conversation.