LINE OA MCP Ultimate
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HTTP_TOKEN | No | Optional bearer token for authenticating the Streamable HTTP transport. Only used when running the self-hosted HTTP server. | |
| LINE_MCP_CONFIG | No | Optional custom path to the multi-OA config file (JSON). If not set, the server auto-discovers ~/.line-mcp/config.json. When using multi-OA mode, you can omit LINE_CHANNEL_ACCESS_TOKEN. | |
| LINE_MYSHOP_API_KEY | No | Optional MyShop API key to enable the 14 LINE Shopping tools. In single-OA mode, set this environment variable; in multi-OA mode, add a 'myshop_api_key' field per OA in the config file. | |
| LINE_CHANNEL_ACCESS_TOKEN | Yes | Your LINE Channel Access Token. Required for single-OA mode, which is the default and most common configuration. |
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