n8n-claw Skills

Skill catalog for n8n-claw MCP servers. Install pre-built API integrations with a single chat command — no coding required.

Available Skills (74)

Tested column — A ✓ in the Tested column means the skill has been verified end-to-end on at least one live n8n-claw instance (install + tool call working as expected). An empty cell means the skill is published but has not been hands-on verified yet.

Analytics

Calendar

Cloud Storage

CMS

Communication

Creativity

Developer Tools

E-commerce

Entertainment

Finance

Health & Fitness

Knowledge

Language

Maps

Marketing

Meetings

Network

News

Notes & CRM

Reference

Smart Home

Tasks

Tourism

Transport

Utilities

Weather

Usage

Skills are managed via chat with your n8n-claw agent:

"What skills are available?"        → lists all skills
"Install weather-openmeteo"         → installs the skill
"Remove weather-openmeteo"          → uninstalls and cleans up

Skills with API keys

Some skills require API credentials. When you install one, the agent sends you a secure one-time link (valid 10 minutes) to enter your API key via HTTPS form. Your key is never visible in the chat.

"Install news-newsapi"                → installs + sends credential link
"Add credential for news-newsapi"     → generates a new credential link

⚠️ Security notice — Skill credentials are stored in plain text

API keys entered via the credential form are currently stored unencrypted in the template_credentials table in PostgreSQL. This means:

• Anyone with access to the database can read all stored API keys
• Supabase Studio (localhost:3001, accessible via SSH tunnel) shows credentials in plain text
• A compromised VPS exposes all stored API keys

What an attacker would need: Neither the database nor the API are reachable from the internet. PostgREST runs on a Docker-internal network only, and PostgreSQL (port 5432) is bound to 127.0.0.1. To read credentials, an attacker would need SSH access to your VPS — there is no remote network path.

Mitigation: Secure SSH access (key-based auth, no root password, fail2ban), and use API keys with minimal permissions where possible.

Encryption at rest for skill credentials is planned and in progress.

Skills with infrastructure requirements

Some skills need additional services running alongside n8n:

Skill Types

Creating a Template

Directory structure

Each template lives in its own directory under templates/:

templates/
  index.json                  ← catalog (add your template here)
  my-template/
    manifest.json             ← metadata (name, tools, credentials)
    workflow.json             ← n8n workflow bundle (two workflows)
    README.md                 ← optional: usage notes

Step 1: Add to index.json

Add an entry to the templates array in templates/index.json:

{
  "id": "my-template",
  "name": "My Template",
  "type": "native",
  "category": "utilities",
  "description": "Short description of what this template does",
  "credentials_required": [],
  "version": "1.0.0"
}

Step 2: Create manifest.json

{
  "id": "my-template",
  "name": "My Template",
  "version": "1.0.0",
  "updated": "2026-03-08",
  "type": "native",
  "category": "utilities",
  "description": "Short description of what this template does",
  "credentials_required": [],
  "credentials_optional": [
    {
      "key": "some_api_key",
      "label": "Some API Key",
      "hint": "Only needed for premium features"
    }
  ],
  "tools": [
    {
      "name": "my_tool",
      "description": "What this tool does"
    }
  ],
  "author": "your-github-username",
  "license": "MIT",
  "tested_n8n_version": "2.10.4"
}

Manifest fields

Step 3: Create workflow.json

The workflow bundle uses the n8n-claw-template format. Every template consists of two workflows:

1. Sub-workflow (sub) — contains the actual tool logic (Code node)
2. Server workflow (server) — the MCP server that exposes the tool (mcpTrigger + toolWorkflow)

This two-workflow pattern is required because n8n's API ignores specifyInputSchema when creating workflows, so toolCode parameters don't work. The toolWorkflow pattern avoids this bug.

