"A GitHub MCP server for browsing and understanding source code without requiring an API key" matching MCP servers:

Enables LLMs to discover and invoke generated API actions as MCP tools and read context through MCP resources for list and get-by-id operations. It provides HTTP-based MCP access for clients such as Cursor and Claude without extra glue code.

Enables LLMs to discover and use generated REST API services as Model Context Protocol tools and resources, supporting CRUD actions and read-only data access without custom glue code.

Enables AI assistants to interact directly with generated REST APIs by exposing CRUD operations as MCP tools and read-only data as resources.

Exposes generated CRUD services to LLM clients over the Model Context Protocol, providing tools for create, update, and delete actions plus read-only resources for listing and fetching records by id. It lets assistants like Claude, ChatGPT, and Cursor discover and manipulate the same data served by the project's REST endpoints without any extra glue code.

Enables LLMs to discover and invoke generated CRUD operations as MCP tools and read data through MCP resources, alongside standard REST endpoints, using one codebase.

Enables LLMs to discover and invoke generated CRUD tools and resources, allowing AI assistants to interact with the same data exposed by the REST API. Supports MCP clients such as Cursor and Claude over HTTP.

Enables LLMs and AI assistants to discover and use tools and resources for CRUD operations on generated services, providing direct interaction with the same data exposed by REST endpoints.

Multi-datasource MCP server that connects AI assistants to 6 database types (MySQL, PostgreSQL, ClickHouse, MongoDB, SQLite, Huawei DWS) with dynamic configuration, encrypted credential storage, and schema discovery.

Enables LLMs to discover and invoke CRUD tools and read-only resources for generated services, allowing direct interaction with the same data exposed by the REST API.

This MCP server provides secure access to databases for AI agents, enforcing authentication, authorization, human approval, logging, and notifications to prevent dangerous actions.

Enables LLMs to interact directly with generated REST services by discovering and invoking CRUD tools and reading exposed resources for list and get-by-id data.

It enables AI assistants to discover and invoke CRUD operations as MCP tools and read application data through MCP resources, allowing natural-language interaction with the generated backend.

It enables LLMs to interact with generated REST APIs by exposing CRUD operations as MCP tools and readable records as MCP resources. This lets AI clients discover and manage API data through the Model Context Protocol.

Enables LLMs to discover and invoke CRUD operations and read-only data resources for generated services through the Model Context Protocol, alongside traditional REST endpoints.

Read-only MySQL MCP server that lets AI agents list tables, describe schemas, and run SELECT/SHOW/EXPLAIN queries with a row cap, bound to a single database for safety.

An MCP server that caches your GitHub starred repositories in a local SQLite database and lets you search, list, and retrieve details about them through any MCP client (Claude Desktop, Cursor, VS Code, etc.), with automatic freshness checks via GitHub's ETag mechanism.

Enables AI assistants to interact with Databricks workspaces, running SQL queries, managing jobs, and exploring schemas via the Model Context Protocol.

MCP server that enables AI agents to read and write records in a live REST API generated from pasted data, with tools for listing, querying, inserting, updating, and deleting records.

Builds rich code graphs from TypeScript/NestJS codebases using AST analysis and Neo4j, enabling semantic search, natural language querying, and intelligent graph traversal to provide deep contextual understanding of code relationships and dependencies.

A safety-gated Python MCP server for Metabase that lets MCP clients and agents inspect Metabase, run governed queries, and create or maintain dashboards, cards/questions, collections, snippets, permissions, and other Metabase assets through the Metabase REST API.