| 0 |
| Ecosystem | 0 | 0 |
| Match Graph | 0 | 0 |
| Pricing | Free | Free |
| Capabilities | 7 decomposed | 9 decomposed |
| Times Matched | 0 | 0 |
Enables Claude and other MCP clients to send text, template, and rich messages to LINE users through the LINE Messaging API by translating MCP tool calls into authenticated LINE API requests. Implements the MCP server specification to expose LINE's message endpoints as standardized tools, handling OAuth token management and request serialization automatically.
Unique: Bridges MCP protocol and LINE Messaging API by implementing the MCP server specification to expose LINE message sending as standardized tools, eliminating the need for developers to write custom API wrapper code or manage OAuth token lifecycle manually.
vs alternatives: Simpler than building a custom LINE API wrapper because it leverages the MCP standard, allowing any MCP-compatible LLM (Claude, others) to control LINE messaging without client-side integration code.
Automatically generates MCP-compliant tool schemas that map LINE Messaging API message types (text, template, flex, quick reply) into callable functions with proper parameter validation and type hints. Uses JSON Schema to define input constraints, allowing MCP clients to understand available message capabilities and validate payloads before sending.
Unique: Generates MCP-compliant tool schemas specifically for LINE message types, mapping LINE's API documentation into LLM-friendly function definitions with JSON Schema validation, rather than requiring manual schema authoring.
vs alternatives: More discoverable than raw LINE API documentation because schemas are embedded in the MCP server, allowing Claude to introspect available message types and parameters without external documentation lookup.
Receives incoming LINE webhook events (messages, joins, follows) via HTTP POST, parses the LINE signature for authenticity verification, and exposes event data as context or tool inputs to MCP clients. Implements LINE's webhook signature validation using HMAC-SHA256 to ensure requests originate from LINE's servers before processing.
Unique: Implements LINE webhook signature verification (HMAC-SHA256) natively within the MCP server, ensuring only authentic LINE events trigger agent actions, and propagates parsed event context directly to MCP tool calls without requiring separate webhook middleware.
vs alternatives: More secure than generic webhook handlers because it validates LINE's HMAC signature before processing, and tighter integration than separate webhook + MCP layers because event parsing and context propagation happen in a single component.
Fetches user profile data (name, avatar, status message) and group/room metadata from the LINE Messaging API and exposes it as MCP tool outputs or context. Implements caching of profile data to reduce API calls and handles rate limiting from LINE's API gracefully.
Unique: Caches LINE user and group metadata within the MCP server to reduce redundant API calls, allowing Claude to reference user names and group context without triggering a LINE API request on every message.
vs alternatives: More efficient than calling LINE API directly for every user reference because caching is built-in, and more context-aware than stateless bots because metadata is available to Claude's reasoning layer.
Exposes LINE's rich menu and quick reply APIs as MCP tools, allowing Claude to create, update, or delete rich menus and quick reply buttons programmatically. Translates MCP tool calls into LINE Messaging API requests with proper JSON serialization for menu structure and button definitions.
Unique: Exposes LINE rich menu and quick reply management as MCP tools, enabling Claude to dynamically construct and deploy menu structures without requiring separate UI management code or manual LINE Official Account configuration.
vs alternatives: More dynamic than static rich menus because Claude can reason about user context and adjust menu structure programmatically, versus manually configuring menus in the LINE Official Account dashboard.
Implements LINE's broadcast and multicast APIs as MCP tools, allowing Claude to send messages to multiple users or groups in a single API call. Handles recipient list management and message payload serialization for bulk delivery scenarios.
Unique: Wraps LINE's broadcast and multicast APIs as MCP tools, allowing Claude to send bulk messages without iterating through recipient lists, and handles the 500-recipient multicast limit transparently.
vs alternatives: More efficient than sending individual messages because broadcast/multicast use a single API call, and more discoverable than raw LINE API because the MCP tool abstracts recipient list management.
Provides a mechanism to store and retrieve conversation state (user preferences, conversation history, session data) associated with LINE user IDs, enabling Claude to maintain context across multiple message exchanges. Implementation details (in-memory, database, external store) are abstraction-dependent but expose a key-value interface to MCP clients.
Unique: Provides a state management abstraction within the MCP server that allows Claude to store and retrieve conversation context keyed by LINE user ID, enabling multi-turn stateful interactions without requiring external session management.
vs alternatives: More integrated than external session stores because state is accessible directly from MCP tools, and more convenient than LINE's built-in message history because Claude can store arbitrary structured data, not just message transcripts.
Executes SQL queries against Supabase PostgreSQL instances through the Model Context Protocol, translating natural language or structured query requests into parameterized SQL statements. Uses MCP's tool-calling interface to expose database operations as callable functions with schema validation, enabling LLM agents to perform CRUD operations, joins, and aggregations with automatic connection pooling and credential management through Supabase client SDK.
Unique: Exposes Supabase PostgreSQL as MCP tools with automatic credential injection from Supabase client SDK, eliminating manual connection string management and enabling seamless LLM-to-database queries within Claude or compatible agents
vs alternatives: Tighter integration than generic SQL MCP servers because it leverages Supabase's built-in authentication and connection pooling rather than requiring separate database credential configuration
Exposes Supabase Auth session state and user metadata through MCP tools, allowing agents to inspect current authentication context, retrieve user profiles, and trigger auth-related operations. Integrates with Supabase's JWT-based auth system to validate sessions and access user claims without re-authenticating, using the Supabase client's built-in session management.
Unique: Integrates Supabase's JWT-based auth system directly into MCP tool interface, allowing agents to inspect and act on auth state without managing separate credential stores or re-authentication flows
vs alternatives: More seamless than generic auth MCP servers because it leverages Supabase's built-in session management and avoids redundant credential passing between agent and auth system
Invokes Supabase Edge Functions (serverless TypeScript/JavaScript functions) through MCP tools, passing parameters and receiving results with optional streaming support. Uses Supabase's edge function HTTP API to trigger functions with automatic authentication headers and response parsing, enabling agents to execute custom business logic without embedding it in the agent itself.
Supabase scores higher at 42/100 vs @line/line-bot-mcp-server at 22/100. @line/line-bot-mcp-server leads on ecosystem, while Supabase is stronger on quality.
Need something different?
Search the match graph →© 2026 Unfragile. Stronger through disorder.
Unique: Exposes Supabase Edge Functions as MCP tools with automatic authentication and response parsing, allowing agents to invoke custom serverless logic without managing HTTP clients or credential injection
vs alternatives: More integrated than generic HTTP MCP tools because it handles Supabase-specific authentication, error handling, and response formatting automatically
Subscribes to real-time changes on Supabase tables through MCP's event streaming interface, using Supabase's PostgreSQL LISTEN/NOTIFY mechanism to push INSERT, UPDATE, and DELETE events to agents. Maintains persistent WebSocket connections and filters events by table and row-level policies, enabling agents to react to database changes without polling.
Unique: Bridges Supabase's PostgreSQL LISTEN/NOTIFY real-time system with MCP's tool interface, enabling agents to subscribe to database changes without managing WebSocket connections or event serialization
vs alternatives: More efficient than polling-based approaches because it uses Supabase's native real-time infrastructure rather than repeated database queries
Manages files in Supabase Storage buckets through MCP tools, supporting upload, download, list, and delete operations with automatic authentication and path-based access control. Uses Supabase's S3-compatible storage API with built-in support for public/private buckets and signed URLs for temporary access, enabling agents to handle file I/O without managing cloud storage credentials.
Unique: Exposes Supabase Storage's S3-compatible API as MCP tools with automatic authentication and signed URL generation, eliminating the need for agents to manage cloud storage credentials or generate temporary access tokens
vs alternatives: More integrated than generic S3 MCP tools because it leverages Supabase's built-in bucket policies and authentication rather than requiring separate AWS credentials
Performs semantic similarity searches on vector embeddings stored in Supabase PostgreSQL using pgvector extension, translating natural language queries into embedding vectors and executing cosine/L2 distance searches. Integrates with embedding providers (OpenAI, Cohere) or uses pre-computed embeddings, enabling agents to retrieve semantically similar documents or records without full-text search limitations.
Unique: Integrates pgvector directly into MCP tools with automatic embedding generation and distance calculation, enabling agents to perform semantic search without managing separate vector database infrastructure
vs alternatives: More efficient than external vector databases (Pinecone, Weaviate) for Supabase users because it colocates embeddings with relational data, reducing network latency and simplifying data synchronization
Exposes Supabase database schema information through MCP tools, allowing agents to discover table structures, column types, constraints, and relationships without manual schema documentation. Queries PostgreSQL information_schema and Supabase metadata tables to dynamically generate schema descriptions, enabling agents to construct valid queries and understand data relationships.
Unique: Queries Supabase's PostgreSQL information_schema directly through MCP tools, enabling agents to dynamically discover and adapt to database schemas without pre-configured schema definitions
vs alternatives: More flexible than static schema definitions because it reflects live database state, including recent migrations or schema changes
Enforces Supabase Row-Level Security policies within agent queries, ensuring that agents can only access rows permitted by RLS rules defined in the database. Evaluates policies based on authenticated user context (JWT claims, user ID) and applies WHERE clause filters automatically, preventing unauthorized data access at the database layer rather than application layer.
Unique: Delegates authorization enforcement to PostgreSQL RLS policies rather than implementing authorization in agent code, ensuring that data access rules are centralized and cannot be bypassed by agent logic
vs alternatives: More secure than application-level authorization because RLS is enforced at the database layer, preventing accidental data leaks even if agent code has bugs
+1 more capabilities