Skip to main content

​
What Are MCP Servers

MCP (Model Context Protocol) Servers enable your apps to connect with external services like Gmail, Google Docs, and GitHub. You can use official pre-built connectors or create custom integrations that work across all your apps.

Official Connectors

One-click setup for Gmail, Google Docs, GitHub, and more

Custom Integrations

Build your own MCP servers using our schema for any service

Use in Copilot

Connected services work automatically with your AI Copilot

Reusable Across Apps

Configure once and use in all your apps

​
Two Connection Methods

Choose the method that fits your workflow:

Quick Connect (Per-App)

Best for: Single app, fast setup
Scope: Current app only
Setup: No configuration needed. Authorize during or after build.

Global Configuration (All Apps)

Best for: Multiple apps, custom services
Scope: All apps in your account
Setup: Define once using MCP Schema, then reuse anywhere.

​
Quick Connect Method

Use this when you need to connect a single app quickly to an official service.
1

Select the connector during build

Choose the official MCP connector you need when building your app.Select MCP connector
2

Authorize after build

When your app is ready, a window will prompt you to sign in and authorize access.Authorization prompt
3

Start using the connection

Once authorized, the connection is active. Use it directly in your app or ask Copilot to interact with the service.
4

Manage access anytime

You can revoke, refresh, or re-authorize at any time from your app settings.Manage connection
App-specific access: Connections made this way only work in the app where you set them up.

​
Global Configuration Method

Use this when you want to configure a custom MCP server once and use it across all your apps.
1

Define your MCP Schema

Create a schema that specifies your server details, authentication method, and available tools. See the schema reference below.
2

Add the MCP to your integrations

Go to your integrations page and create a new custom MCP using your schema.Add custom MCP
3

Use in any app

When building apps, select this custom MCP. It works across all apps in your account without additional setup.Select from integrationsIf the AI doesn’t automatically suggest your custom MCP, you can manually select it from all available integrations.Browse all integrationsChoose custom MCP

​
MCP Schema Reference

Use this schema to define custom MCP servers for the global configuration method.

​
Schema Overview

An MCP schema consists of four main sections:
  1. Version - Track your schema version
  2. Server - Define connection details
  3. Auth - Specify authentication method
  4. Tools - List available operations

​
Version

Track your schema updates with a version string. 
{
  "version": {
    "type": "string"
  }
}
This helps you manage changes when updating your MCP configuration.

​
Server Configuration

Define where your MCP server is hosted and how to connect. 
{
  "server": {
    "type": "object",
    "required": ["url", "transport"],
    "properties": {
      "url": {
        "type": "string"
      },
      "transport": {
        "type": "string",
        "enum": ["https", "sse"]
      }
    },
    "additionalProperties": false
  }
}
Properties:
  • url: The endpoint URL for your MCP service
  • transport: Connection protocol - choose https for standard HTTP or sse for server-sent events

​
Authentication

Specify how clients should authenticate with your MCP server. 
{
  "auth": {
    "type": "object",
    "required": ["type"],
    "properties": {
      "type": {
        "type": "string",
        "enum": ["none", "bearer", "apikey", "basic"]
      },
      "headerName": {
        "type": "string"
      },
      "headerContent": {
        "type": "string"
      }
    },
    "additionalProperties": false
  }
}
Authentication Types:
  • none: No authentication required. Leave headerName and headerContent empty.
  • bearer: Token-based authentication using Bearer tokens
  • apikey: API key authentication
  • basic: Basic HTTP authentication with username and password
Header Configuration: When using bearer, apikey, or basic authentication:
  • headerName: The header name (e.g., Authorization). Case-sensitive.
  • headerContent: The header value including any prefix (e.g., Bearer your-token-here). Case-sensitive.

​
Tools

Define the operations your MCP server provides. 
{
  "tools": {
    "type": "array",
    "items": {
      "type": "object",
      "properties": {
        "name": {
          "type": "string"
        },
        "inputSchema": {
          "type": "object",
          "required": ["type", "properties"],
          "properties": {
            "type": {
              "const": "object"
            },
            "properties": {
              "type": "object",
              "additionalProperties": {
                "type": "boolean"
              }
            },
            "additionalProperties": {
              "type": "boolean"
            }
          }
        },
        "outputSchema": {
          "type": "object",
          "required": ["type", "properties"],
          "properties": {
            "type": {
              "type": "string"
            },
            "properties": {
              "type": "object"
            },
            "additionalProperties": {
              "type": "boolean"
            }
          }
        }
      },
      "required": ["name", "inputSchema"],
      "additionalProperties": false
    }
  }
}
Tool Properties:
  • name: Unique identifier for the tool
  • inputSchema: Defines the expected input format (required)
  • outputSchema: Defines the response format (optional but recommended to improve AI accuracy)

​
Common Uses

Communication

Post updates, send alerts, and automate team notifications

Calendars & Docs

Schedule events, update docs, or sync sheets

Development Tools

Create issues, update repositories, or track development tasks

Business & Social

Automate messages, manage posts, or fetch analytics

Need custom APIs?

Learn how to add OpenAPIs and custom services