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 | Custom path to the multi-OA config JSON file (for agencies managing several OAs). Defaults to ~/.line-mcp/config.json. In multi-OA mode the LINE_CHANNEL_ACCESS_TOKEN env var should be dropped. | |
| LINE_MYSHOP_API_KEY | No | Optional MyShop Open API key (Admin role) that unlocks the 14 LINE Shopping tools. Without it the server stays messaging-only. | |
| LINE_CHANNEL_ACCESS_TOKEN | No | Your LINE Messaging API channel access token. Required in single-OA mode (the default) so the server can operate your LINE Official Account. |
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