MCP Provider Setup
Provider-specific setup for MCP servers that need manual connection - create an OAuth app for a Client ID and Client Secret, or add a provider-generated MCP server URL.
Overview
Set up the provider side of an MCP connection. Most providers need a provider-owned OAuth app with a manual Client ID and Client Secret; a few only need their MCP server URL added manually.
Slack
Use a Slack app when a Slack MCP integration asks for a Slack Client ID and Client Secret.
GitHub
Use a GitHub OAuth app when a GitHub MCP integration asks for a GitHub Client ID and Client Secret.
Zoho
Zoho Cliq exposes its MCP server through the Zoho MCP console. Unlike Slack and GitHub, you do not create an OAuth app or provide a Client ID and Client Secret for Zoho.
Google Workspace
Google Workspace is a QuilrAI-built MCP available in the MCP Store. It exposes Gmail, Google Calendar, and Google Drive tools. The MCP is multi-tenant and does not ship a shared Google OAuth client, so each connection must use its own Google OAuth Client ID and Client Secret created in Google Cloud.
Figma
Figma is a QuilrAI-built MCP available in the MCP Store. It exposes design context, comment, and Code Connect tools. The MCP is multi-tenant and does not ship a shared Figma OAuth app, so each connection must use its own Figma OAuth Client ID and Client Secret created at the Figma developer portal.
Datadog
Datadog exposes its MCP server through an OAuth flow tied to your Datadog organization. Unlike Slack and GitHub, you do not create a separate OAuth app or supply a Client ID and Client Secret. Instead, you register the QuilrAI callback URL in Datadog's organization settings and then add your site-specific Datadog MCP server URL to QuilrAI.
Zoom
Use a Zoom OAuth app when a Zoom MCP integration asks for a Zoom Client ID and Client Secret.
Calendly Custom MCP
Connect the QuilrAI-built Calendly MCP with a customer-owned Calendly OAuth
Azure DevOps Advanced MCP
Connect Azure DevOps Services to QuilrAI through the custom Azure DevOps
Semrush Advanced
Semrush Advanced is a QuilrAI-built MCP for SEO, keyword, backlink, traffic, market, and project research. It uses a Semrush API key instead of a Semrush OAuth Client ID and Client Secret.
BrowserStack Advanced
BrowserStack Advanced is a QuilrAI-built MCP for BrowserStack account discovery, browser and device inventories, Automate and App Automate sessions, diagnostic data, app uploads, and Test Management workflows. It uses a BrowserStack username and access key instead of an OAuth Client ID and Client Secret.