LINE OA MCP Ultimate
by teresa1034
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 (for self-hosted / always-on server deployments). Not needed for stdio mode. | |
| LINE_MCP_CONFIG | No | Custom path to the multi-OA JSON config file. When set, the server uses this instead of the default ~/.line-mcp/config.json, and the LINE_CHANNEL_ACCESS_TOKEN env var should be dropped. 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 MyShop API key (from oaplus.line.biz → Settings → API keys, Admin role). Setting it unlocks the 14 LINE Shopping tools; without it the server stays messaging-only. | |
| LINE_CHANNEL_ACCESS_TOKEN | No | Your LINE Channel Access Token (long-lived). Required for single-OA mode. Get it from the LINE Developers Console → Messaging API tab → Channel access token. 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
ResponsivenessNo issues