"MCP servers that work without API keys" matching MCP servers:

Enables interaction with MongoDB databases through CRUD operations, aggregation, and schema discovery, with automatic field validation and ObjectId conversion.

Enables recording, querying, and summarizing daily work entries with tags using a local SQLite database. Supports work logging, search, timeline queries, tag management, and automated reminders for tracking daily tasks.

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.

Monitor and manage Apache Airflow clusters through natural language queries via MCP tools: DAG inspection, task monitoring, health checks, and cluster analytics without API complexity. * Guide: https://call518.medium.com/mcp-airflow-api-a-model-context-protocol-mcp-server-for-apache-airflow-5dfdfb2

A server that allows AI agents to interact with the Tally API to access DAO governance data, proposals, and metadata using Model Context Protocol (MCP), built with TypeScript and GraphQL.

Enables interaction with a comprehensive healthcare management system through FastAPI, supporting operations for patients, doctors, appointments, medical records, telemedicine, lab orders, prescriptions, insurance claims, and more with JWT authentication.

MCP server that exposes book management tools for AI assistants, enabling CRUD operations on book collections through a .NET Books API backend.

Enables read-only access to curated Datum data platform marts, including products, resources, consensus questions, and health metrics, through MCP tools such as list_products, list_questions, ask, query, and health.

Enables AI agents to safely interact with Supabase through read-only and gated-write tools, with bounded queries, allowlists, and explicit project targeting.

A public MCP server demonstrating how an AI agent can retrieve database schemas and manage local OpenAPI contracts via tools for CRUD operations.

A Model Context Protocol server that enables Claude and other MCP-compatible AI assistants to securely access and manage PI Dashboard resources including categories and charts.

Facilitates secure and type-safe interactions with both v1 and v2 of the Glide API, allowing users to manage app data and perform CRUD operations on tables via a Model Context Protocol interface.

Enables interaction with FHIR resources on Google Cloud Healthcare API through a SmartOnFHIR gateway secured by Firebase Auth, providing access to patient data, medical records, and medical research tools like PubMed.

Enables AI assistants to discover and invoke CRUD tools and read-only resources over the Model Context Protocol for generated API services.

Exposes Django admin's ModelAdmin as MCP tools, with identical permissions, form validation, and session authentication.

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.

Exposes every generated CRUD service to LLM clients such as Claude, ChatGPT, or Cursor through discoverable MCP tools for create, update, and list actions plus read-only resources, so models can query and manipulate data without raw HTTP calls. It runs alongside the same codebase's REST endpoints, letting clients and AI share one data layer.

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 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 invoke CRUD tools and read-only resources for generated services, allowing direct interaction with the same data exposed by the REST API.