Neon

This tool:
1. Applies suggested changes (like creating indexes) to the main branch (or specified branch) if approved
2. Handles cleanup of temporary branch
3. Must be called even when changes are rejected to ensure proper cleanup

Workflow:
1. After 'prepare_query_tuning' suggests changes
2. User reviews and approves/rejects changes
3. This tool is called to either:
  - Apply approved changes to main branch and cleanup
  - OR just cleanup if changes are rejected

Supported operations:
CREATE operations:
- Add new columns (e.g., "Add email column to users table")
- Create new tables (e.g., "Create posts table with title and content columns")
- Add constraints (e.g., "Add unique constraint on users.email")

ALTER operations:
- Modify column types (e.g., "Change posts.views to bigint")
- Rename columns (e.g., "Rename user_name to username in users table")
- Add/modify indexes (e.g., "Add index on posts.title")
- Add/modify foreign keys (e.g., "Add foreign key from posts.user_id to users.id")

DROP operations:
- Remove columns (e.g., "Drop temporary_field from users table")
- Drop tables (e.g., "Drop the old_logs table")
- Remove constraints (e.g., "Remove unique constraint from posts.slug")

The tool will:
1. Parse your natural language request
2. Generate appropriate SQL
3. Execute in a temporary branch for safety
4. Verify the changes before applying to main branch

Project ID and database name will be automatically extracted from your request.
If the database name is not provided, the default neondb or first available database is used.

You should test it with:
SELECT column_name, data_type 
FROM information_schema.columns 
WHERE table_name = 'users' AND column_name = 'last_login';

You can use 'run_sql' to test the migration in the temporary branch that this
tool creates.

  <response_instructions>
    <instructions>
      Provide a brief confirmation of the requested change and ask for migration commit approval.

      You MUST include ALL of the following fields in your response:
      - Migration ID (this is required for commit and must be shown first)  
      - Temporary Branch Name (always include exact branch name)
      - Temporary Branch ID (always include exact ID)
      - Migration Result (include brief success/failure status)

      Even if some fields are missing from the tool's response, use placeholders like "not provided" rather than omitting fields.
    </instructions>

    <do_not_include>
      IMPORTANT: Your response MUST NOT contain ANY technical implementation details such as:
      - Data types (e.g., DO NOT mention if a column is boolean, varchar, timestamp, etc.)
      - Column specifications or properties
      - SQL syntax or statements
      - Constraint definitions or rules
      - Default values
      - Index types
      - Foreign key specifications

      Keep the response focused ONLY on confirming the high-level change and requesting approval.

      <example>
        INCORRECT: "I've added a boolean is_published column to the posts table..."
        CORRECT: "I've added the is_published column to the posts table..."
      </example>
    </do_not_include>

    <example>
      I've verified that [requested change] has been successfully applied to a temporary branch. Would you like to commit the migration [migration_id] to the main branch?

      Migration Details:
      - Migration ID (required for commit)
      - Temporary Branch Name
      - Temporary Branch ID
      - Migration Result
    </example>
  </response_instructions>

3. If approved, use 'complete_database_migration' tool with the migration_id

Error response will include:
- Original error details
- Confirmation that retry was attempted
- Final error state

Important: After a failed retry, you must terminate the current flow completely. Do not attempt to use alternative tools or workarounds.

The tool will:
1. Create a temporary branch for testing optimizations and remember the branch ID
2. Extract and analyze the current query execution plan
3. Extract all fully qualified table names (schema.table) referenced in the plan 
4. Gather detailed schema information for each referenced table using describe_table_schema
5. Suggest and implement improvements like:
  - Adding or modifying indexes based on table schemas and query patterns
  - Query structure modifications
  - Identifying potential performance bottlenecks
6. Apply the changes to the temporary branch using run_sql
7. Compare performance before and after changes (but ONLY on the temporary branch passing branch ID to all tools)
8. Continue with next steps using complete_query_tuning tool (on main branch)

Project ID and database name will be automatically extracted from your request.
The temporary branch ID will be added when invoking other tools.
Default database is neondb if not specified.

