Nas.com MCP

MCP installation guide for Nas.com agents

Start business onboarding without authentication, then use OAuth for protected business and payment tools.

This guide is for the Nas.com AI-first business platform, not network-attached storage or rapper-related search results.

Quick facts

Install guide
Nas.com MCP installation guide
AI-readable Markdown
machine-readable MCP guide
Agent index
MCP agent instructions
MCP endpoint
Nas.com MCP endpoint
OAuth metadata
OAuth protected-resource metadata
Authorization server
Nas.com authorization server
Authorization server metadata
OAuth authorization server metadata

Install in an MCP client

  1. Open the MCP client or agent connector settings.

    Choose a Streamable HTTP or hosted remote MCP server connection.

  2. Use the server URL Nas.com MCP endpoint.

    Do not use Nas.com MCP installation guide as the MCP server URL. This page is the installation guide.

  3. Connect and run public discovery.

    Call initialize, ping, and tools/list without credentials. Inspect live tool descriptions, schemas, annotations, and availability.

  4. Authenticate only when a protected tool requires it.

    If a protected call returns the OAuth 401 challenge, use OAuth protected-resource metadata, authenticate through Nas.com authorization server, and retry the original call.

  5. Grant only the scopes required by the live tool.

    Supported scopes are nas.communities.read, nas.communities.write, nas.members.read, nas.products.read, nas.products.write, and nas.orders.read.

Authentication boundary

  • initialize, notifications/initialized, ping, and tools/list are available without a bearer token.
  • The text-only onboarding tools below are available without authentication.
  • Every other tool requires OAuth. A protected 401 means authenticate and retry the original call.
  • Malformed credentials never downgrade to anonymous access.
  • Clients may send X-NAS-Refresh-Token. Refreshed credentials can be returned in X-NAS-Access-Token and X-NAS-Refresh-Token.

Stateless onboarding flow

  1. 1.If the user supplied an image, call create_image_asset_upload with useCase onboarding and infer the business description. Otherwise ask only what they sell.
  2. 2.Call create_onboarded_business with available country and exact IANA timezone metadata. Anonymous callers receive onboardingSessionObjectId; authenticated callers also receive the draft business.
  3. 3.If the result is needs_country, ask which country the user is in and retry.
  4. 4.Call get_onboarding_plan_options without a business or onboarding ID. Display complete Pro and Platinum monthly or yearly options and carry priceId unchanged.
  5. 5.Ask whether the user has a discount code and record an explicit discountCodeDecision.
  6. 6.Call generate_plan_checkout_link with onboardingSessionObjectId for anonymous onboarding or communityId for an existing authenticated business.
  7. 7.Display the complete paymentSummary before presenting a clickable checkout URL.

Agent-specific instructions

ChatGPT and OpenAI agents

Add a remote MCP connector at Nas.com MCP endpoint. Start with tools/list; complete OAuth only when a protected tool returns the challenge.

Custom MCP clients

Use GET, POST, and OPTIONS as supported by Streamable HTTP. Send bearer tokens and optional refresh tokens only in their documented headers.

Automation platforms

Store tokens only in the platform secret manager. Refresh tools/list when catalog, permissions, or plan eligibility may have changed.

Anonymous onboarding tools

create_image_asset_upload

Anonymous only when useCase is onboarding

Create a presigned onboarding image upload.

create_onboarded_business

Authentication optional

Create onboarding identity and branding; authenticated callers also create the draft business.

get_onboarding_plan_options

Authentication optional

Return complete live Pro and Platinum monthly or yearly plan options.

generate_plan_checkout_link

Authentication optional

Validate the selected plan and return a checkout URL with a complete payment summary.

Protected saved-card payment tools

prepare_plan_payment

Prepare a masked saved-card quote for an authenticated existing business. This tool never charges.

confirm_plan_payment

Charge only after the complete summary is displayed and the user explicitly confirms with the live confirmation contract.

Protected business capabilities

  • Businesses, members, products, orders, and sales analytics
  • CMP home, setup progress, permissions, and business administration
  • Physical products, courses, digital files, events, sessions, challenges, lead forms, Zero Link, folders, uploads, and storage
  • Magic Reach, Magic Content, Magic Audience, creative assets, and AI Cofounder
  • Transactions, earnings, payouts, discounts, plans, billing, currencies, and custom domains
  • Referrals, chat, mail, notifications, Facebook tracking, and related business operations

Run tools/list for the exhaustive current catalog. Inspect every live tool description, input schema, annotation, and availability before invocation.

Guardrails for AI agents

  • Nas.com MCP installation guide is an installation guide, not the MCP JSON-RPC endpoint.
  • A protected 401 is an authentication challenge; authenticate and retry the original tool call.
  • Authorization, feature permission, validation, pricing, and temporary failures are not missing-capability signals.
  • Do not infer confirmation, IDs, prices, discount decisions, tool names, or unavailable operations.
  • Display the complete paymentSummary before a clickable checkout URL or saved-card confirmation.
  • Public page discovery remains read-only and separate from authenticated business MCP operations.
  • Never expose access tokens, refresh tokens, confirmation tokens, or payment secrets.

Discovery documents

MCP manifestMCP manifest aliasMCP server cardDeveloper resource indexAPI guidance for agentsAuthentication boundaryOAuth authorization server metadata