| 0 |
| Ecosystem | 0 | 0 |
| Match Graph | 0 | 0 |
| Pricing | Free | Free |
| Capabilities | 10 decomposed | 9 decomposed |
| Times Matched | 0 | 0 |
Implements a bidirectional protocol adapter that translates Model Context Protocol tool calls from AI agents (like Claude) into LINE Messaging API requests using the @line/bot-sdk. The server uses StdioServerTransport for stdio-based communication with the AI agent and converts structured MCP tool invocations into authenticated LINE API calls, handling schema validation via Zod before transmission.
Unique: Uses MCP's stdio-based transport protocol as the primary integration point rather than REST webhooks, enabling direct stdio communication between AI agents and the LINE server without requiring HTTP infrastructure or webhook URL exposure
vs alternatives: Simpler than building custom REST API wrappers because it leverages MCP's standardized tool-calling interface, reducing boilerplate and making the integration portable across any MCP-compatible AI agent
Implements the push_text_message tool that sends plain-text messages to a specific LINE user by user ID. The tool accepts a message.text parameter and optional user_id, validates input via Zod schema, and invokes the LINE Bot SDK's client.pushMessage() method with the user ID and text message object, returning the LINE API response with message metadata.
Unique: Exposes LINE's pushMessage API as a discrete MCP tool with Zod-validated schemas, allowing AI agents to invoke messaging without understanding LINE SDK internals or managing authentication tokens
vs alternatives: More direct than building a custom REST endpoint because it integrates directly into the agent's tool-calling interface, eliminating the need for agents to construct HTTP requests or parse LINE API documentation
Implements push_flex_message and broadcast_flex_message tools that send LINE's Flex Message format (JSON-based rich messages with buttons, carousels, and interactive components) to individual users or all followers. The tools accept message.altText (fallback text), message.content or message.contents (Flex message JSON structure), validate via Zod, and invoke the LINE Bot SDK's pushMessage() or broadcastMessage() methods with the Flex message object.
Unique: Exposes both targeted (push_flex_message) and broadcast (broadcast_flex_message) variants as separate tools, allowing agents to choose between individual delivery and mass distribution without conditional logic
vs alternatives: Enables agents to send interactive UI elements (buttons, carousels) directly through the messaging interface, whereas plain text tools require agents to describe actions in prose or use external link generation
Implements the broadcast_text_message tool that sends a plain-text message to all followers of a LINE Official Account without requiring individual user IDs. The tool accepts message.text, validates via Zod, and invokes the LINE Bot SDK's broadcastMessage() method, which distributes the message to the entire follower base in a single API call.
Unique: Separates broadcast messaging into its own tool distinct from targeted push_text_message, forcing agents to explicitly choose between one-to-one and one-to-many delivery patterns rather than inferring intent from missing user IDs
vs alternatives: Simpler than agents managing follower lists or pagination because LINE's broadcastMessage API handles distribution server-side, eliminating the need for agents to query user lists or batch messages
Implements the get_profile tool that retrieves a LINE user's profile information (display name, profile picture URL, status message) by user ID. The tool invokes the LINE Bot SDK's getProfile() method, which queries LINE's user profile API and returns structured profile data. The server does not implement caching, so repeated calls for the same user incur API latency.
Unique: Exposes LINE's getProfile API as a discrete MCP tool, allowing agents to fetch user metadata on-demand without managing SDK client initialization or error handling
vs alternatives: Enables agents to personalize responses with user names and pictures without requiring agents to parse webhook payloads or maintain user databases, delegating profile storage to LINE
Implements optional DESTINATION_USER_ID environment variable that serves as a fallback user ID when push_text_message or get_profile tools are invoked without an explicit user_id parameter. The server reads this variable at startup and uses it as the default target for message delivery, reducing boilerplate in agent configurations where a single primary user is the primary recipient.
Unique: Uses environment variables for runtime configuration rather than hardcoding or requiring agent-side configuration, enabling deployment-time customization without rebuilding the server
vs alternatives: Simpler than agents managing user ID routing logic because the server centralizes default targeting, reducing conditional logic in agent tool calls
Integrates Zod schema validation library to validate all tool parameters (message text, user IDs, Flex message structures) before invoking LINE Messaging API calls. The server defines Zod schemas for each tool's input, validates incoming MCP tool calls against these schemas, and returns validation errors to the agent if parameters are malformed or missing required fields.
Unique: Uses Zod for declarative schema validation rather than imperative if-checks, enabling reusable, composable validation logic that can be extended without modifying tool implementation code
vs alternatives: More maintainable than manual parameter validation because Zod schemas serve as both validation logic and documentation, reducing the gap between spec and implementation
Provides a Dockerfile and Docker Compose configuration enabling the LINE Bot MCP Server to be containerized and deployed in Docker environments without requiring Node.js installation on the host. The Docker image includes Node.js v20+, installs dependencies via npm, and exposes the server via stdio for MCP client communication.
Unique: Provides both Dockerfile and Docker Compose templates, enabling both single-container deployments and multi-container orchestration without requiring users to write Docker configurations from scratch
vs alternatives: Simpler than manual Node.js installation and dependency management because Docker encapsulates all runtime requirements, reducing deployment friction and environment-specific issues
+2 more capabilities
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 Official Account at 22/100.
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