feat: automatic project detection and enhanced authentication

- Add automatic Supabase project detection from working directory
  - Scan .env, .env.local, .supabase/config.toml, .supabase/.env files
  - Support framework-specific variables (Next.js, React, Vite)
  - Priority-based configuration resolution system
  - Extract project credentials and auto-switch context

- Enhance personal access token detection
  - Auto-detect from ~/.supabase/access-token (CLI integration)
  - Support multiple token file formats and locations
  - Seamless integration with `supabase login` workflow
  - Smart fallback chain for token resolution

- Implement dual authentication modes
  - personal-token: Management API with personal access tokens
  - project-keys: Project-specific anon/service keys when available
  - Automatic mode switching based on available credentials

- Update platform integration
  - Enhanced API platform to use project context
  - Project-specific URL and key resolution
  - Improved fallback handling for missing credentials

- Add comprehensive test suite
  - Unit tests for project context detection
  - Enhanced authentication flow testing
  - Config file parsing and validation tests

- Update documentation and examples
  - README with automatic detection features
  - CHANGELOG with detailed feature descriptions
  - Enhanced Claude CLI integration guide

Author: ringo380

.vscode/settings.json

@@ -5,4 +5,4 @@
   "[json]": {
     "editor.defaultFormatter": "biomejs.biome"
   }
-}
+}

AGENTS.md

@@ -0,0 +1,24 @@
+# Repository Guidelines
+
+## Project Structure & Module Organization
+The pnpm workspace centers on `packages/mcp-server-supabase` (production MCP server) and `packages/mcp-utils` (shared schemas, validation, and helpers). An experimental `mcp-server-postgrest` lives alongside them for targeted pilots. Runtime code stays under each package’s `src/`; Vitest fixtures sit in sibling `test/` folders. Top-level `docs/` holds integration guides, `scripts/` provides registry and release automation, and `supabase/` contains migrations plus seed data consumed by integration suites.
+
+## Build, Test, and Development Commands
+- `pnpm install` — install workspace dependencies.
+- `pnpm build` — run `tsup` builds for utils and the Supabase server.
+- `pnpm --filter @supabase/mcp-server-supabase dev` — watch-and-rebuild while coding.
+- `pnpm test` — execute all Vitest projects in parallel.
+- `pnpm test:coverage` — collect coverage for the Supabase server.
+- `pnpm format` / `pnpm format:check` — apply or verify Biome formatting.
+
+## Coding Style & Naming Conventions
+Code is TypeScript-first, strict ESM, and two-space indented. Favor named exports; map filesystem names to camelCase exports (see `src/tools`). Generated OpenAPI artifacts belong under `src/management-api/`. Biome is the source of truth for formatting, linting, and import order—run it before committing. `tsup.config.ts` already targets both ESM and CJS outputs; keep new entrypoints consistent with existing build targets.
+
+## Testing Guidelines
+Vitest drives unit, integration, and e2e suites configured in `vitest.workspace.ts`. Use package-scoped scripts (`pnpm test:unit`, `test:integration`, `test:e2e`) for faster iteration. Integration flows expect the seeded Supabase instance; refresh with `supabase db reset` when fixtures drift. Place new tests beside the modules they cover, naming files `*.test.ts`, and assert on concrete Supabase responses where possible instead of broad snapshots.
+
+## Commit & Pull Request Guidelines
+Follow Conventional Commits (`feat:`, `fix:`, `chore:`) and collapse WIP history before raising a PR. Reference Supabase issues or MCP registry tickets when applicable. PR descriptions should outline behaviour changes, highlight tooling updates, and mention any Supabase config required for reviewers. Confirm `pnpm build`, `pnpm test`, and `pnpm format:check` pass locally, and attach CLI output for non-obvious failures or regressions.
+
+## Security & Configuration Tips
+Store `SUPABASE_ACCESS_TOKEN` outside the repo (environment managers or MCP client secrets). Prefer `--read-only` and `--project-ref` flags when sharing demos, and scrub captured payloads before committing fixtures or docs.

CLAUDE.md

