Configure a Connection with OAuth Authorization

Business Example: Authorize Access to Customer Meeting Records to Organize Requirements and Follow-Up Items

The sales team uses a customer meeting recording tool to record online customer meetings. An opportunity often involves multiple meetings between initial contact and solution confirmation. Customer requirements, concerns, and agreed action items are spread across different meeting records.

Before the next conversation, a sales representative wants a quick overview of the customer's main concerns, unresolved issues, and their own commitments. After an administrator connects a customer meeting recording tool, each sales representative signs in to their own account and authorizes access. They can then ask WinNexo to query meeting records they have permission to access and help prepare for the next customer conversation.

Administrator Configuration

The following example creates a “Customer Meeting Records” connector. All names, URLs, and configuration values are examples. Before integration, confirm that the provider offers an MCP service that supports WinNexo's OAuth discovery and authorization flow.

Method 1: Configure MCP Manually

1. Open the creation page. In the Admin Console, go to Capability Center > App Connections, click New Connection, and select Configure MCP Manually.
2. Enter the connection information. Select the transport type according to the provider's instructions and set the other fields as needed.

Setting	Example	Instructions
Transport Type	Streamable HTTP	Select according to the provider's integration instructions.
Connector Name	Customer Meeting Records	Use a name that is easy for the team to understand.
Connector URL	https://mcp.example.com/meetings/mcp	Replace this with the actual MCP URL provided by the service provider.
Description	Query customer meeting records accessible to the current user and organize requirements and follow-up items	Describe the connector's purpose.
Tags	Customer Follow-Up	Select or enter as needed.
Headers	Leave blank	This example obtains credentials through OAuth authorization. No personal keys, Tokens, or ${参数名} are required.
Timeout	30 seconds	Adjust according to the service requirements.
Visibility	Public Within the Organization	Choose Public Within the Organization or Role-Specific as needed.

Method 2: Configure MCP with JSON

Click New Connection, select Configure MCP with JSON, paste the following configuration, and replace the service URL with the actual URL:

{
  "mcpServers": {
    "客户会议记录": {
      "type": "streamable-http",
      "url": "https://mcp.example.com/meetings/mcp"
    }
  }
}

Where:

• 客户会议记录 is the connector name and can be changed.
• Replace url with the actual MCP service URL.
• Set type according to the provider's instructions. This example uses streamable-http; use sse for SSE.
• This example obtains credentials through OAuth authorization. Do not add headers or credential parameters, and do not enter users' account passwords or Tokens in the JSON.

Test and Save

After completing configuration, click Test Connection. Once the test passes and you confirm that the system identifies the connection as OAuth Authorization, follow the page instructions to save it and confirm that the connector is enabled. If OAuth is not identified, check that you entered the correct MCP service URL and confirm with the provider that it supports the corresponding OAuth integration flow.

A successful administrator test does not mean that users have authorized access. Each user must still sign in to their own third-party account and authorize access in the user interface before using the connector.

User Instructions

1. Find the connector. Find “Customer Meeting Records” under Capability Center > App Connections > Enterprise App Connections and click Authorize Now.
2. Sign in and authorize. On the page that opens, sign in to your meeting recording tool account, review the requested permissions, and authorize access.