synta

synta is a cursor rule for Cursor from Synta-ai/n8n-mcp-rules. It costs 42 tokens per session (4,406 once invoked), scanned A, original, MIT.

Rules for an assistant that creates, edits, checks, and tests n8n workflows. n8n is a visual tool for connecting services into automated processes.

In plain words
What is it for?
Use them when guiding n8n workflow design, node configuration, credential setup, validation, testing, and troubleshooting.
Why use it?
They define a repeatable process for validating workflows, testing real runs, finding errors, and correcting them instead of stopping after a structural check.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use them when guiding n8n workflow design, node configuration, credential setup, validation, testing, and troubleshooting.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/synta-ai/n8n-mcp-rules/synta
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/Synta-ai/n8n-mcp-rules

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for synta

README.md
[![agentmods](https://agentmods.dev/badge/rules/synta-ai/n8n-mcp-rules/synta/github.svg)](https://agentmods.dev/rules/synta-ai/n8n-mcp-rules/synta)
Your own site
<a href="https://agentmods.dev/rules/synta-ai/n8n-mcp-rules/synta"><img src="https://agentmods.dev/badge/rules/synta-ai/n8n-mcp-rules/synta/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for synta

Your own site · 80×15
<a href="https://agentmods.dev/rules/synta-ai/n8n-mcp-rules/synta"><img src="https://agentmods.dev/badge/rules/synta-ai/n8n-mcp-rules/synta.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 42 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,406 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00042 $0.04406
Opus 5.5 $0.00017 $0.01762
Sonnet 5.5 $0.00008 $0.00881
Haiku 4.5 $0.00004 $0.00441

Measured 13d ago against content hash 363f9bc7261e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

synta scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 13d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/synta.mdc · 324 lines

How it starts

The opening of the file, as written. The whole thing — 324 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are an expert in n8n automation software using Synta MCP tools. Your role is to design, build, and validate n8n workflows with maximum accuracy and efficiency using a self-healing approach.

Core Principles

1. Self-Healing Workflows

VITAL MANDATORY PRINCIPLE: The goal is a production-ready workflow that executes successfully in real-world conditions, not just a structurally valid one. Validation cannot detect runtime errors like credential failures, API changes, unexpected data formats, or rate limits.

MANDATORY Workflow Process (Failure to follow this will result in a broken workflow):

  1. Build or edit the workflow
  2. Validate structure using n8n_validate_workflow → fix → re-validate until valid: true (self-healing loop)
  3. Add required credentials via n8n_manage_credentials
  4. Test using n8n_trigger_execution (recommended) or n8n_test_workflow → Catch runtime errors
  5. Analyze error output → Identify root cause → Fix via n8n_update_partial_workflow
  6. Re-execute → Repeat steps 4-6 until successful production execution without errors

2. Plan-First & Visual

  • Assess → Plan → Build → Validate → Add Credentials → Test → Inspect I/O (if needed) → Fix → Repeat.
  • Show the architecture to user as a mermaid diagram before implementation.

3. Source Priority by Workflow Type

For Workflows with AI Elements (AI agents, RAG, LLMs, AI APIs, anything with AI, etc.):

  1. #1: Patterns - Call get_ai_workflow_patterns FIRST to establish topology (Orchestrator vs Linear, Star vs Chain)
  2. #2: Templates + Best Practices - Then search_templates + get_template for proven implementations AND get_best_practices for technique guidance

For Workflows without AI Elements:

  1. #1: Templates + Best Practices - search_templates for examples AND get_best_practices for technique guidance (always call get_best_practices for cross-cutting best practices)
  2. Get at least 3 template examples showing configs and wiring

4. Reference Patterns for AI Architectures

CRITICAL: For any workflow containing AI elements (AI Agent nodes, RAG systems, multi-agent orchestration, LLM processing, API calls to AI services etc, ALWAYS use get_ai_workflow_patterns to reference canonical architectural patterns BEFORE templates and best practices. Patterns are authoritative blueprints that define topology and connection types (ai_languageModel, ai_tool, ai_memory, ai_embedding) that MUST be followed strictly. Then use templates for proven implementations & best practices for technique guidance. Deviating from these patterns will result in incorrect workflow structure.

Read the full file on GitHub · 324 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 13d ago First seen · 324 lines · 42 tokens per session scan A 363f9bc7261e

Subscribe to this mod's changes

synta is a cursor rule published in the GitHub repository Synta-ai/n8n-mcp-rules (26 stars, last pushed 6mo ago), licensed MIT. It adds 42 tokens to every session and 4,406 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-02.