[RussGuo]

Adds FateTell's connector (hosted MCP at https://mcp.fatetell.com/login/mcp, Streamable HTTP, OAuth 2.1 + PKCE via auth.fatetell.com, with Client ID Metadata Documents and Dynamic Client Registration, so no client ID or secret in the manifest) under third_party/fatetell, following the Questrade / AdKit pattern: .cursor-plugin/plugin.json, mcp.json, README, CHANGELOG, MIT license and logo.

FateTell computes BaZi (Four Pillars) charts and the Chinese almanac with its own deterministic engine and returns the charts saved in a FateTell account. The server calls no language model; the agent explains the results. The plugin also ships the fatetell-bazi skill (skills/fatetell-bazi/), which covers which tool to call and how to read the results, with a static chart-card template for hosts that do not render MCP Apps.

Endpoint. /login/mcp answers the first request with 401, so sign-in happens while Cursor connects. FateTell's default endpoint allows anonymous use of two tools and asks for sign-in only when a tool needs it; Cursor handles a sign-in challenge only at connect time, so the plugin uses the sign-in endpoint. The tools are identical on both.

Tools. Nine tools, eight read-only. The only write tool is create_saved_chart, which adds a chart to the user's FateTell account; it cannot edit or delete existing charts.

Free and member. Any email address can sign in and the new account is free. A free account covers chart casting, the almanac, the account summary and reading saved charts (5 tools). The Day Master judgment, daily fortune, chart calendar and saving a chart need an active FateTell membership (4 tools); membership is checked on every call. Every tool has a per-account daily cap to prevent abuse.

Registers it in .cursor-plugin/marketplace.json (appended after questrade, no minClientVersions, so listing is left to you) and the README table. Category is integrations, as for the other hosted MCP connectors. The description is identical across plugin.json, marketplace.json and both READMEs.

node scripts/validate-plugins.mjs passes ("All plugins validated successfully.").

Context: the publisher application was submitted through cursor.com/marketplace/publish on 2026-11-03 (handle fatetell), and a member review account was emailed to marketplace-publishing@cursor.com. The x.ai form was not used because it returned 502. The plugin README has a "Testing the connector" section; it contains no credentials. Happy to adjust anything here, or to close this if the form is the right route.

Vendor repo with the skill and plugin files: https://github.com/RussGuo/fatetell-mcp
Contact: contact@fatetell.com

🤖 Generated with Claude Code