Google Cloud Service Usage for AI agents.
Google Cloud Service Usage integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves Google Cloud Service Usage tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.
# Add your Open Connector MCP server (per-user mcp_url)
$ claude mcp add --transport http \
open-connector <your mcp_url>
# Then ask: “open an issue for the launch checklist”// .cursor/mcp.json
{
"mcpServers": {
"open-connector": { "url": "<your mcp_url>" }
}
}const composio = new Composio({
apiKey: "oc_…",
baseURL: "https://connect.acme.com", // your host
});
await composio.tools.proxy({ … });{
"tool": "GOOGLE_CLOUD_SERVICE_USAGE_SERVICEUSAGE_OPERATIONS_LIST",
"arguments": { … }
}Real Google Cloud Service Usage actions, managed and audited.
Your user connects Google Cloud Service Usage once; your agent can then list services and operations for a project, and get details for one or several services — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.
- 01Connect
Your user grants Google Cloud Service Usage access once (OAuth) — the token lands in the vault.
- 02Call
Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.
- 03Audit
Every routed call appends a hash-chained audit record — nothing leaves your infra.
Supported Google Cloud Service Usage tools.
Browse 4 tools in the Google Cloud Service Usage catalog. Each action uses your configured authentication and tool allowlist.
Showing 4 tools.
- Serviceusage Operations List
- GOOGLE_CLOUD_SERVICE_USAGE_SERVICEUSAGE_OPERATIONS_LIST
- Lists operations that match the specified filter in the request. If the server doesn't support this method, it returns `UNIMPLEMENTED`.
- operations
- Serviceusage Services BatchGet
- GOOGLE_CLOUD_SERVICE_USAGE_SERVICEUSAGE_SERVICES_BATCH_GET
- Returns the service configurations and enabled states for a given list of services.
- services
- Serviceusage Services Get
- GOOGLE_CLOUD_SERVICE_USAGE_SERVICEUSAGE_SERVICES_GET
- Returns the service configuration and enabled state for a given service.
- services
- Serviceusage Services List
- GOOGLE_CLOUD_SERVICE_USAGE_SERVICEUSAGE_SERVICES_LIST
- List all services available to the specified project, and the current state of those services with respect to the project. The list includes all public services, all services for which the calling user has the `servicemanagement.services.bind` permission, and all services that have already been enabled on the project. The list can be filtered to only include services in a specific state, for example to only include services enabled on the project. WARNING: If you need to query enabled services frequently or across an organization, you should use [Cloud Asset Inventory API](https://cloud.google.com/asset-inventory/docs/apis), which provides higher throughput and richer filtering capability.
- services
Google Cloud Service Usage integration, answered
- How do AI agents use Google Cloud Service Usage through Open Connector?
- Your user connects Google Cloud Service Usage once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Google Cloud Service Usage tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
- Is this a Google Cloud Service Usage MCP server?
- Yes. Open Connector can serve Google Cloud Service Usage as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Google Cloud Service Usage actions with credentials injected server-side.
- Where do Google Cloud Service Usage credentials live?
- In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.
Give your agents Google Cloud Service Usage — keep the keys.
Open source, self-hostable, with Google Cloud Service Usage credentials that never leave your infrastructure. Run it from source today.