Connectors

Connectors let LanMate read and write your office platforms and external services (Feishu, WeCom, email, Tencent Docs, etc.). Each connector is authorized individually; data flows only between your computer and the service.

Officially listed connectors cover common office scenarios, for example:

• Feishu / WeCom / DingTalk: docs, messages, calendars, and other collaboration platforms
• Email: generic IMAP/SMTP mail service — send, receive, and organize mail as soon as it’s installed
• Tencent Docs / WPS Base: online documents and spreadsheets
• Tencent Meeting: meeting and schedule management
• Safari (macOS): built on Safari’s native capabilities — no install, zero credentials, direct connection
• Chrome DevTools: a browser debugging channel for developers
• GitHub / Gitee / Notion: code repositories and knowledge bases
• AkShare / iFinD / Wind: financial data
• Amap / Baidu Maps: mapping and location services
• QiAnXin ecosystem: in-org secure office components

The Apple five (Notes / Mail / Calendar / Contacts / Reminders) and Outlook/Office are built-in local app tools, not part of the connector marketplace: macOS uses system automation and Office on Windows uses COM; first use requires system automation permission.

Difference from Custom External Tools

Put simply: connectors work out of the box and suit ordinary users; custom tools are flexible but you configure them yourself.

Usage

1. Open the extensions management page from “Extensions” in the sidebar and switch to the “Connectors” tab to see what’s available
2. Click Install — the program is downloaded automatically or an existing local one is used
3. Click Connect and follow the prompts to authorize (usually a browser login)
4. Once authorized, just say “help me with this Feishu doc…” in chat

Managing in Conversation

You can manage connectors without opening the settings page: in chat, just say “install the email connector for me” or “pause the Feishu connector”, and LanMate handles installation, config pre-fill, authorization, and start/stop — sensitive operations still pop an approval card for confirmation.

Custom Connectors

Services your organization hasn’t distributed can be added yourself:

• Form mode: enter the command/address and fill in parameters one by one
• Paste JSON: supports Claude Code / Cursor .mcp.json fragments; parse, confirm, and batch-create

OAuth connectors support standard discovery endpoints and dynamic registration — enter the discovery URL and go (Client ID can be left blank for auto-registration).

Status

Connector cards show status with icons and buttons:

• Needs configuration: installed, but credentials are missing or expired (key icon)
• Connectable / Connecting: configuration ready, waiting for authorization or connecting
• Connected: the connector is running and usable
• Connection error: yellow dot, with “Retry”; a red dot means the operation failed
• Disabled / Update available: turned off, or a new version exists in the marketplace

Managing Connectors

• Update: click when a new version is available

• Rollback: revert to the previous version if an update misbehaves

• Disconnect: clears authorization but keeps the entry (reversible, no second confirmation)

• Delete: removes local configuration, site address, and credentials together and cannot be undone after confirmation; to change only credentials, use “Clear configuration” on the detail page

• On the connector detail page you can enable or disable each tool and star frequently used ones (up to 20 in total, evicted by usage frequency; takes effect next session)

• Offline package import: the “Import offline package” entry at the top of the Connectors tab accepts .lmpkg files (enabled only after signature verification passes and policy allows)

Notes

• Connectors are listed centrally by organization admins in the backend; individual users cannot publish their own
• When you aren’t signed in to Lansenger, official public connectors are still shown and can be installed anonymously; “Add connector” for creating custom connectors is always available