PromptScout MCP beta
PromptScout MCP is in beta for eligible Growth-and-higher teams. It lets an MCP client use PromptScout context and selected actions for one approved brand without sharing a manual token.
Availability is intentionally limited during beta. If MCP access is not available in your brand's Integrations page, your team or plan is not enabled for this connection yet. This guide does not guarantee that every MCP client supports the required OAuth flow.
Before you connect
You need:
- A PromptScout account with an eligible team and a selected brand.
- Access to that brand's Integrations page.
- An MCP client your team has confirmed can connect to a remote server through OAuth.
- Authority to approve access for the selected brand and any requested write permissions.
Connect a client
- Open your brand dashboard and go to Integrations.
- In MCP access, copy the displayed MCP server URL:
https://mcp.promptscout.app/mcp. - Add that URL in your MCP client's server settings.
- Complete the OAuth sign-in and review the client, selected brand, and requested permissions before approving.
- Return to Integrations to confirm the connected client, authorization date, and last-used state.
Each connection is limited to the brand you approve. A connected client is not a general PromptScout account connection.
What a connected client can do
Every approved connection can read PromptScout context for its granted brand, including brand availability, setup state, prompts and prompt groups, AI provider configuration, and current Tasks with their evidence or execution package.
The OAuth approval can also request write permissions. When you explicitly approve them, a client can:
- Manage prompts, prompt groups, and enabled prompt state.
- Update enabled AI providers within your plan and billing limits.
- Generate eligible Tasks and record a completion receipt.
Write access is separate from ordinary read context. PromptScout does not add it silently; adding a new write permission requires reconnecting the client and approving it in OAuth. MCP actions do not run monitors, crawls, publishing, outreach, or pull requests.
Manage or revoke access
Use Integrations to review each OAuth client separately. You can remove a granted write permission for a connection, or revoke that connection entirely. Revoking one client removes its access; other connected MCP clients remain connected. A revoked client must be authorized again before it can reconnect.
OAuth discovery reference
Most teams can let their MCP client complete discovery automatically. This reference is for client configuration and troubleshooting; it is not a second public documentation route.
- MCP resource:
https://mcp.promptscout.app/mcp - Protected-resource metadata:
https://mcp.promptscout.app/.well-known/oauth-protected-resource/mcp - Compatibility metadata URL:
https://mcp.promptscout.app/.well-known/oauth-protected-resource - Authorization server:
https://sbrmhaklobcvrywmsksd.supabase.co/auth/v1
An unauthenticated request to the MCP resource returns an OAuth bearer challenge that points to the protected-resource metadata. That metadata identifies the MCP resource, the authorization server, and bearer-header authentication. The authorization server publishes its own OAuth metadata; a compatible client follows that metadata to start OAuth.
PromptScout brand permissions are managed in the approval flow and are distinct from OAuth identity scopes. Do not assume custom PromptScout permissions can be supplied as arbitrary OAuth scope values. Keep the resource bound to https://mcp.promptscout.app/mcp and let the client follow the discovery metadata.
Next steps
- Keep the approved Brand accurate so the connection stays tied to the right business context.
- Manage the prompts a client can work with in Prompts.
- Use Weekly workflow to review Task evidence and completion receipts.