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 | Path to the multi-OA JSON config file. When set (or when ~/.line-mcp/config.json exists), the server uses multi-OA mode and LINE_CHANNEL_ACCESS_TOKEN is not needed. Resolution order: LINE_MCP_CONFIG env var → ~/.line-mcp/config.json → LINE_CHANNEL_ACCESS_TOKEN env var. | |
| LINE_MYSHOP_API_KEY | No | Optional MyShop API key (Admin role) to enable the 14 LINE Shopping tools. Without it the server stays messaging-only. In multi-OA mode, set a per-OA `myshop_api_key` in the config file instead. | |
| LINE_CHANNEL_ACCESS_TOKEN | No | Your LINE Channel Access Token. Required for single-OA mode (the default). Issued from the LINE Developers Console under your Messaging API channel. |
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