MCP server configs — stdio, SSE, HTTP

The three transport types side by side. stdio runs a local process; SSE connects to a hosted server (often OAuth); HTTP hits a REST endpoint with header auth. All secrets via ${ENV_VAR} expansion.

Parameters

Parameter	What to supply
`${GITHUB_TOKEN} etc.`	expanded from your shell environment at server start

The artifact

{
  "mcpServers": {
    "postgres-local": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-postgres",
               "postgresql://localhost/mydb"],
      "env": { "PGPASSWORD": "${PGPASSWORD}" }
    },
    "asana-hosted": {
      "type": "sse",
      "url": "https://mcp.asana.com/sse"
    },
    "internal-api": {
      "type": "http",
      "url": "https://api.example.com/mcp",
      "headers": {
        "Authorization": "Bearer ${INTERNAL_API_KEY}"
      }
    }
  }
}