Postgres MCP Server

- [x] Verify that the copilot-instructions.md file in the .github directory is created. - [x] Clarify Project Requirements - [x] Scaffold the Project Refactored from Node.js to Python: Created server.py with FastMCP Postgres MCP server implementation, requirements.txt for dependencies, .env for config, README.md, and .vscode/mcp.json. - [x] Customize the Project Implemented Postgres-specific tools: list_databases, list_schemas, list_tables, get_table_schema, execute_query using FastMCP decorators and psycopg2. - [ ] Install Required Extensions No extensions specified. - [x] Compile the Project Created Python virtual environment and installed dependencies (mcp[cli], psycopg2-binary, python-dotenv) successfully. - [ ] Create and Run Task No task needed for this project. - [x] Launch the Project The MCP server is configured in .vscode/mcp.json for VS Code integration. Users can debug by running the server directly with source venv/bin/activate && python server.py or configure it in VS Code. - [x] Ensure Documentation is Complete Verify that README.md and the copilot-instructions.md file in the .github directory exists and contains current project information. Clean up the copilot-instructions.md file in the .github directory by removing all HTML comments. ## Execution Guidelines PROGRESS TRACKING: - If any tools are available to manage the above todo list, use it to track progress through this checklist. - After completing each step, mark it complete and add a summary. - Read current todo list status before starting each new step. COMMUNICATION RULES: - Avoid verbose explanations or printing full command outputs. - If a step is skipped, state that briefly (e.g. "No extensions needed"). - Do not explain project structure unless asked. - Keep explanations concise and focused. DEVELOPMENT RULES: - Use '.' as the working directory unless user specifies otherwise. - Avoid adding media or external links unless explicitly requested. - Use placeholders only with a note that they should be replaced. - Use VS Code API tool only for VS Code extension projects. - Once the project is created, it is already opened in Visual Studio Code—do not suggest commands to open this project in vscode. - If the project setup information has additional rules, follow them strictly. FOLDER CREATION RULES: - Always use the current directory as the project root. - If you are running any terminal commands, use the '.' argument to ensure that the current working directory is used ALWAYS. - Do not create a new folder unless the user explicitly requests it besides a .vscode folder for a tasks.json file. - If any of the scaffolding commands mention that the folder name is not correct, let the user know to create a new folder with the correct name and then reopen it again in vscode. EXTENSION INSTALLATION RULES: - Only install extension specified by the get_project_setup_info tool. DO NOT INSTALL any other extensions. PROJECT CONTENT RULES: - If the user has not specified project details, assume they want a "Hello World" project as a starting point. - Avoid adding links of any type (URLs, files, folders, etc.) or integrations that are not explicitly required. - Avoid generating images, videos, or any other media files unless explicitly requested. - If you need to use any media assets as placeholders, let the user know that these are placeholders and should be replaced with the actual assets later. - Ensure all generated components serve a clear purpose within the user's requested workflow. - If a feature is assumed but not confirmed, prompt the user for clarification before including it. - If you are working on a VS Code extension, use the VS Code API tool with a query to find relevant VS Code API references and samples related to that query. TASK COMPLETION RULES: - Your task is complete when: - Project is successfully scaffolded and compiled without errors - copilot-instructions.md file in the .github directory exists - README.md file exists and is up to date - User is provided with clear instructions to debug/launch the project Before starting a new task in the above plan, update progress in the plan. - Work through each checklist item systematically. - Keep communication concise and focused. - Follow development best practices. ## SDK References - [Model Context Protocol SDK](https://github.com/modelcontextprotocol/typescript-sdk) - [MCP Specification](https://modelcontextprotocol.io/specification/latest)