Feature Request: Enhanced n8n API Coverage (Credentials, Tags, Users, Retry, etc.)

[ArtemisAI]

Enhanced n8n API Coverage

Overview

This is a comprehensive feature request to expand n8n-mcp's API coverage based on a complete analysis of the n8n Public API. Currently, the MCP server covers workflow and execution basics well, but lacks support for several important API endpoints.

Current API Coverage Analysis

✅ Well Covered

• Workflow CRUD operations
• Workflow activation/deactivation (recently added)
• Execution listing and retrieval
• Execution deletion

🔴 Missing Critical Features

1. Execution Retry (HIGH Priority)

• API: POST /executions/{id}/retry
• Use case: Automated error recovery, resilient workflows
• Impact: Essential for production reliability

2. Credential Management (CRUCIAL Priority) ⚠️

• APIs: /credentials, /credentials/{id}, /credentials/schema/{type}
• Use case: CI/CD credential provisioning, secret management
• Impact: Blocks workflow automation in CI/CD pipelines
• Security note: Credential data is write-only (n8n security feature)

3. Tag Management (MEDIUM Priority)

• APIs: /tags, /tags/{id}, /workflows/{id}/tags
• Use case: Workflow organization, environment tagging
• Impact: Improves workflow discovery and management

4. User Management (HIGH Priority)

• APIs: /users, /users/{id}, /users/{id}/role
• Use case: Automated user provisioning, RBAC
• Impact: Essential for multi-user instances

📝 Additional Features (Lower Priority)

5. Variable Management - Environment variable lifecycle
6. Project Management - Enterprise multi-tenant support
7. Source Control Integration - GitOps workflows
8. Audit Generation - Security compliance

Proposed Implementation Approach

Each feature would follow the established pattern:

1. Add API client methods to src/services/n8n-api-client.ts
2. Define tools in src/mcp/tools-n8n-manager.ts
3. Implement handlers in src/mcp/handlers-n8n-manager.ts
4. Register in src/mcp/server.ts

Benefits

• 95%+ API coverage for crucial features
• Complete workflow lifecycle management
• Production-ready error recovery
• CI/CD integration support
• Enterprise features support

Breaking Changes

None - all additions are backward compatible.

Related Work

• Full API coverage analysis: [Available on request]
• Detailed implementation specifications prepared
• Similar to recent activation/deactivation PR pattern

Community Interest

Would the maintainers be interested in PRs for these features? I can submit them incrementally, starting with high-priority items like execution retry and credential management.

Implementation Order Recommendation

1. Phase 1 (Quick wins): Retry execution, Variable management
2. Phase 2 (Core features): Credential management, Tag management
3. Phase 3 (Advanced): User management, Source control
4. Phase 4 (Enterprise): Project management, Audit generation

Happy to contribute PRs following the project's coding standards and patterns!

[czlonkowski]

Hi @ArtemisAI and thank you for your proposition! I would be happy to review the PRs, if you decide to contribute

[czlonkowski]

PR #402

[danlflh]

Great proposition