Summary
gws auth login does not offer OAuth scopes for the People API (contacts.readonly) or Meet REST API (meetings.space.created) in its interactive scope selector, even though gws supports both people and meet as services with full API discovery.
Steps to reproduce
- Run
gws auth login
- Observe the interactive scope selector — only 9 scopes offered:
- Drive, Sheets, Gmail, Calendar, Docs, Slides, Tasks, Pub/Sub, Cloud Platform
- Run
gws schema people.people.searchContacts — shows it requires contacts or contacts.readonly scope
- Run
gws schema meet.spaces.create — shows it requires meetings.space.created scope
- Try to call
gws people people searchContacts ... — fails with "insufficient authentication scopes"
- Try to call
gws meet spaces create — fails with "insufficient authentication scopes"
Expected behavior
The auth login scope selector should include all scopes needed by the services gws supports, including:
https://www.googleapis.com/auth/contacts.readonly (or contacts) for the People API
https://www.googleapis.com/auth/meetings.space.created for the Meet API
Workaround attempted
Manually editing the OAuth authorization URL to include the missing scopes before submitting — Google's consent screen shows the additional permissions, but gws's local callback server does not capture them in the resulting credential.
Environment
Context
We're building an MCP server on top of gws (google-workspace-mcp) and discovered this while expanding coverage to all gws-supported services. The factory architecture generates tools from gws's own API discovery, so it's natural to expect auth to cover the same services.
Summary
gws auth logindoes not offer OAuth scopes for the People API (contacts.readonly) or Meet REST API (meetings.space.created) in its interactive scope selector, even though gws supports bothpeopleandmeetas services with full API discovery.Steps to reproduce
gws auth logingws schema people.people.searchContacts— shows it requirescontactsorcontacts.readonlyscopegws schema meet.spaces.create— shows it requiresmeetings.space.createdscopegws people people searchContacts ...— fails with "insufficient authentication scopes"gws meet spaces create— fails with "insufficient authentication scopes"Expected behavior
The auth login scope selector should include all scopes needed by the services gws supports, including:
https://www.googleapis.com/auth/contacts.readonly(orcontacts) for the People APIhttps://www.googleapis.com/auth/meetings.space.createdfor the Meet APIWorkaround attempted
Manually editing the OAuth authorization URL to include the missing scopes before submitting — Google's consent screen shows the additional permissions, but gws's local callback server does not capture them in the resulting credential.
Environment
Context
We're building an MCP server on top of gws (google-workspace-mcp) and discovered this while expanding coverage to all gws-supported services. The factory architecture generates tools from gws's own API discovery, so it's natural to expect auth to cover the same services.