Skip to main content
Plyne MCP uses OAuth access tokens. Start the connection from your assistant, sign in to Plyne, choose a workspace, and review the requested permissions before approving access.

What you authorize

An authorized connection can read Signal Agents, Sheets, Leads, Accounts, and saved signal history in the selected workspace. No additional product-specific scope is required. The tools are read-only. They cannot run or modify Signal Agents, enrich records, edit results, or send outreach. Read access shares the returned workspace data with the assistant you connected. Your connection is bound to the user and workspace selected during authorization. You must remain a member of that workspace. Switching the active workspace in the portal does not change an existing MCP connection; authorize another connection to use a different workspace.

Manage a connection

Use your assistant’s connector settings to manage or remove its Plyne connection. The Plyne MCP settings page provides the server URL and setup instructions; it does not list managed OAuth authorizations. If your assistant reports that access has expired or been revoked, restart its sign-in flow and approve the intended workspace again.

For custom MCP clients

The endpoint uses Streamable HTTP. Clients discover the authorization server from the public OAuth protected-resource metadata, then complete sign-in with PKCE. Each OAuth access token must be valid for the exact MCP endpoint being called and identify the selected workspace. Review the requesting application and redirect destination on the consent screen. Approve only applications you recognize and trust. Keep tokens in the assistant’s credential storage; never put them in server URLs, shared project files, or prompts. MCP requires OAuth access tokens. Portal session tokens and Plyne REST API keys are not accepted as MCP credentials. Existing API keys remain available for the REST API. For protocol details, see the MCP authorization specification.