LINE OA MCP Ultimate
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HTTP_TOKEN | No | Bearer token used to authenticate the optional Streamable HTTP transport (self-hosted / remote use). | |
| LINE_MCP_CONFIG | No | Custom path to the multi-OA JSON config file (default auto-discovery path is ~/.line-mcp/config.json). Use this for agencies managing several LINE Official Accounts from one config. When using this mode, drop the LINE_CHANNEL_ACCESS_TOKEN env var. Resolution order: LINE_MCP_CONFIG env var → ~/.line-mcp/config.json → LINE_CHANNEL_ACCESS_TOKEN env var (single-OA fallback). | |
| LINE_MYSHOP_API_KEY | No | Optional LINE Shopping (MyShop) API key. When set, the server registers 14 shopping tools (products, inventory, orders, parcel labels, settlements, checkout links). Get it from oaplus.line.biz → Settings → API keys (Admin role). Without it, the server stays messaging-only. In multi-OA mode, set "myshop_api_key" per OA in the config file instead. | |
| LINE_CHANNEL_ACCESS_TOKEN | No | Your LINE Channel Access Token (long-lived), issued from the LINE Developers Console under Messaging API → Channel access token. Used in single-OA mode. Treat it like a password. |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityActive
ResponsivenessResponsive