n8n MCP: Troubleshooting Empty workflow.tags from get_workflow_details

The MCP get_workflow_details call returning an empty workflow.tags array is a practical problem for teams implementing governance, auditing, and automation on top of n8n. Tags are often the primary way teams categorize workflows by owner, environment, compliance requirements, or business domain; losing that metadata in programmatic access breaks reporting, access controls, and analytics pipelines.

Root causes to evaluate: API surface mismatches between UI and MCP tools, schema or migration issues where tags are stored differently (e.g., separate join tables or newer tag models), permission scopes preventing tags from being exposed, or caching layers returning stale representations. Start by reproducing the issue with a minimal authenticated call using the same credentials the MCP server uses, and inspect raw database rows for tags to confirm persistence. Compare MCP's API contract to the UI backend endpoints to see if there's a mapping discrepancy.

Practical mitigations include adding a temporary reconciliation step: query the UI's workflow list endpoint or directly read the database for tag joins and enrich MCP responses. Implement integration tests that assert tag roundtrips and tag visibility across roles. For longer-term fixes, push for a schema alignment or API contract update and document expected tag shapes in the MCP tools reference.

For business leaders: prioritize this as a medium-severity governance issue. If compliance or audit trails depend on tags, treat the fix as operationally urgent. Ask engineering to implement defensive logging and a reconciliation job, and require tag-preservation tests in your CI pipeline before adopting MCP-based automation across production workflows.