# 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](https://mcp.nas.com/mcp).

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.

```text
Your MCP client
      |
      | Bearer token
      v
n8n scoped MCP workflow
      |
      | Nas.com OAuth
      v
https://mcp.nas.com/mcp
```

## Quick start

1. Use a current n8n version with the MCP Server Trigger and MCP Client Tool
   nodes.
2. Import one or more files from [`workflows/`](workflows/).
3. Open the **MCP Server Trigger** and create your own inbound bearer credential.
4. Open the **NAS Actions** node and create your own Nas.com MCP OAuth2
   credential.
5. Complete the Nas.com OAuth connection.
6. Activate the workflow.
7. Copy the production MCP URL from the trigger into your MCP client and use
   your own bearer token.
8. Run `tools/list` from the client and confirm that only the expected scoped
   tools are visible.

Detailed instructions are in [docs/setup.md](docs/setup.md).

## Included templates

Every generated JSON file in [`workflows/`](workflows/) is an independent
importable MCP server. Import only the product scopes you need.

[`workflows/orchestrator.json`](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.

```bash
npm run build
npm test
npm run audit:live
```

`npm run build` regenerates the importable workflow files from
[`src/workflow-specs.mjs`](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:

```bash
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](SECURITY.md) before deploying.

## License

[MIT](LICENSE)