{
  "format": "n8n-claw-template",
  "format_version": 1,
  "sub": {
    "name": "MCP Sub: My Template",
    "settings": {
      "executionOrder": "v1",
      "callerPolicy": "workflowsFromSameOwner"
    },
    "nodes": [
      {
        "id": "sub-trigger",
        "name": "Execute Workflow Trigger",
        "type": "n8n-nodes-base.executeWorkflowTrigger",
        "typeVersion": 1.1,
        "position": [0, 0],
        "parameters": { "inputSource": "passthrough" }
      },
      {
        "id": "sub-code",
        "name": "My Tool Logic",
        "type": "n8n-nodes-base.code",
        "typeVersion": 2,
        "position": [256, 0],
        "parameters": {
          "jsCode": "const input = $input.first().json;\nconst city = input.city || 'Berlin';\n\n// Make HTTP requests with helpers.httpRequest()\nconst data = await helpers.httpRequest({\n  method: 'GET',\n  url: 'https://api.example.com/data?q=' + encodeURIComponent(city)\n});\n\nreturn [{ json: { result: data } }];"
        }
      }
    ],
    "connections": {
      "Execute Workflow Trigger": {
        "main": [[{ "node": "My Tool Logic", "type": "main", "index": 0 }]]
      }
    }
  },
  "server": {
    "name": "MCP: My Template",
    "settings": { "executionOrder": "v1" },
    "nodes": [
      {
        "id": "mcp-trigger",
        "name": "MCP Server Trigger",
        "type": "@n8n/n8n-nodes-langchain.mcpTrigger",
        "typeVersion": 2,
        "position": [0, 0],
        "parameters": { "path": "my-template" }
      },
      {
        "id": "tool-wf",
        "name": "my_tool",
        "type": "@n8n/n8n-nodes-langchain.toolWorkflow",
        "typeVersion": 2.2,
        "position": [0, 300],
        "parameters": {
          "name": "my_tool",
          "description": "What this tool does. Parameter: city (city name)",
          "workflowId": {
            "__rl": true,
            "value": "REPLACE_SUB_WORKFLOW_ID",
            "mode": "id"
          },
          "workflowInputs": {
            "mappingMode": "defineBelow",
            "value": {
              "city": "={{ $fromAI('city', 'The city name', 'string') }}"
            },
            "matchingColumns": [],
            "schema": [
              {
                "id": "city",
                "displayName": "city",
                "type": "string",
                "description": "The city name",
                "required": true
              }
            ],
            "attemptToConvertTypes": false,
            "convertFieldsToString": false
          }
        }
      }
    ],
    "connections": {
      "my_tool": {
        "ai_tool": [[{ "node": "MCP Server Trigger", "type": "ai_tool", "index": 0 }]]
      }
    }
  }
}

Key points

Testing your template

Before submitting a pull request, test your template locally:

1. Validate JSON — ensure manifest.json and workflow.json are valid JSON
2. Import manually — import the sub-workflow and server workflow into your n8n instance via the API or UI
3. Test the MCP server — call the tool via the n8n-claw agent or directly via MCP client
4. Check the response — verify the tool returns useful data in the expected format

You can also test via the Library Manager if you push your template to a fork and temporarily change the CDN_BASE URL in the Library Manager workflow.

Contributing

1. Fork this repository
2. Create a directory under templates/ with your template ID
3. Add manifest.json and workflow.json (see above)
4. Add an entry to templates/index.json
5. Submit a pull request

PR checklist

• [ ] Template ID is lowercase with hyphens only (e.g. my-api-tool)
• [ ] manifest.json has all required fields
• [ ] workflow.json uses n8n-claw-template format with sub and server
• [ ] REPLACE_SUB_WORKFLOW_ID is used as the workflowId placeholder
• [ ] Code uses helpers.httpRequest() (not $helpers)
• [ ] index.json entry matches manifest data
• [ ] Template tested on a live n8n instance
• [ ] All text in English

CDN

Templates are served via jsDelivr CDN for fast, reliable delivery:

https://cdn.jsdelivr.net/gh/freddy-schuetz/n8n-claw-templates@master/templates/index.json
https://cdn.jsdelivr.net/gh/freddy-schuetz/n8n-claw-templates@master/templates/{id}/manifest.json
https://cdn.jsdelivr.net/gh/freddy-schuetz/n8n-claw-templates@master/templates/{id}/workflow.json

The CDN uses the @master branch reference. Cache updates may take a few minutes after pushing changes. For a reference of template files, see templates/TEMPLATE_EXAMPLE.md.

License

MIT