LINE Context Relay
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| line_statusA | Refresh and verify a new stable read-only snapshot of the local LINE DB, then report discovery, Keychain availability, decryption, LINE process state, and snapshot time without returning secrets or chat content. Call this before every LINE read task. |
| list_chats | List recent chats from a stable read-only snapshot of LINE's local encrypted DB. Does not require LINE to be foreground or running. |
| read_history | Read bounded local history by exact display name or chatId. Every call opens a new stable read-only snapshot of the current source DB and returns its refresh time. Use order=oldest for the first cursor page, then pass the returned timestampMs+messageId cursor. Exact duplicate names return candidate chatIds instead of guessing. Successful reads are deduplicated into local memory. |
| refresh_latest | Wait for one exact chat to advance in fresh stable read-only LINE DB snapshots. It first polls passively, then performs only a fixed LINE app activation or fixed LINE app launch when needed. It never selects a chat, focuses the composer, types, pastes, presses keys, or sends messages. Call read_history separately after success. |
| get_relationship_context | Read the local-only relationship summary and its imported-message cursor for one exact LINE chat. This may initialize or migrate the private local memory schema, but it never modifies LINE's source DB and never uses UI automation. |
| save_relationship_context | Save bounded model-derived relationship context only to private local memory for one exact chat. The cursor must already exist in read_history memory and expectedContextVersion prevents stale overwrites. It never modifies LINE's source DB, controls LINE, or sends a message. |
| sync_older_messages | Best-effort, narrowly constrained older-history UI backfill. Do not use it to refresh ordinary latest-message reads: use line_status, refresh_latest, then read_history. It can only resolve an existing exact chat and use the audited Peekaboo adapter; it never focuses the composer, types/pastes a message, or presses Return. |
| line_health | Return a redacted health report for DB snapshots, Keychain, decrypt status, memory DB, MCP allow-list, Peekaboo, permissions, and power/Remote evidence. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/LEO0047/line-chat-advisor-mcp-ai-assistant'
If you have feedback or need assistance with the MCP directory API, please join our Discord server