mirror of
https://github.com/domfelipe/vibeflow-n8n.git
synced 2026-08-07 11:56:49 +00:00
feat: launch Vibeflow n8n v0.5.0
This commit is contained in:
commit
097f35215f
60 changed files with 2831 additions and 0 deletions
28
clients/codex/README.md
Normal file
28
clients/codex/README.md
Normal file
|
|
@ -0,0 +1,28 @@
|
|||
# Codex CLI
|
||||
|
||||
## Goal
|
||||
|
||||
Use Vibeflow n8n with Codex CLI as the behavior layer that guides intake, planning, build, validation, and final reporting.
|
||||
|
||||
## Recommended setup idea
|
||||
|
||||
- connect Codex CLI to the n8n MCP server
|
||||
- load the core prompt from `templates/system-prompt.md`
|
||||
- optionally keep `docs/skill-spec.md` and `docs/conversation-contract.md` in the working directory for extra context
|
||||
|
||||
## Suggested working pattern
|
||||
|
||||
1. Start Codex in a project folder that contains this repository.
|
||||
2. Ensure MCP access to n8n is configured.
|
||||
3. Ask for a workflow in natural language.
|
||||
4. Let the agent ask a few focused questions.
|
||||
5. Review the plan.
|
||||
6. Approve the build.
|
||||
|
||||
## Helpful prompt seed
|
||||
|
||||
```text
|
||||
Use the Vibeflow n8n skill in this repository. Interview me briefly, produce a build plan, then create the workflow in n8n through MCP and return a final handoff report.
|
||||
```
|
||||
|
||||
See `config-snippets.md` for example `codex mcp add` and `config.toml` setup.
|
||||
31
clients/codex/config-snippets.md
Normal file
31
clients/codex/config-snippets.md
Normal file
|
|
@ -0,0 +1,31 @@
|
|||
# Codex CLI config snippets
|
||||
|
||||
These snippets are examples. Replace placeholder URLs and names with your real n8n MCP configuration.
|
||||
|
||||
## Option 1: add with CLI
|
||||
|
||||
```bash
|
||||
codex mcp add n8n --url https://YOUR-N8N-MCP-ENDPOINT
|
||||
codex mcp list
|
||||
```
|
||||
|
||||
## Option 2: add in config file
|
||||
|
||||
Project-scoped or user-scoped configuration can live in `~/.codex/config.toml` or `.codex/config.toml`.
|
||||
|
||||
```toml
|
||||
[mcp_servers.n8n]
|
||||
url = "https://YOUR-N8N-MCP-ENDPOINT"
|
||||
```
|
||||
|
||||
## Optional instruction in AGENTS.md
|
||||
|
||||
```text
|
||||
Always use the n8n MCP server when the request is about creating, updating, validating, or testing n8n workflows. Before building anything, produce a normalized plan that matches schemas/plan.schema.json.
|
||||
```
|
||||
|
||||
## Suggested first prompt
|
||||
|
||||
```text
|
||||
Use the Vibeflow n8n skill in this repository. Interview me briefly, produce a normalized plan, then build the workflow in n8n through MCP and finish with a concise handoff report.
|
||||
```
|
||||
10
clients/codex/sample-config.toml
Normal file
10
clients/codex/sample-config.toml
Normal file
|
|
@ -0,0 +1,10 @@
|
|||
# Example Codex CLI MCP configuration
|
||||
# Adjust command, args, and environment to match your local n8n MCP setup.
|
||||
|
||||
[mcp_servers.n8n]
|
||||
command = "npx"
|
||||
args = ["-y", "n8n-mcp"]
|
||||
|
||||
[mcp_servers.n8n.env]
|
||||
N8N_BASE_URL = "http://localhost:5678"
|
||||
N8N_API_KEY = "replace-me"
|
||||
Loading…
Add table
Add a link
Reference in a new issue