Configure a Connection with Enterprise Credentials

Enterprise credentials are company-provided accounts or keys configured centrally by an administrator. Team members share these credentials when accessing the service through the connector, without entering credentials or signing in to authorize access individually. This method applies to centrally purchased services that allow shared team use.

Business Example: Share a Company Information Service to Screen Prospective Customers

The company purchases a company information service that sales representatives use to look up business registration details, operating status, and risk information. Before following up on a new batch of leads, sales representatives want to enrich customer profiles and identify which companies match their target criteria and which have business risks that need further investigation.

If the provider supplies an enterprise key that the team may share, the administrator can configure it in the MCP connector. Sales representatives can then enable the connector and ask WinNexo to query prospective customer information in batches, helping them choose follow-up targets while sharing the company's purchased query quota.

Administrator Configuration

The following example creates an “Enterprise Customer Information Query” connector. All names, URLs, and configuration values are examples. Before configuration, obtain the actual MCP service URL and enterprise credentials that may be shared by the team from the provider.

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. The following example uses a Bearer Token:

Setting	Example	Instructions
Connector URL	https://mcp.example.com/company-info/mcp	This is an example URL. Replace it with the actual MCP service URL.
Headers	Name: Authorization; Value: Bearer demo-key-123	Replace demo-key-123 with the actual enterprise credential. Keep Bearer and the single space after it.

If the service requires a different Header format, replace the values according to the following table. These are alternative examples; you do not need to enter all of them:

Service Requirement	Header Name	Header Value
API Key	The name specified by the provider, such as X-API-Key	The actual enterprise Key, such as demo-key-123
Key and Secret passed through separate Headers	Enter each provider-specified name on a separate line, such as X-API-Key and X-API-Secret	Enter the actual enterprise Key and Secret separately. This only applies to directly passed values, without dynamic signing.
Basic Auth	Authorization	Basic followed by the Base64-encoded value of 用户名:密码. Keep the single space after Basic.

Method 2: Configure MCP with JSON

Click New Connection, select Configure MCP with JSON, paste the following configuration, and replace the service URL and enterprise credential with the actual values. This example also uses a Bearer Token:

{
  "mcpServers": {
    "企业客户信息查询": {
      "type": "streamable-http",
      "url": "https://mcp.example.com/company-info/mcp",
      "headers": {
        "Authorization": "Bearer demo-key-123"
      }
    }
  }
}

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.
• The field names in headers correspond to Header Name, and the field values correspond to Header Value. Replace demo-key-123 with the actual enterprise credential, keeping Bearer and the single space after it.
• If the service requires another authentication format, replace the names and complete values in headers according to the table above. For example, an API Key can be written as "headers": { "X-API-Key": "******" }. You do not need to keep the Authorization line from the Bearer example unless the provider also requires it.

TIP

If the provider requires enterprise credentials in the URL, enter the fixed values directly in Connector URL for manual configuration, or in url for JSON configuration. Configure Headers as required by the service; do not add the same credentials again.

Test and Save

After completing either configuration method, click Test Connection. The system verifies the connection using the enterprise credentials you entered. Once the test succeeds and you confirm that the system identifies the connection as Static Credentials (Enterprise Credentials), follow the page instructions to save it and confirm that the connector is enabled.

If authentication fails, check that the credentials are valid and that the Header names, fixed prefixes, and value formats match the service requirements.

User Instructions

After the administrator completes configuration, users can find and directly use the app connection under Capability Center > App Connections > Enterprise App Connections.