agentleFS
neondatabaseneondatabase/mcp-server-neon/public/llms.txt

mcp-server-neon

llms.txt652 starsChanged 3 months agoMITView on GitHub

Connect AI tools to Lakebase Postgres databases on Neon using the Model Context Protocol (MCP). The Neon MCP Server enables Large Language Models to manage Lakebase Postgres databases on Neon through natural language commands. It implements the Model Context Protocol specification for seamless AI integration.

We split this llms.txt into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create and manage Neon projects, branches, and databases

    line 9
  2. Distinctive:

    Run SQL queries and migrations

    line 10

≈ “Common” is an estimate: at least 1 in 5 of the 3,225 llms.txt files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
llms.txt
# Neon MCP Server

> Connect AI tools to Lakebase Postgres databases on Neon using the Model Context Protocol (MCP).

The Neon MCP Server enables Large Language Models to manage Lakebase Postgres databases on Neon through natural language commands. It implements the Model Context Protocol specification for seamless AI integration.

## Capabilities

- Create and manage Neon projects, branches, and databases
- Run SQL queries and migrations
- Optimize query performance
- Manage database roles and permissions

## Integration

- **NPM Package**: @neondatabase/mcp-server-neon
- **Remote MCP**: Connect via https://mcp.neon.tech/sse
- **Docs-only (no auth)**: Connect via https://mcp.neon.tech/mcp?category=docs to use only the documentation tools (`list_docs_resources`, `get_doc_resource`) and `send_feedback` without an account or OAuth flow.

## Documentation

- Neon MCP Docs: https://neon.com/docs/ai/neon-mcp-server
- MCP Protocol: https://modelcontextprotocol.io

## Contact

- Website: https://neon.tech
- GitHub: https://github.com/neondatabase/mcp-server-neon

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.