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
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。