LINE Issue MCP

A system that collects customer issues from LINE Official Account/Group, then uses AI to triage messages, inspect recent commits and related route/path in GitLab, and automatically create a ClickUp task in the Client Issues list.

Flow

LINE OA / Group
      │ webhook + signature
      ▼
HTTP /webhooks/line
      │
      ▼
OpenAI Responses API
  classify + priority + summarize + search terms
      │
      ▼
GitLab recent commits + commit diffs
  rank related commits + paths + routes
      │
      ▼
ClickUp / Client Issues
  task + tag + priority + GitLab evidence

Classification: Bug, Feature Request, Q&A
Priority: Low, Medium, High, Critical

Related MCP server: Kepler MCP GitLab Server

Getting Started

Requires Node.js 20 or higher.

npm install
copy .env.example .env
npm run dev

Set up at least these .env variables:

• LINE_CHANNEL_SECRET: from LINE Developers > Messaging API channel

• OPENAI_API_KEY: API key for the Responses API

• GITLAB_TOKEN: token with repository read access

• GITLAB_PROJECT: namespace/project

• CLICKUP_API_TOKEN: personal token or OAuth token

• CLICKUP_LIST_ID: ID of the Client Issues list (recommended)

If CLICKUP_LIST_ID is not set, set CLICKUP_TEAM_ID; the system will search every Space/Folder, the system will search every Space/Folder of the Workspace for a list whose name matches CLICKUP_LIST_NAME=Client Issues.

Set the LINE webhook URL to a public HTTPS URL:

https://your-domain.example/webhooks/line

The health check is at GET /health.

MCP tools

Run the MCP server via stdio:

npm run mcp

There are 2 tools:

• analyze_client_experience: analyzes and searches GitLab context but does not create a task

• create_client_issue: does the full flow and creates a ClickUp task

Example MCP client config:

{
  "mcpServers": {
    "line-issue": {
      "command": "npm",
      "args": ["run", "mcp"],
      "cwd": "C:/absolute/path/to/line-issue-mcp"
    }
  }
}

Important Behaviors

• Verify x-line-signature from the raw request body before accepting the event

• Reply to the LINE webhook immediately, then process in the background

• Use webhookEventId to prevent duplicate events within a single process

• GitLab failure does not block creating the ClickUp task; the task will include a warning instead

• Q&A creates a task by default; can be disabled with CREATE_QA_TASKS=false

• OpenAI requests use Structured Outputs and store: false

Before production

This MVP stores event deduplication in memory, suitable for a single instance. For production, you should add a durable queue and an idempotency store (such as Redis/Postgres), a retry/dead-letter queue, a secret manager, observability, and an allowlist for the repository/ClickUp workspace.