longportapp/longport-mcp

Overview

An open-source Model Context Protocol server that connects AI assistants to LongPort's developer platform. Written in Rust, it exposes LongPort APIs through the MCP standard so MCP-compatible clients can access trading data and actions.

Best for

Best for
Developers building AI assistants on LongPort's trading platform.

Use cases

• Connect MCP-compatible AI assistants to LongPort services
• Build custom tools that query LongPort account or market data
• Integrate LongPort developer APIs into agent workflows

How to use

Tools exposed

• LONGPORT_MCP_CONFIG_DIR
• LONGPORT_HTTP_URL
• LONGPORT_QUOTE_WS_URL
• LONGPORT_TRADE_WS_URL
• LONGPORT_MCP_LOG_PAYLOADS
• LONGPORT_LOG_PATH
• mcp_tool_calls_total
• mcp_tool_call_duration_seconds
• mcp_tool_call_errors_total

Tested with

Claude Desktop, Claude Code, Cursor, Windsurf, Cline

Example client config

{\n  "mcpServers": {\n    "longport": {\n      "url": "https://mcp.longportapp.com"\n    }\n  }\n}

Notes

An open-source Model Context Protocol server that connects AI assistants to LongPort’s developer platform. Written in Rust, it exposes LongPort APIs through the MCP standard so MCP-compatible clients can access trading data and actions.

4 stars on GitHub. Last updated 2026-07-29. Licensed Apache-2.0.

Use cases

• Connect MCP-compatible AI assistants to LongPort services
• Build custom tools that query LongPort account or market data
• Integrate LongPort developer APIs into agent workflows

Pros

• Open source and auditable
• Rust provides strong performance and memory safety
• Follows the MCP standard for interoperability

Cons

• Very few GitHub stars suggest limited adoption
• No clear evidence of active maintenance or documentation
• Requires familiarity with LongPort’s API and MCP setup

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.