Connectors and MCP

Lansenger connectors are integration capabilities provided by the Open Platform, used to connect external systems and business processes to the Lansenger platform, enabling data integration and automated workflows.

Connector Overview

Connectors link Lansenger with third-party systems through standardized interfaces, supporting:

• Push messages and notifications from external systems to Lansenger
• Trigger external system business processes from Lansenger
• Cross-system data synchronization and automation

Connector Types

Webhook Connector

• Receives messages pushed by external systems via a webhook URL
• Supports security settings (signature verification, etc.)
• Suitable for one-way message push scenarios

API Connector

• Bidirectional data interaction via OpenAPI interfaces
• Supports reading Lansenger contacts, sending messages, managing apps, etc.
• Requires app authorization

Event Callback Connector

• Subscribe to Lansenger business events (message reception, personnel changes, etc.)
• Lansenger pushes event data to configured callback URLs
• Suitable for real-time response scenarios

MCP (Model Context Protocol)

MCP is a standardized protocol for AI models to interact with external tools and data sources. Lansenger supports exposing platform capabilities to AI agents via MCP.

MCP Capabilities

• AI agents can call Lansenger OpenAPI interfaces via MCP
• Supports contact queries, message sending, schedule management, and other operations
• Enables AI-driven automated office scenarios

Usage

1. Create an app in the Developer Center and obtain credentials
2. Configure the MCP endpoint
3. AI agents connect to Lansenger via the MCP protocol
4. Call tools and interfaces provided by Lansenger

For detailed MCP configuration and API documentation, see the Developer Documentation.

Connector Development

Development Standards

• Follow Lansenger Open Platform API specifications
• App authorization required
• Supports private deployment scenarios

Publishing Process

1. Create a connector app in the Developer Center
2. Develop and test connector logic
3. Configure callback URLs and API permissions
4. Publish and set visibility scope

For detailed connector development and publishing specifications, see the Connector Development Guide in the Developer Documentation.