# Toolcape + Cloud Services

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.

## The connection
Cloud Services: Controls which Google APIs are enabled in a cloud project.
API connection · AI uses Toolcape through MCP
Provider sign-in (OAuth). Confirm whether the configured connection acts as the user or uses application permissions.

## Typical actions
- Read: List enabled APIs
- Change: Enable or disable an API
Disabling an API can interrupt applications. Reserve changes for the responsible IT team.

## Setup
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.

## Permissions
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.

## Calling an operation
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.

## Operation reference
Catalog snapshot: 16 September 2026. Verify the current schema before calling.
- serviceusageServicesEnable — Services Enable
  POST https://serviceusage.googleapis.com/v1/{+name}:enable
  https://cloud.google.com/service-usage/
- serviceusageServicesDisable — Services Disable
  POST https://serviceusage.googleapis.com/v1/{+name}:disable
  https://cloud.google.com/service-usage/
- serviceusageServicesBatchGet — Batch Services Get
  GET https://serviceusage.googleapis.com/v1/{+parent}/services:batchGet
  https://cloud.google.com/service-usage/
- serviceusageServicesGet — Get Services
  GET https://serviceusage.googleapis.com/v1/{+name}
  https://cloud.google.com/service-usage/
- serviceusageServicesBatchEnable — Batch Services Enable
  POST https://serviceusage.googleapis.com/v1/{+parent}/services:batchEnable
  https://cloud.google.com/service-usage/
- serviceusageServicesList — List Services
  GET https://serviceusage.googleapis.com/v1/{+parent}/services
  https://cloud.google.com/service-usage/
- serviceusageOperationsCancel — Operations Cancel
  POST https://serviceusage.googleapis.com/v1/{+name}:cancel
  https://cloud.google.com/service-usage/
- serviceusageOperationsGet — Get Operations
  GET https://serviceusage.googleapis.com/v1/{+name}
  https://cloud.google.com/service-usage/
- serviceusageOperationsDelete — Delete Operations
  DELETE https://serviceusage.googleapis.com/v1/{+name}
  https://cloud.google.com/service-usage/
- serviceusageOperationsList — List Operations
  GET https://serviceusage.googleapis.com/v1/operations
  https://cloud.google.com/service-usage/

## A useful first question
Which APIs are enabled for this project?

## If it fails
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.