brilliant-directories-mcp 5.2.1 → 5.2.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -2011,7 +2011,7 @@
2011
2011
  "/api/v2/user/transactions": {
2012
2012
  "post": {
2013
2013
  "operationId": "getUserTransactions",
2014
- "summary": "Get user transactions",
2014
+ "summary": "Get member billing transactions (invoices)",
2015
2015
  "tags": [
2016
2016
  "Users"
2017
2017
  ],
@@ -2045,13 +2045,13 @@
2045
2045
  }
2046
2046
  }
2047
2047
  },
2048
- "description": "Fetch a single usertransactions record. Read-only.\n\n**Required:** `user_id`.\n\n**Returns:** `{ status: \"success\", message: [{...record}] }` — the `message` array contains 1 record when found. Empty or HTTP 404 when not found.\n\n_Auth: `X-Api-Key` header. Rate limit: 100 req/60s (on 429, back off 60s). Errors: `{ \"status\": \"error\", \"message\": \"...\" }` with standard HTTP codes._"
2048
+ "description": "Fetch the billing transaction history (invoices) for a specific member. Read-only. Backed by the WHMCS billing integration.\n\n**Required:** `user_id` (POST body).\n\n**Use when:** you need to see a member's paid/unpaid invoices, payment methods, billing history, or reconcile billing status. Common reasons: answering a member's \"what did I pay for?\" question, exporting billing history, auditing revenue per member.\n\n**See also:** `getUserSubscriptions` (active/past membership plan signups — different resource from invoices), `getUser` (member profile).\n\n**Returns:** `{ status: \"success\", message: { total: <count>, invoices: [{...invoice records}] } }`. Each invoice includes `id`, `invoicenum`, `date`, `duedate`, `datepaid`, `subtotal`, `credit`, `tax`, `total`, `status` (`Paid`, `Unpaid`, etc.), `paymentmethod`, and an `items` array with per-line `description`, `amount`, `type`, etc. NOT a simple list of rows — the `message` is an object containing `invoices` as the array.\n\n**Reference support articles:**\n- https://support.brilliantdirectories.com/support/solutions/articles/12000108047 (API Reference — Users)\n- https://support.brilliantdirectories.com/support/solutions/articles/12000103947 (Users API — How to Manage Users with API Calls)\n\n_Auth: `X-Api-Key` header. Rate limit: 100 req/60s (on 429, back off 60s). Errors: `{ \"status\": \"error\", \"message\": \"...\" }` with standard HTTP codes._"
2049
2049
  }
2050
2050
  },
2051
2051
  "/api/v2/user/subscriptions": {
2052
2052
  "post": {
2053
2053
  "operationId": "getUserSubscriptions",
2054
- "summary": "Get user subscriptions",
2054
+ "summary": "Get member subscriptions (membership plan history)",
2055
2055
  "tags": [
2056
2056
  "Users"
2057
2057
  ],
@@ -2085,7 +2085,7 @@
2085
2085
  }
2086
2086
  }
2087
2087
  },
2088
- "description": "Fetch a single usersubscriptions record. Read-only.\n\n**Required:** `user_id`.\n\n**Returns:** `{ status: \"success\", message: [{...record}] }` — the `message` array contains 1 record when found. Empty or HTTP 404 when not found.\n\n_Auth: `X-Api-Key` header. Rate limit: 100 req/60s (on 429, back off 60s). Errors: `{ \"status\": \"error\", \"message\": \"...\" }` with standard HTTP codes._"
2088
+ "description": "Fetch the subscription / membership-plan history for a specific member. Read-only. Backed by the WHMCS billing integration.\n\n**Required:** `user_id` (POST body).\n\n**Use when:** checking a member's current membership plan, their billing cycle (Monthly/Yearly), next due date, plan upgrade history, whether auto-renewal is on, or past canceled subscriptions.\n\n**See also:** `getUserTransactions` (invoice-level billing records — different resource), `getUser` (member profile — profile-level subscription references `subscription_id`), `listMembershipPlans` (all plan definitions on the site).\n\n**Returns:** `{ status: \"success\", message: { total: <count>, subscriptions: [{...subscription records}] } }`. Each subscription includes `id`, `userid`, `packageid` (membership plan ID), `regdate`, `nextduedate`, `billingcycle` (e.g. `Monthly`, `Yearly`), `paymentmethod`, `amount`, `domainstatus` (`Active`, `Cancelled`, etc.), and related fields. NOT a simple list of rows — the `message` is an object containing `subscriptions` as the array.\n\n**Reference support articles:**\n- https://support.brilliantdirectories.com/support/solutions/articles/12000108047 (API Reference — Users)\n- https://support.brilliantdirectories.com/support/solutions/articles/12000103947 (Users API — How to Manage Users with API Calls)\n\n_Auth: `X-Api-Key` header. Rate limit: 100 req/60s (on 429, back off 60s). Errors: `{ \"status\": \"error\", \"message\": \"...\" }` with standard HTTP codes._"
2089
2089
  }
2090
2090
  },
2091
2091
  "/api/v2/users_reviews/get": {
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "brilliant-directories-mcp",
3
3
  "mcpName": "io.github.brilliantdirectories/brilliant-directories-mcp",
4
- "version": "5.2.1",
4
+ "version": "5.2.2",
5
5
  "description": "Official MCP server for Brilliant Directories — manage members, posts, leads, reviews, and more.",
6
6
  "main": "index.js",
7
7
  "bin": {