@@ -0,0 +1,156 @@
+# CLAUDE.md
+
+This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+
+## Project Overview
+
+This is a monorepo containing MCP (Model Context Protocol) servers for Supabase integration. The project allows AI assistants like Claude to directly interact with Supabase projects through standardized tools.
+
+### Repository Structure
+
+- `packages/mcp-server-supabase/` - Main MCP server providing Supabase management tools
+- `packages/mcp-server-postgrest/` - PostgREST-specific MCP server for REST API interactions
+- `packages/mcp-utils/` - Shared utilities for building MCP servers
+
+## Development Commands
+
+### Installation
+```bash
+pnpm install
+```
+
+### Building
+```bash
+# Build all packages
+pnpm build
+
+# Build specific package
+pnpm --filter @supabase/mcp-server-supabase build
+```
+
+### Development
+```bash
+# Watch mode for main server
+cd packages/mcp-server-supabase
+pnpm dev
+```
+
+### Testing
+```bash
+# Run all tests
+pnpm test
+
+# Run tests with coverage
+pnpm test:coverage
+
+# Run specific test types for main package
+pnpm --filter @supabase/mcp-server-supabase test:unit
+pnpm --filter @supabase/mcp-server-supabase test:e2e
+pnpm --filter @supabase/mcp-server-supabase test:integration
+```
+
+### Linting & Formatting
+```bash
+# Format code (using Biome)
+pnpm format
+
+# Check formatting
+pnpm format:check
+```
+
+### Type Checking
+```bash
+# Type check main server
+cd packages/mcp-server-supabase
+pnpm typecheck
+```
+
+## Architecture
+
+### MCP Server Architecture
+
+The main server (`packages/mcp-server-supabase/`) follows a modular tool-based architecture:
+
+- **Platform Interface** (`src/platform/`): Defines operations interface that different platform implementations can fulfill
+- **Authentication System** (`src/auth.ts`, `src/config/`): Enhanced dual-mode authentication with automatic project detection
+- **Tool Groups** (`src/tools/`): Organized by feature area:
+  - `account-tools.ts` - Project and organization management
+  - `database-operation-tools.ts` - SQL execution and migrations
+  - `development-tools.ts` - API keys, URLs, TypeScript type generation
+  - `debugging-tools.ts` - Logs and performance advisors
+  - `edge-function-tools.ts` - Edge Function deployment and management
+  - `storage-tools.ts` - Storage bucket and config management
+  - `branching-tools.ts` - Development branch operations
+  - `docs-tools.ts` - Documentation search
+
+### Authentication Features (NEW)
+
+The server now includes comprehensive authentication enhancements:
+
+- **Automatic Project Detection** (`src/config/project-context.ts`):
+  - Scans current working directory for Supabase configuration
+  - Supports `.env`, `.env.local`, `.supabase/config.toml`, `.supabase/.env`
+  - Framework-specific variable naming (Next.js, React, Vite)
+  - Priority-based configuration resolution
+
+- **Enhanced Token Detection** (`src/config/supabase-config.ts`):
+  - Automatic detection from `~/.supabase/access-token` (CLI integration)
+  - Support for multiple token file formats and locations
+  - Seamless integration with `supabase login` workflow
+
+- **Dual Authentication Modes** (`src/auth.ts`):
+  - `personal-token`: Uses management API with personal access tokens
+  - `project-keys`: Uses project-specific anon/service keys when available
+  - Automatic switching based on available credentials
+
+- **Smart Fallback Chain**:
+  1. CLI flags (--project-ref)
+  2. Environment variables (SUPABASE_ACCESS_TOKEN)
+  3. Project context from working directory
+  4. Config files (~/.supabase/access-token)
+  5. None (graceful degradation)
+
+### Feature System
+
+The server uses a feature group system allowing selective tool enablement:
+- `--features=database,docs` enables only database and docs tools
+- Default groups: `account`, `database`, `debugging`, `development`, `docs`, `functions`, `branching`
+- Storage tools are disabled by default to reduce tool count
+
+### Platform Independence
+
+Core functionality is separated into platform-specific implementations through the `SupabasePlatform` interface, allowing different backends (API-based, local, etc.) while maintaining the same tool interface.
+
+## Key Dependencies
+
+- **pnpm** (v10.15.0) - Package manager
+- **Node.js** 22.18.0 (see `.nvmrc`)
+- **Vitest** - Testing framework with unit/e2e/integration test separation
+- **Biome** - Formatting and linting
+- **tsup** - TypeScript bundling
+- **Zod** - Runtime type validation and schema definition
+
+## Testing Strategy
+
+- **Unit tests**: `src/**/*.test.ts` - Component testing with 30s timeout for PGlite initialization
+- **E2E tests**: `test/e2e/**/*.e2e.ts` - End-to-end flows with 60s timeout
+- **Integration tests**: `test/**/*.integration.ts` - Integration testing
+- Uses Vitest workspace for parallel execution of different test types
+- Custom text loader plugin for SQL files
+- MSW for API mocking
+
+## Registry Publishing
+
+The main server is published to the official MCP registry:
+
+1. Update version in `packages/mcp-server-supabase/package.json`
+2. Run `pnpm registry:update` to update `server.json`
+3. Login with `pnpm registry:login`
+4. Publish with `pnpm registry:publish`
+
+## Development Configuration
+
+- Local development uses `file:` protocol for MCP client testing
+- Server exposes both ES modules and CommonJS builds
+- Multiple entry points for platform-specific usage
+- Uses TypeScript with `@total-typescript/tsconfig` for strict configuration