"Using Supabase in Flutter applications" matching MCP servers:

A TypeScript server implementing the Model Context Protocol that provides secure code execution in isolated Docker containers, allowing LLM applications to safely run Python, Go, or JavaScript code snippets.

This project implements a simple MCP server in Go that exposes a single tool (create_short_link) to generate short URLs using the Rebrandly API.

Enables AI coding assistants to search and retrieve information from a locally ingested knowledge base using hybrid search, grounded in user-curated documentation.

An MCP server that enables AI applications to interact with DiceDB databases.

Deploy, manage, and scale applications directly from your AI assistant.

MCP server in Go to search and download books, papers, comics and more from Library Genesis — three focused tools, one static binary, no account required.

Production-grade MCP Gateway in Go featuring dynamic OpenAPI tool registration, RBAC governance, in-flight PII/DLP redaction, and structured JSON audit logging.

MCP server for GLEIF LEI (Legal Entity Identifier) database access. Look up, validate, and search legal entities and their relationships in the global LEI system.

MCP server for a self-hostable personal planner — exposes memo, todo, calendar event, and cross-resource full-text search tools so Claude, Cursor, or any MCP client can manage your schedule and notes in natural language.

Local CI/CD engine for AI agents. ActionD listens to LGH git events and runs plugin jobs (Go/Python/Java/web toolchains) in isolated checkouts, with structured results, root-cause failure diagnosis, approval gates, and auto-rollback. The MCP server exposes 23 tools, including dev_cycle_run (commit → CI → structured verdict in one call) and actiond_diagnose for failed-job analysis.

Local-first Microsoft Outlook MCP server: a single Go binary that manages calendar events and mail through the Microsoft Graph API over stdio, with tokens stored in the OS keychain and no Entra ID app registration required. Exposes four aggregate tools (calendar, mail, account, system) dispatched by an operation verb, with multi-account support and read-only and mail-gating modes.

Self-hostable, markdown-native team wiki with a built-in MCP server: agents search, read, and write your wiki pages (ranked Postgres full-text + semantic search, backlink traversal). Plus Atlas, which auto-generates a cited, coverage-checked wiki from your git repos and Jira.

Coordination for parallel coding agents: TTL file claims stored in the git common dir (visible across all worktrees), enforcement hooks that block colliding edits, agent presence, handoff notes, and a git-committed lessons knowledge base with BM25 search. Single static Go binary — no server, no database.

CI health reports for GitHub Actions: flaky tests named from logs, wasted compute priced in dollars, zombie crons, PR feedback time, plus 21 lint rules with safe auto-fixes. Read-only MCP tools wrap the same Go binary.

Fork, break, and revert real VirtualBox VMs as MCP tools; drive GUI-only guests through the hypervisor (screenshot, click, type, keys) with nothing installed in the guest. Windows host with VirtualBox.

A high-performance, multi-protocol API mock server with 18 built-in MCP tools for managing HTTP, GraphQL, gRPC, WebSocket, MQTT, SSE, and SOAP mocks, chaos engineering, stateful CRUD resources, and request verification.

Enables AI image generation and editing using Google's Gemini Multimodal Image APIs.

MCP server for Nordic company registries. Verify companies, check board members, signing authority, and financial data across Norway, Denmark, Finland, and Sweden using official public APIs. 23 tools covering search, details, roles, and batch lookups.

Decentralized Git with on-chain governance, bounties, and DAOs. Tools for repos, issues, PRs, labels, releases, bounties, and DAO proposals. Auto-wallet on first use, trust tiers, and approval mode for human-in-the-loop.

An MCP server that gives AI agents structured read/write access to a story-based project backlog. Agents can list stories, read content, update status, and append notes — all backed by plain markdown files that live inside your project repository. There is no shared server. The backlog files live in your repo under requirements/, committed and versioned alongside your code