LINE's official MCP server lets AI agents run Official Accounts without API code

LINE has published an official Model Context Protocol (MCP) server for its Messaging API. The release means a configured AI agent can operate a LINE Official Account directly, replying to users, running broadcasts and delivering Flex Message cards, without anyone writing custom code against the REST API. A walkthrough published on dev.to documents a working end-to-end setup built on the Codex coding agent, and records the points where LINE's documentation and observed behaviour do not match.

What the agent can do

The dev.to author connected the server to Codex and exercised every capability it exposes, from setting up a fresh account through to delivering a message to a real phone. Because MCP is agent-agnostic, the same LINE server also works with Claude Desktop and Cline. The only thing that changes between clients is the format of the configuration file each one expects.

That difference is where most people stumble first, according to the walkthrough: Codex keeps its MCP configuration in TOML at ~/.codex/config.toml, while most published guides assume the JSON format used by Claude Desktop. The author identifies this as the single most common setup mistake.

Where documentation and reality diverge

The walkthrough highlights two further mismatches beyond the config format.

Verified status and API capability are separate concerns. A free, unverified account can use the Messaging API, but the get_follower_ids tool returns a 403 Forbidden error until the account is either verified or moved to a premium plan. An agent that appears correctly configured can still hit a permissions wall here.

Official security guidance also conflicts with an official feature. LINE's example configuration disables npm install scripts as a hardening measure, but that same setting prevents installation of the headless browser that the rich menu tool depends on. Following the recommended config therefore breaks one of the server's own tools.

Agent habits and safeguards

The guide also captures behavioural quirks of the agent itself. Codex is a coding agent first: when asked in natural language to build a rich menu, it responded by writing a Node script rather than calling the MCP tool. Explicitly naming the tool in the prompt resolved this.

The more consequential caveat is that broadcasts on LINE cannot be recalled once sent. The walkthrough recommends setting default_tools_approval_mode to "writes", so the agent must ask for human approval before any operation that pushes content to followers. The author notes that every screenshot in the guide comes from the real working setup, errors included, and that the article is available in both English and Thai.

Why it matters

MCP is quickly becoming the standard plumbing that lets AI agents call external services, and an official server from a platform as widely used as LINE moves agent-driven account management from experiment to supported product. For businesses that run Official Accounts, automation shifts from bespoke integration work to configuration and prompting.

The friction points in the dev.to walkthrough matter just as much as the capability. They show that agent integrations inherit the quirks of the protocol, the client and the platform all at once, and that small defaults, a config file format, an npm flag, an approval mode, decide whether an autonomous agent safely drafts messages or fires an unrecoverable broadcast at real customers.