IMPORTANT: This tool is part of the query tuning workflow. Any suggested changes (like creating indexes) must first be applied to the temporary branch using the 'run_sql' tool.
and then to the main branch using the 'complete_query_tuning' tool, NOT the 'prepare_database_migration' tool. 
To apply using the 'complete_query_tuning' tool, you must pass the tuning_id, NOT the temporary branch ID to it.

DO NOT use 'prepare_database_migration' tool for applying query tuning changes.
Always use 'complete_query_tuning' to ensure changes are properly tracked and applied.

Note: 
- Some operations like creating indexes can take significant time on large tables
- Table statistics updates (ANALYZE) are NOT automatically performed as they can be long-running
- Table statistics maintenance should be handled by PostgreSQL auto-analyze or scheduled maintenance jobs
- If statistics are suspected to be stale, suggest running ANALYZE as a separate maintenance task

The tool will:
1. Extract referenced tables: public.orders, public.customers
2. Gather schema information for both tables
3. Analyze the execution plan
4. Suggest improvements like:
   - Creating a composite index on orders(status, created_at)
   - Optimizing the join conditions
5. If confirmed, apply the suggested changes to the temporary branch using run_sql
6. Compare execution plans and performance before and after changes (but ONLY on the temporary branch passing branch ID to all tools)

  <response_instructions>
    <instructions>
      Provide a brief summary of the performance analysis and ask for approval to apply changes on the temporary branch.

      You MUST include ALL of the following fields in your response:
      - Tuning ID (this is required for completion)
      - Temporary Branch Name
      - Temporary Branch ID
      - Original Query Cost
      - Improved Query Cost
      - Referenced Tables (list all tables found in the plan)
      - Suggested Changes

      Even if some fields are missing from the tool's response, use placeholders like "not provided" rather than omitting fields.
    </instructions>

    <do_not_include>
      IMPORTANT: Your response MUST NOT contain ANY technical implementation details such as:
      - Exact index definitions
      - Internal PostgreSQL settings
      - Complex query rewrites
      - Table partitioning details

      Keep the response focused on high-level changes and performance metrics.
    </do_not_include>

    <example>
      I've analyzed your query and found potential improvements that could reduce execution time by [X]%.
      Would you like to apply these changes to improve performance?

      Analysis Details:
      - Tuning ID: [id]
      - Temporary Branch: [name]
      - Branch ID: [id]
      - Original Cost: [cost]
      - Improved Cost: [cost]
      - Referenced Tables:
        * public.orders
        * public.customers
      - Suggested Changes:
        * Add index for frequently filtered columns
        * Optimize join conditions

      To apply these changes, I will use the 'complete_query_tuning' tool after your approval and pass the tuning_id, NOT the temporary branch ID to it.
    </example>
  </response_instructions>

3. If approved, use ONLY the 'complete_query_tuning' tool with the tuning_id

Error response will include:
- Original error details
- Confirmation that retry was attempted
- Final error state

Important: After a failed retry, you must terminate the current flow completely.

Parameters:
- <project_id>: The Project ID of the Neon project to provision authentication for.
- [database]: The database name to setup Neon Auth for. If not provided, the default neondb or first available database is used.

The tool will:
  1. Establish a connection between your Neon Auth project and Stack Auth
  2. Creates a dedicated authentication schema in your database ("neon_auth")
  3. Sets up the user table under the "neon_auth" schema. This table is synced with Stack Auth. It does not store user credentials or secrets.
  4. Generates Client Key and Secret Key to connect your application with authentication provider.

Use the Stack Auth SDK (@stackframe/stack) on the frontend to connect your application with authentication provider. DO NOT use NextAuth.js! DO NOT use better-auth! Here's some documentation on Stack Auth:

# Stack Auth Guidelines

## Setup Guidelines
  If you're building an app with Next.js, to set up Neon Auth and Stack Auth, follow these steps:
  1. Provision a Neon Auth project with this tool
  2. Place the returned credentials in project's `.env.local` or `.env` file
    - `NEXT_PUBLIC_STACK_PROJECT_ID`
    - `NEXT_PUBLIC_STACK_PUBLISHABLE_CLIENT_KEY`
    - `STACK_SECRET_SERVER_KEY`
  3. To setup Stack Auth, run following command: 
    ```bash
    npx @stackframe/init-stack . --no-browser 
    ```
    This command will automaticallysetup the project with - 
    - It will add `@stackframe/stack` dependency to `package.json`
    - It will create a `stack.ts` file in your project to setup `StackServerApp`. 
    - It will wrap the root layout with `StackProvider` and `StackTheme`
    - It will create root Suspense boundary `app/loading.tsx` to handle loading state while Stack is fetching user data.
    - It will also create `app/handler/[...stack]/page.tsx` file to handle auth routes like sign in, sign up, forgot password, etc.
  4. Do not try to manually create any of these files or directories. Do not try to create SignIn, SignUp, or UserButton components manually, instead use the ones provided by `@stackframe/stack`.


