#mcp

2 post(s)

til

n8n MCP 404 in Claude Code? The endpoint is /sse on a v1 trigger

To use your n8n workflows as tools inside Claude Code, add an MCP Server Trigger node, connect a tool node to it over the ai_tool connection, and activate the workflow. Then point Claude Code at the SSE endpoint: on n8n 2.29 with a v1 MCP Server Trigger the URL is http://host:5678/mcp/{path}/sse, not /mcp/{path} (that 404s). Register it with claude mcp add --transport sse. Separate concern: n8n-as-a-server (this post) is the opposite of czlonkowski/n8n-mcp, which lets Claude build workflows for you.

#claude-code #n8n #mcp #automation #ai-assisted
article

Claude Code MCP Permissions: What Your AI Agent Can Actually Access

If you've connected MCP servers (a notetaker, Gmail, Drive) to Claude Code, check three layers: run claude mcp list to see what's connected (reach), set settings.json permissions so risky tools are read-only or denied (scope — deny wins over allow), and keep the approval prompt on (gate). And remember the vector nobody mentions: text your notetaker pulls in — a meeting transcript — can itself carry instructions the agent will try to follow. Claude Code's own docs warn to trust a server before connecting it.

#claude-code #mcp #ai-security #ai-at-work #ai-assisted