Shioaji MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SHIOAJI_API_KEY | Yes | Your Sinopac Shioaji API Key. | |
| SHIOAJI_SECRET_KEY | Yes | Your Sinopac Shioaji Secret Key. | |
| SHIOAJI_TRADING_ENABLED | No | Set to 'true' to enable trading operations (place_order, cancel_order). Defaults to 'false' for read-only mode. | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_account_infoD | Get account information |
| search_contractsC | Search for trading contracts |
| get_snapshotsC | Get real-time market snapshots |
| get_kbarsC | Get historical K-bar data |
| place_orderB | Place a trading order (requires SHIOAJI_TRADING_ENABLED=true) |
| cancel_orderC | Cancel an existing order (requires SHIOAJI_TRADING_ENABLED=true) |
| list_ordersC | List all orders |
| get_positionsC | Get current positions from stock and/or futures accounts |
| get_account_balanceC | Get account balance information for stock and/or futures accounts |
| check_terms_statusB | Check service terms signing status and API testing completion |
| run_api_testB | Run API test for service terms compliance (login and order tests) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Every tool has a clearly distinct purpose with no ambiguity. Each targets a specific action on a specific resource (e.g., get_account_balance vs. get_positions, place_order vs. cancel_order). The descriptions clearly differentiate their functions, making misselection unlikely.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., get_account_balance, place_order, search_contracts). There are no deviations in naming conventions, making the set predictable and easy to understand.
With 11 tools, the count is well-scoped for a trading API server. Each tool earns its place by covering essential functions like account management, market data, order handling, and compliance checks, without being overwhelming or insufficient.
The tool set provides strong coverage for core trading operations, including account info, market data, order placement/cancellation, and compliance. A minor gap exists in update operations (e.g., modifying orders or positions), but agents can work around this by canceling and re-placing orders.