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 self-hosted Streamable HTTP transport. | |
| LINE_MCP_CONFIG | No | Optional custom path to the multi-OA JSON config file. The server first checks LINE_MCP_CONFIG, then ~/.line-mcp/config.json, then falls back to the LINE_CHANNEL_ACCESS_TOKEN environment variable (single-OA mode). | |
| LINE_MYSHOP_API_KEY | No | Optional MyShop (LINE Shopping) API key. When set, the 14 LINE Shopping tools (products, inventory, orders, parcel labels, settlements, checkout links) are enabled; without it the server stays messaging-only. Get it from oaplus.line.biz → Settings → API keys (Admin role). In multi-OA mode set "myshop_api_key" per OA in the config file instead. | |
| LINE_CHANNEL_ACCESS_TOKEN | Yes | Your LINE Messaging API channel access token (long-lived). Required in single-OA mode. Obtain it from the LINE Developers Console → Messaging API channel → Messaging API tab → Channel access token → Issue. In multi-OA mode this can be omitted, since the server auto-discovers the OA tokens from ~/.line-mcp/config.json. |
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
ResponsivenessNo issues