Fanvault

Fanvault MCP

Connect Fanvault to Claude, ChatGPT, Cursor, and other Model Context Protocol clients. Creators can run their storefront through natural-language requests: publish posts, create listings and courses, manage orders and shipping, schedule content, publish to Instagram, and read analytics.

Hosted service: this public repository contains distribution metadata and documentation. The production server is hosted by Fanvault; its application source code is not published here.

Connect

Field	Value
MCP endpoint	https://fanvault.shop/mcp
Transport	Streamable HTTP
Authentication	OAuth 2.1 or a Fanvault personal access token
Availability	Open beta for Fanvault creator accounts
Tool count	52
Documentation	https://fanvault.shop/developers/mcp
OpenAPI 3.1	https://fanvault.shop/api/mcp/openapi
Health	https://fanvault.shop/api/mcp/health

Claude and ChatGPT

Add https://fanvault.shop/mcp as a custom connector. The client opens Fanvault's OAuth consent flow; sign in and approve access.

Claude Code

Create a personal access token in Fanvault → Settings → MCP, then run:

claude mcp add --transport http fanvault https://fanvault.shop/mcp \
  --header "Authorization: Bearer fv_mcp_your_token_here"

Cursor

{
  "mcpServers": {
    "fanvault": {
      "url": "https://fanvault.shop/mcp",
      "headers": {
        "Authorization": "Bearer fv_mcp_your_token_here"
      }
    }
  }
}

Never paste a personal access token into a chat message. Store it only in the client's protected configuration or credential store.

What agents can do

• Storefront: read and update creator profiles, layouts, and shipping origin settings.
• Listings: create, edit, cancel, and relist physical products and auctions.
• Digital products: manage downloads, courses, memberships, files, and lessons.
• Content: create feed posts, import media, generate story images, and publish to Instagram.
• Commerce: inspect orders, generate shipping labels, mark fulfillment, and review payout readiness.
• Operations: search inventory, read analytics and transactions, respond to messages, and schedule one-off or recurring actions.

See the complete tool catalog and usage examples.

Access model

A creator connection can act only on that creator's own Fanvault account. Fan accounts are not accepted during the open beta. Agency and administrator tokens can be restricted to a defined creator set.

Personal access tokens use least-privilege scopes:

• read — view listings, products, orders, and analytics.
• write — create and update storefront data.
• destructive — delete supported records; destructive calls also require explicit confirmation.
• payments — generate Stripe-hosted onboarding or dashboard links.

OAuth connections use the scopes approved in the browser consent flow.

Security and privacy

• Authorization and account status are checked on every call.
• Personal access tokens are displayed once and stored as hashes.
• Tool calls are rate-limited and audit-logged.
• Destructive actions require both scope permission and explicit confirmation.
• Card and bank credentials do not flow through MCP; payment tools return Stripe-hosted links.
• URL-based media imports use guarded fetch and content-validation pipelines.

Read Security, the Fanvault privacy policy, and the Fanvault terms.

Registry metadata

• server.json — Official MCP Registry manifest.
• mcp.json — remote-server client configuration.
• .cursor-plugin/plugin.json — Cursor Marketplace plugin manifest.
• context7.json — Context7 documentation-indexing configuration.

Canonical registry name: io.github.thefanvault/fanvault

Support

• Developer documentation: https://fanvault.shop/developers/mcp
• Support: mailto:support@fanvaultshop.com
• Security reports: see SECURITY.md

Documentation license

The documentation and metadata in this repository are available under CC BY 4.0. This license does not apply to the hosted Fanvault service or its proprietary server implementation.