Why this server?
A Model Context Protocol (MCP) server that provides programmatic access to the Supabase Management API. This server allows AI models and other clients to manage Supabase projects and organizations through a standardized interface.
Why this server?
This is an MCP server for PostgREST. It allows LLMs perform database queries and operations on Postgres databases via PostgREST. This server works with both Supabase projects (which use PostgREST) and standalone PostgREST servers.
Why this server?
A TypeScript-based server that implements a simple notes system, enabling users to create and manage text notes and generate summaries, showcasing core MCP concepts.
Why this server?
A server that implements a checklist management system with features like task creation, progress tracking, data persistence, and item comments.
Why this server?
Provides an interface to access and manage JIRA data through the Model Context Protocol, offering features like relationship tracking, data cleaning, and contextual insights for AI applications.
Why this server?
Enables seamless integration with Flowise via the Model Context Protocol (MCP) for creating, calling, and retrieving information about chat flows and predictions.
Why this server?
A robust SSH server facilitating secure remote command execution with TMUX session management, multi-window support, and smart session recovery for improved AI-human interaction.
Why this server?
Browse, list, and edit filesystem. Implemented in Java/Quarkus with native image (Fast!) available
Why this server?
Enables integration with Todoist for natural language task management, supporting project and section organization, task creation, updating, completion, and deletion using everyday language.