NAS MCP n8n Bridge
Splits the live Nas.com MCP catalog into 24 product-scoped n8n workflows, enabling focused agent interactions with specific business, product, and marketing tools.
README
NAS MCP n8n Bridge
Credential-free n8n workflow templates that expose the complete public Nas.com MCP catalog through smaller, product-scoped servers backed by the official Nas.com MCP endpoint.
Instead of giving one agent the entire Nas.com tool catalog, this project splits the live actions across focused endpoints for:
- Core business operations
- Physical products
- Courses
- Events
- Lead forms
- Zero Link
- Sessions
- Challenges
- Operations and business administration
- Members
- Magic Reach
- Custom domains
- Magic Audience
- Facebook tracking
- Referrals
- Commerce analytics
- Discounts and upsells
- Chat and mail
- Payouts
- Creative assets
- Magic Content
- AI Cofounder
- Plans and billing
This is an unofficial community project. It is not affiliated with or endorsed by Nas Company.
Why this exists
Large tool catalogs make agent behavior harder to reason about. These templates use n8n as a thin MCP-to-MCP bridge so each client only receives the product actions it needs while the repository as a whole covers the complete live catalog.
The optional orchestrator provides one MCP endpoint in front of all 24 scoped servers. It does not use another LLM or a generic dispatcher. Each of the 422 unique tool names is deterministically connected to exactly one downstream workflow, so n8n forwards the call to the correct product scope.
Your MCP client
|
| Bearer token
v
n8n scoped MCP workflow
|
| Nas.com OAuth
v
https://mcp.nas.com/mcp
Quick start
- Use a current n8n version with the MCP Server Trigger and MCP Client Tool nodes.
- Import one or more files from
workflows/. - Open the MCP Server Trigger and create your own inbound bearer credential.
- Open the NAS Actions node and create your own Nas.com MCP OAuth2 credential.
- Complete the Nas.com OAuth connection.
- Activate the workflow.
- Copy the production MCP URL from the trigger into your MCP client and use your own bearer token.
- Run
tools/listfrom the client and confirm that only the expected scoped tools are visible.
Detailed instructions are in docs/setup.md.
Included templates
Every generated JSON file in workflows/ is an independent
importable MCP server. Import only the product scopes you need.
workflows/orchestrator.json is optional. Import
it after the 24 scoped servers when you want one client-facing MCP URL. Replace
the https://your-n8n.example placeholder in its MCP Client Tool nodes with
your own n8n base URL, then attach the same bearer credential used by the
downstream scoped servers.
The committed workflows contain no credentials, credential IDs, account IDs, workflow IDs, webhook IDs, access tokens, refresh tokens, personal server URLs, email addresses, or user-specific community data. After import, n8n will ask you to attach your own credentials.
Development
Requires Node.js 20 or newer. There are no runtime dependencies.
npm run build
npm test
npm run audit:live
npm run build regenerates the importable workflow files from
src/workflow-specs.mjs. npm test verifies that the
generated files are current, credential-free, structurally valid, and clean of
common secret patterns. npm run audit:live compares every published allowlist
with Nas.com's current anonymous tools/list response and fails if a live action
is missing or a configured action has disappeared.
When Nas.com changes its public catalog:
npm run sync:catalog
npm run build
npm run audit:live
Security model
- Inbound access is protected by a bearer credential you create in n8n.
- Outbound protected Nas.com calls use OAuth through the MCP Client Tool.
- Credentials stay in n8n's credential store, not inside exported workflow JSON.
- Each workflow uses an explicit allowlist of Nas.com tools.
- The orchestrator removes duplicated shared actions before aggregation, so every public tool name has one deterministic downstream route.
- Publishing, deletion, and other consequential actions are still available in relevant scopes. Your MCP client should require confirmation for those calls.
See SECURITY.md before deploying.
License
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
E2B
Using MCP to run code via e2b.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.