## Components Guidelines
  - Use pre-built components from `@stackframe/stack` like `<UserButton />`, `<SignIn />`, and `<SignUp />` to quickly set up auth UI.
  - You can also compose smaller pieces like `<OAuthButtonGroup />`, `<MagicLinkSignIn />`, and `<CredentialSignIn />` for custom flows.
  - Example:

    ```tsx
    import { SignIn } from '@stackframe/stack';
    export default function Page() {
      return <SignIn />;
    }
    ```

## User Management Guidelines
  - In Client Components, use the `useUser()` hook to retrieve the current user (it returns `null` when not signed in).
  - Update user details using `user.update({...})` and sign out via `user.signOut()`.
  - For pages that require a user, call `useUser({ or: "redirect" })` so unauthorized visitors are automatically redirected.

## Client Component Guidelines
  - Client Components rely on hooks like `useUser()` and `useStackApp()`.
  - Example:

    ```tsx
    "use client";
    import { useUser } from "@stackframe/stack";
    export function MyComponent() {
      const user = useUser();
      return <div>{user ? `Hello, ${user.displayName}` : "Not logged in"}</div>;
    }
    ```

## Server Component Guidelines
  - For Server Components, use `stackServerApp.getUser()` from your `stack.ts` file.
  - Example:

    ```tsx
    import { stackServerApp } from "@/stack";
    export default async function ServerComponent() {
      const user = await stackServerApp.getUser();
      return <div>{user ? `Hello, ${user.displayName}` : "Not logged in"}</div>;
    }
    ```

## Page Protection Guidelines
  - Protect pages by:
    - Using `useUser({ or: "redirect" })` in Client Components.
    - Using `await stackServerApp.getUser({ or: "redirect" })` in Server Components.
    - Implementing middleware that checks for a user and redirects to `/handler/sign-in` if not found.
  - Example middleware:

    ```tsx
    export async function middleware(request: NextRequest) {
      const user = await stackServerApp.getUser();
      if (!user) {
        return NextResponse.redirect(new URL('/handler/sign-in', request.url));
      }
      return NextResponse.next();
    }
    export const config = { matcher: '/protected/:path*' };
    ```

  ```
  ## Examples
  ### Example: custom-profile-page
  #### Task
  Create a custom profile page that:
  - Displays the user's avatar, display name, and email.
  - Provides options to sign out.
  - Uses Stack Auth components and hooks.
  #### Response
  ##### File: app/profile/page.tsx
  ###### Code
  ```tsx
  'use client';
  import { useUser, useStackApp, UserButton } from '@stackframe/stack';
  export default function ProfilePage() {
    const user = useUser({ or: "redirect" });
    const app = useStackApp();
    return (
      <div>
        <UserButton />
        <h1>Welcome, {user.displayName || "User"}</h1>
        <p>Email: {user.primaryEmail}</p>
        <button onClick={() => user.signOut()}>Sign Out</button>
      </div>
    );
  }
  ```

<important_notes>
  If you have a temporary branch from a prior step, you MUST:
  1. Pass the branch ID to this tool unless explicitly told otherwise
  2. Tell the user that you are using the temporary branch with ID [branch_id]
</important_notes>

<important_notes>
  If you have a temporary branch from a prior step, you MUST:
  1. Pass the branch ID to this tool unless explicitly told otherwise
  2. Tell the user that you are using the temporary branch with ID [branch_id]
</important_notes>

{
  "mcpServers": {
    "neon": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "NEON_API_KEY",
        "mcp/neon"
      ],
      "env": {
        "NEON_API_KEY": "YOUR_API_KEY_HERE"
      }
    }
  }
}