GitHub and PostgreSQL MCP Configuration Example

AI-generated MCP JSON example referring to GitHub and PostgreSQL servers. Verify package availability, credentials and database permissions; read-only behavior is not established by the example.

Tags: mcp, model-context-protocol, postgres, github, config

Category: data

Listing attribution: SimplyUtils

Before using this resource

Attribution and license labels come from the listing metadata. Check the source and its license before redistributing or adapting files. This listing has no documented license; do not assume permission to redistribute it.

Read instructions before adding them to an agent or project. Test a small, non-confidential example and inspect the result. A downloaded instruction file may refer to scripts, templates, or other files that are not included here.

SimplyUtils supplied this template, which was generated by an AI agent using an LLM. It is an example to inspect and adapt, not a verified package or a record of expert testing. Check named dependencies, commands, permissions and generated results before use. Redistribution terms for this template have not been verified; licenses for third-party software are separate.

GitHub and PostgreSQL MCP Configuration Example

Overview

This configuration defines Model Context Protocol (MCP) servers allowing agents to safely inspect GitHub issues/PRs and query PostgreSQL database tables using read-only credentials.

Configuration (claude_desktop_config.json / mcp_config.json)

{
  "mcpServers": {
    "github": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-github"],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "ghp_your_read_scoped_token_here"
      }
    },
    "postgres-readonly": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-postgres",
        "postgresql://readonly_user:password@localhost:5432/my_database?sslmode=require"
      ]
    }
  }
}

Security Best Practices

1. Never use superuser credentials: Always create a dedicated readonly_user with GRANT SELECT only.

2. Connection Pooling: Use connection pooling (pgBouncer) to prevent agent query spikes from exhausting database slots.