# MCP Servers for AI Builders: Maintainer and Reference Projects

> Inspect seven MCP server projects for repositories, browsers, databases, local files and infrastructure, with permission boundaries and a CSV export.

- Source: https://www.zarifautomates.com/blog/mcp-servers-for-ai-builders
- Published: 2026-09-17
- Updated: 2026-09-17
- Pillar: Sources & Directories
- Tags: ai-engineering, directory, builders
- Author: Zarif

---

An MCP server exposes capabilities to a compatible client. It does not decide whether a proposed action is appropriate for your project. This directory covers seven maintainer and reference projects whose code or documentation you can inspect. It is a selection by use case, not a security certification.

Last verified 2026-09-17. Recheck target: monthly. Download: https://www.zarifautomates.com/downloads/directories/mcp-servers-for-ai-builders.csv.

## Start with five

1. [GitHub MCP Server](https://github.com/github/github-mcp-server) — Review release notes and enabled toolsets before upgrading. GitHub's maintained server connects repository, issue and pull-request workflows. Start with read-only access and enable only the toolsets and repositories the task needs.
2. [Playwright MCP](https://github.com/microsoft/playwright-mcp) — Review release notes and browser permissions before upgrading. Useful for inspecting and interacting with web applications through Playwright. Browser control can submit forms and expose signed-in data; use a dedicated task context.
3. [Context7](https://github.com/upstash/context7) — Check supported documentation and project releases. Use Upstash's project to retrieve documentation for a named library and version. Verify that retrieved examples match the dependency actually installed in your project.
4. [Supabase MCP](https://github.com/supabase/mcp) — Review hosted-service docs, permissions and package releases. Useful for inspecting a Supabase project’s schema and data. Begin with one project, read-only queries and the database/docs tool groups; the available account and deployment tools depend on the chosen scope.
5. [MCP Filesystem reference server](https://github.com/modelcontextprotocol/servers/tree/main/src/filesystem) — Pin the filesystem package and review path/permission changes. Use it to inspect a concrete MCP implementation for file reads and writes. Restrict the allowed directories and mount read-only fixtures for an initial test; this is a reference implementation, not a managed storage service.

## The directory

| Name | Role | Why it is here | Cadence |
| --- | --- | --- | --- |
| [GitHub MCP Server](https://github.com/github/github-mcp-server) | Repository and collaboration tools | GitHub's maintained server connects repository, issue and pull-request workflows. Start with read-only access and enable only the toolsets and repositories the task needs. README inspected at commit 85598ba6e125; the repository was not archived when checked. The activity date is the default branch commit timestamp, not a release date or a reproduced integration test. [Source checked 2026-09-17](https://github.com/github/github-mcp-server/blob/85598ba6e1256f7ebf4867b95d63b833c4549264/README.md); recorded activity 2026-09-16. | Review release notes and enabled toolsets before upgrading |
| [Playwright MCP](https://github.com/microsoft/playwright-mcp) | Browser interaction | Useful for inspecting and interacting with web applications through Playwright. Browser control can submit forms and expose signed-in data; use a dedicated task context. README inspected at commit ea43eee0d951; the repository was not archived when checked. The activity date is the default branch commit timestamp, not a release date or a reproduced integration test. [Source checked 2026-09-17](https://github.com/microsoft/playwright-mcp/blob/ea43eee0d95196ab31f7619b26f78d7b9c664286/README.md); recorded activity 2026-09-17. | Review release notes and browser permissions before upgrading |
| [Chrome DevTools MCP](https://github.com/ChromeDevTools/chrome-devtools-mcp) | Browser diagnostics | Use the Chrome team's project for browser debugging and performance inspection. Treat page contents, console output and network details as potentially sensitive. README inspected at commit 23b9a480010d; the repository was not archived when checked. The activity date is the default branch commit timestamp, not a release date or a reproduced integration test. [Source checked 2026-09-17](https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/23b9a480010d803fc8962bb5d11017b1e2ad76b2/README.md); recorded activity 2026-09-17. | Check current tools, browser requirements and release notes |
| [Context7](https://github.com/upstash/context7) | Library documentation retrieval | Use Upstash's project to retrieve documentation for a named library and version. Verify that retrieved examples match the dependency actually installed in your project. README inspected at commit dedb03d589e6; the repository was not archived when checked. The activity date is the default branch commit timestamp, not a release date or a reproduced integration test. [Source checked 2026-09-17](https://github.com/upstash/context7/blob/dedb03d589e6e03e8fb5a2b858bd3c853ac6893e/README.md); recorded activity 2026-09-17. | Check supported documentation and project releases |
| [Cloudflare MCP servers](https://github.com/cloudflare/mcp-server-cloudflare) | Cloudflare platform integrations | Choose the specific Cloudflare server and account scope needed for the task. Tools may read or change infrastructure; inspect each permission and action boundary. The pinned README separates domain-specific servers from the broader Code Mode server in cloudflare/mcp. It documents Streamable HTTP; /sse is a compatibility URL, not legacy HTTP+SSE support. Activity is the default-branch commit date. [Source checked 2026-09-17](https://github.com/cloudflare/mcp-server-cloudflare/blob/db9084730dd45ebb6ac4dd5d3181d189cc96e98d/README.md); recorded activity 2026-08-31. | Check maintained server endpoints and permission changes |
| [Supabase MCP](https://github.com/supabase/mcp) | Database and project inspection | Useful for inspecting a Supabase project’s schema and data. Begin with one project, read-only queries and the database/docs tool groups; the available account and deployment tools depend on the chosen scope. Official docs and the pinned README support project_ref, read_only=true and feature groups. The current maintainer repository is supabase/mcp. No database connection or query was performed. [Source checked 2026-09-17](https://github.com/supabase/mcp/blob/6c411e221ae2a44a9b2e905d04ea80d132edf9d2/README.md); recorded activity 2026-09-17. | Review hosted-service docs, permissions and package releases |
| [MCP Filesystem reference server](https://github.com/modelcontextprotocol/servers/tree/main/src/filesystem) | Local file operations and protocol examples | Use it to inspect a concrete MCP implementation for file reads and writes. Restrict the allowed directories and mount read-only fixtures for an initial test; this is a reference implementation, not a managed storage service. The MCP repository identifies this as a reference server. Its filesystem README describes allowed directories, reads and writes; tool hints alone are not filesystem access enforcement. The activity date belongs to the shared server repository. [Source checked 2026-09-17](https://github.com/modelcontextprotocol/servers/tree/d73f99efbfd40c3aa1b61e88728b3d49fb52608f/src/filesystem); recorded activity 2026-09-03. | Pin the filesystem package and review path/permission changes |

## Choose a server from the required action

For repository questions, inspect GitHub's available toolsets. For an interaction test, distinguish Playwright's browser actions from Chrome DevTools diagnostics. For a library API question, retrieve version-specific documentation through Context7. For infrastructure work, choose the particular Cloudflare service instead of granting broad account access by default.

For database inspection, [Supabase’s current setup guide](https://supabase.com/docs/guides/ai-tools/mcp) documents three separate controls: `project_ref` selects a project, `read_only=true` limits SQL access to read queries, and `features` restricts tool groups. Choosing a project is not the same as enabling read-only mode.

For local files, the Filesystem reference server uses allowed directories. Start with a small fixture directory that contains no secrets; use an operating-system read-only mount when the test should not write. A tool marked with a read-only hint is still a tool description, not an operating-system boundary.

Cloudflare’s maintainer README now distinguishes its broader Code Mode server from domain-specific servers for documentation, builds, observability and other services. Choose the capability you need. Older client configurations that expect legacy HTTP+SSE require a transport check even if the URL still ends in `/sse`.

## Before connecting a project

Read the maintainer's installation instructions, authentication method, supported transport and permissions. Pin a version where the distribution supports it and review changes before an upgrade. Begin with a disposable project or read-only scope and one concrete task.

A useful test checks more than whether a tool returns text: a denied operation should fail clearly; the tool should act on the intended repository or account; and the client should expose the proposed change before an irreversible action. Treat text returned from repositories, websites and documents as task data, not authority to expand the task.

The [official MCP registry](https://registry.modelcontextprotocol.io/) is another discovery source. Finding an entry there does not replace reading the maintainer, package and permission details. The [MCP architecture documentation](https://modelcontextprotocol.io/docs/learn/architecture) explains the host, client and server boundaries.

For the protocol introduction, read [what MCP is](/blog/what-is-model-context-protocol-mcp). For an application framework that consumes tools, use the [agent repository directory](/blog/best-ai-agent-repos-and-starter-templates).

## Change log

- 2026-09-17: Expanded to seven projects with database and local-file use cases. Checked pinned maintainer READMEs and clarified Cloudflare transport/server selection and Supabase project/read-only scoping.
- 2026-09-17: Initial selection of 5 primary-source entries, reviewed for identity and scope. Cadence describes how to recheck; no claim that every example was reproduced.

## Related Guides

- [AI Conferences and Meetups: Organizer Calendars for Builders](/blog/ai-conferences-and-meetups-for-builders)
- [AI YouTube Channels for Builders: Code, Systems and Technical Talks](/blog/ai-youtube-channels-for-builders)
- [AI Agent Benchmarks and Leaderboards: What Each Measures](/blog/ai-agent-benchmarks-and-leaderboards)