Reference
What is available?
Understand enabled features, connection-dependent actions and rollout limits.
Standard team agent work
The standard team MCP connection supports your own campaign work through six read and draft tools: get_workspace, list_campaigns, get_campaign, list_campaign_prospects, create_campaign_draft and import_campaign_prospects. The exact tool list in your client and your granted scopes determine availability.
These tools do not approve or send outreach. If your workspace has not enabled a mode or provider, the app should show that state rather than a connected badge. Optional personal integrations can expose a different tool set; they do not turn into shared access to someone else’s private records.
Channel capabilities vary
Gmail and Google Calendar are the first rollout. LinkedIn’s sending adapter remains off. A provider connection can support identity, inbox reads or selected actions without supporting every possible operation. Treat each action’s displayed capability as separate from the provider’s sign-in state.
No campaign sending service is registered, and campaign reply ingestion is not yet built. Firm-wide sending stays off until real reply reading and required stop controls are proven. The intended enabled workflow is automatic by default under configured hard guardrails; a refusal always wins. A Connect button does not establish delivery or reply synchronization.
Use the app’s live status
This documentation describes the intended team workflow and its controls. The deployed app’s status, permission checks and available tools determine what you can use now.
Single sign-on remains marked coming soon. Client plans, installed versions and workspace policies may also restrict custom connectors. If something is unavailable, use the troubleshooting guide or ask your administrator.