gabogg/semillero-special-hotel
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: add n8n, git, and puppeteer mcp servers to workstation guide

Browse source
This commit is contained in:
Luis Gabriel Ramos Robles 2026-06-11 13:34:00 +00:00
parent 3f3a2148ce
commit 4f3da7e36e
1 changed files with 40 additions and 14 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

54
docs/AI_DEVELOPER_WORKSTATION.md
View file

@ -86,15 +86,30 @@ N8N_WEBHOOK_SECRET="prod_shared_signature_to_verify_n8n_callbacks"
## 2. Optimizing the Workspace for the Antigravity Agent (agy)
To make this codebase highly friendly for the **Antigravity agent (`agy`)**, you can configure the following Model Context Protocol (MCP) servers. Once registered in the agent's active configuration, `agy` is equipped to inspect database schemas, view live query states, and debug migrations during the development phase.
To make this codebase highly friendly for the **Antigravity agent (`agy`)**, you can configure the following Model Context Protocol (MCP) servers. Once registered in the agent's active configuration, `agy` is equipped with specialized tools to inspect database schemas, execute and debug n8n workflows, manage git versions, and run automated browser checks.
### 2.1. Recommended MCP Servers for agy
#### A. Prisma Postgres MCP Server (`@prisma/mcp`)
#### A. n8n MCP Server (Official Beta / Community)
Exposes tools to read, execute, and write workflows directly on the n8n canvas.
* **Use Case**: Allows `agy` to trigger calculation runs, inspect failing nodes on the canvas, check webhook logs, and modify workflows dynamically.
* **Harness Registration**:
```json
"n8n": {
"command": "npx",
"args": ["-y", "n8n-mcp"],
"env": {
"N8N_API_KEY": "your_n8n_api_key_here",
"N8N_URL": "http://localhost:5678"
}
}
```
#### B. Prisma Postgres MCP Server (`@prisma/mcp`)
Exposes tools allowing `agy` to interact with the database using type-safe schemas.
* **Use Case**: Allows `agy` to run schema checks, dry-run validations on schemas, and automatically inspect tables during development.
* **Use Case**: Allows `agy` to run schema checks, dry-run validations, and automatically inspect database tables during development.
* **Available Tools**: `ListDatabases`, `ExecuteSqlQuery`, `IntrospectSchema`, and `ExecuteRawSql`.
* **Harness Registration**: Add this to the active MCP server list for the `agy` agent session:
* **Harness Registration**:
```json
"prisma-postgres": {
"command": "npx",
@ -105,7 +120,7 @@ Exposes tools allowing `agy` to interact with the database using type-safe schem
}
```
#### B. PostgreSQL MCP Server (`@modelcontextprotocol/server-postgres`)
#### C. PostgreSQL MCP Server (`@modelcontextprotocol/server-postgres`)
Provides raw PostgreSQL connection and querying tools.
* **Use Case**: Enables `agy` to query migration status, seed verification, and raw audit log verification directly.
* **Harness Registration**:
@ -116,14 +131,25 @@ Provides raw PostgreSQL connection and querying tools.
}
```
---
#### D. Git MCP Server (`@modelcontextprotocol/server-git`)
Provides local Git operations tools (clone, commit, diff, log, status).
* **Use Case**: Allows `agy` to review local branches, examine diffs of modified code files, and make structured, micro-commits during development.
* **Harness Registration**:
```json
"git": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-git", "/home/gabogg/Proyects/semillero-special-hotel"]
}
```
## 3. IDE Rules & Agent Contexts (`.cursorrules` / `.clauderules`)
#### E. Puppeteer MCP Server (`@modelcontextprotocol/server-puppeteer`)
Exposes browser automation tools (take screenshots, click, type, fill forms).
* **Use Case**: Allows `agy` to start a headless browser, render our Next.js pages, and verify layout responsiveness and style details against the style guide without manual developer steps.
* **Harness Registration**:
```json
"puppeteer": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-puppeteer"]
}
```
Create a `.cursorrules` or `.clauderules` file in the root of the project. This guides the AI agent on architecture rules when editing files.
### 3.1. Standard Prompts for the Agent:
* **Prisma Rule**: Always run `npx prisma generate` after editing `schema.prisma`. All DB queries must utilize Prisma Client.
* **Styling Rule**: Do not use utility classes or TailwindCSS. Write Vanilla CSS in `<Component>.module.css` and import it as local styles. Follow CSS variables from `globals.css`.
* **Calculation Engine Rule**: The Next.js API only handles inputs, DB commits, and triggers. Do not write complex multi-step calculation loops inside Next.js; offload these to n8n triggers.
* **Auditing Rule**: Never write manually triggered audit logging. Use the `@explita/prisma-audit-log` client extension attached to the prisma instance.