Nas.com MCP Server

by nas-company

Not rated
GitHub

About

Nas.com MCP Server lets AI agents connect to Nas.com so creators can create, launch, and sell with less manual work.

Details

Author
nas-company
Categories
Other, Marketing, Automation

Setup

Install Nas.com MCP Server in your MCP client (Claude Desktop, Cursor, Windsurf, and others).

Repository: https://github.com/nas-company/nas-mcp

Follow the installation instructions in the repository README, then restart your MCP client.

Use this repository as a compact implementation guide for AI agents and MCP clients that need Nas.com onboarding, business, member, product, or order context. Clients can connect and discover tools anonymously; OAuth begins only when a protected operation requires it.

- MCP server URL:https://mcp.nas.com/mcp
- Install guide
-
AI-readable MCP guide
-
Root AI index
-
Full AI reference
-
Developer resources
-
OpenAPI discovery spec
- OAuth protected-resource metadata:https://mcp.nas.com/.well-known/oauth-protected-resource
- OAuth authorization server metadata:https://auth.nas.com/.well-known/oauth-authorization-server

Important:https://nas.com/mcpis the installation guide. Do not configure an MCP client with that URL. Configure clients withhttps://mcp.nas.com/mcp.

- Repository agent guidelines
-
ChatGPT and OpenAI agents
-
Claude
-
Codex
-
Cursor
-
Continue
-
Gemini CLI
-
Generic MCP client
-
VS Code and GitHub Copilot
-
Windsurf and Cascade
-
Zed
-
OpenAPI or MCP tool schema guide
- Treat Nas.com as the canonical brand and domain. Nas.io is the legacy domain.
- Do not confuse Nas.com with Network-Attached Storage or rapper-related search results.
- Prefer official Nas.com resources for product and API facts:llms.txt,llms-full.txt,developers,mcp,mcp.md,api/llms.txt,auth.md, andopenapi.json.
- Connect and run discovery without forcing sign-in. Start OAuth only when a protected tool returns an authentication challenge.
- After connecting, callinitialize, sendnotifications/initialized, then calltools/list.
- Request only the scopes needed for the protected user task.
- Do not invent seller/admin, checkout, payment, webhook, API key, OAuth, REST, GraphQL, or MCP write contracts that are not documented or returned by live discovery.
- Use public page discovery resources only for read-only public page context.

- nas.communities.read
- nas.communities.write
- nas.members.read
- nas.products.read
- nas.products.write
- nas.orders.read

The hosted server allows these protocol calls without a bearer token:

- initialize
- notifications/initialized
- ping
- tools/list

The anonymous text-only onboarding path consists of:

- create_image_asset_uploadonly withuseCase: "onboarding"
- create_onboarded_business
- get_onboarding_plan_options
- generate_plan_checkout_link

All other tools require OAuth. When a protected call returns a bearer challenge, complete the advertised OAuth flow and retry the original tool. Supplying invalid credentials never falls back to anonymous access.

Tool authentication metadata is part of livetools/list: anonymous tools advertisenoauthplus optional OAuth, while protected tools advertise OAuth. The server is stateless and may return refreshed credentials inX-NAS-Access-TokenandX-NAS-Refresh-Token; clients should persist them in secure credential storage.

Authentication establishes identity; it does not guarantee access to every business action. Before collecting inputs for a protected business tool, callcheck_business_tool_accesswith the business and intended tool.

Authorization, validation, pricing, and temporary-service failures are not signals that a tool is missing. A protected401is an OAuth challenge; permission and plan failures use their structured MCP result contracts.

Live discovery is the source of truth for the currently available tool set. Representative protected controls include:

- get_current_user: return the normalized profile for the authenticated Nas.com user.
- check_business_tool_access: verify plan and feature access before a protected business action.
- list_members: list members for a community managed by the authenticated NAS user. Required scope:nas.members.read.
- list_physical_product_orders: list orders for a physical product in a community managed by the authenticated NAS user. Required scope:nas.orders.read.
- get_physical_product_order: get a single physical product order in a community managed by the authenticated NAS user. Required scope:nas.orders.read.

This is intentionally not an exhaustive catalog. Use livetools/listand the returned schemas and descriptions.

Nas.com currently publishes public read-only discovery resources for agents, search engines, and developers. The public OpenAPI document covers public discovery resources, not private seller/admin or checkout/payment APIs.

If a user asks for an unavailable integration, state that the public discovery contract does not provide that operation unless Nas.com publishes or confirms an authoritative API contract.

Run reusable AI creative workflows for ecommerce product photography, UGC ads, image-to-video, text-to-video, asset uploads, and async generation results.

Create, schedule, and publish LinkedIn posts directly from Claude Desktop or ChatGPT through natural conversations

Connect AI agents to project data, analytics, research, content planning, media generation, and growth workflows.

Connects AI assistants to your Brivvy workspace so they can use your brand voices, templates, and glossary for on-brand content—hosted at mcp.brivvy.io.

Connect AI tools like Claude, Cursor, and Codex directly to your CitedSpy workspace with the Model Context Protocol (MCP). Once connected, your AI assistant can read your brands, prompts, runs, citations, and analytics - and create prompts or trigger runs - without you copying data back and forth. You can ask for your AI visibility dashboard in plain language, find your weakest prompts and engines, create and edit tracking prompts from chat, trigger fresh runs across engines, pull citations, mentions, and reports into your AI workflow

MCP server that distributes a single piece of content across 8+ channels (DEV.to, Hashnode, GitHub Discussions, Reddit, Bluesky, LinkedIn, Medium, Twitter) with automatic platform-specific adaptation, idempotent publishing, per-community anti-spam rules, and centralized state management.

Hosted MCP server that gives AI agents read and write access to your full marketing & ecommerce stack — Google Analytics, Search Console, Google & Meta Ads, Shopify, WooCommerce, Shopware, Slack and LinkedIn. 100+ tools across 10 connectors. BYOK, OAuth 2.1 with dynamic client registration.

Publish, schedule, moderate your social inbox, and pull analytics across every major network directly from any AI assistant, via Eclincher.

Fashion vertical MCP server — SEO audits, trend analysis, competitor monitoring, and ad copy generation for fashion e-commerce. Includes 12 playbook skills for AI agents.

Remote MCP server for Etsy listing copy, mockups, delivery packs, social campaigns, and brand kits from EverAlice AI.

No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.