@crscreditapi/finstack-mcp-server 0.2.0-fac1a77 → 0.3.0-61c51ea

package/.env.example

@@ -11,8 +11,3 @@ FINSTACK_PROD_BASE_URL=https://portal.example.com
 
 # Shared secret for the mware-portal chatbase endpoints (X-Chatbase-Secret header)
 FINSTACK_CHATBASE_SECRET=
-
-# === Vendor contact directory (crs-vendor-contacts) ===
-# Base URL of the already-deployed vendor contacts app. Read-only, no auth.
-# Defaults to the production Vercel URL if unset.
-# VENDOR_CONTACTS_BASE_URL=https://crs-vendor-contacts.vercel.app

package/README.md

@@ -12,6 +12,7 @@ MCP server exposing CRS B2B (Finstack) customer data over the [Model Context Pro
 | `finstack_get_customer_invoices` | Paginated list of finalized invoices for one customer with full line-item breakdown. |
 | `finstack_get_customer_pricing_config` | Full configured pricing state for one customer: products, pricing addendums, and environment-user productPricing. Use to cross-check invoiced rates against contracted pricing. |
 | `finstack_get_pricing_addendum_text` | Extracted text from a pricing addendum PDF (with or without disclaimer). Server-side parses the PDF and returns plain text. |
+| `finstack_get_vendors` | Look up who to contact at an external vendor/partner (credit bureaus and data vendors like Equifax, TransUnion, Experian, CIC). OR-matches `query` across company, name, role, notes, location, and specialty tags; optional `connection` degree filter. |
 
 ## Install
 

package/dist/api/vendor.api.d.ts

@@ -1,15 +1,25 @@
+/**
+ * Vendor contact directory calls.
+ *
+ * Backed by the mware-portal chatbase API, same as the customer tools:
+ * GET /api/v1/chatbase/vendor_contacts returns the whole vendor contact list
+ * in one shot (authenticated with the shared X-Chatbase-Secret). We fetch the
+ * full list and filter in-process so callers can match on specialty tags and
+ * connection degree too.
+ */
+import type { ApiClient } from './client.js';
 export interface VendorContact {
-    id: string;
+    id: number;
     vendor: string;
     name: string;
     email: string;
     phone: string;
     role: string;
-    notes: string;
-    connection: string;
     location: string;
-    bestFor: string;
+    linkedin: string | null;
     specialties: string[];
+    degree: string;
+    notes: string;
 }
 export type VendorConnection = '1st Degree' | '2nd Degree' | 'all';
 export interface VendorSearchResult {
@@ -22,12 +32,12 @@ export interface VendorSearchResult {
 /**
  * Search the vendor contact directory.
  *
- * The connection filter is applied server-side; the keyword query is applied
- * here, OR-matched across every contact field plus specialty tags so that a
- * question like "who handles ECM pricing" matches on role, notes, AND the
- * `pricing` specialty.
+ * The whole list is fetched from the chatbase endpoint, then filtered here:
+ * the connection filter narrows by degree, and the keyword query is OR-matched
+ * across every contact field plus specialty tags so that a question like
+ * "who handles ECM pricing" matches on role, notes, AND the `pricing` specialty.
  */
-export declare function searchVendorContacts(args: {
+export declare function searchVendorContacts(client: ApiClient, args: {
     query?: string;
     connection?: VendorConnection;
     limit?: number;

package/dist/api/vendor.api.js

@@ -1,53 +1,34 @@
-/**
- * Vendor contact directory calls.
- *
- * Backed by the standalone crs-vendor-contacts web service (the CPO's
- * Slack-powered vendor Rolodex). There is no database — the service stores
- * contacts in a JSON blob and exposes them over a read-only REST endpoint
- * (GET /api/vendors). We fetch the list and filter in-process so callers can
- * match on specialty tags too (the upstream ?q= filter only covers a subset
- * of fields).
- *
- * This calls the vendor app's already-deployed public API, so it needs no
- * redeploy of that project — only the env var VENDOR_CONTACTS_BASE_URL
- * (defaults to the production Vercel URL).
- */
-import { ApiClient } from './client.js';
-const DEFAULT_BASE_URL = 'https://crs-vendor-contacts.vercel.app';
-const DEFAULT_TIMEOUT_MS = 30_000;
-let _vendorClient = null;
-function getVendorClient() {
-    if (_vendorClient)
-        return _vendorClient;
-    const baseUrl = process.env.VENDOR_CONTACTS_BASE_URL ?? DEFAULT_BASE_URL;
-    const timeoutMs = process.env.FINSTACK_TIMEOUT_MS
-        ? parseInt(process.env.FINSTACK_TIMEOUT_MS, 10)
-        : DEFAULT_TIMEOUT_MS;
-    _vendorClient = new ApiClient({ baseUrl, timeoutMs });
-    return _vendorClient;
-}
+const CONNECTION_TO_DEGREE = {
+    '1st Degree': 'first_degree',
+    '2nd Degree': 'second_degree',
+};
 /**
  * Search the vendor contact directory.
  *
- * The connection filter is applied server-side; the keyword query is applied
- * here, OR-matched across every contact field plus specialty tags so that a
- * question like "who handles ECM pricing" matches on role, notes, AND the
- * `pricing` specialty.
+ * The whole list is fetched from the chatbase endpoint, then filtered here:
+ * the connection filter narrows by degree, and the keyword query is OR-matched
+ * across every contact field plus specialty tags so that a question like
+ * "who handles ECM pricing" matches on role, notes, AND the `pricing` specialty.
  */
-export async function searchVendorContacts(args) {
-    const client = getVendorClient();
-    const params = new URLSearchParams();
+export async function searchVendorContacts(client, args) {
+    const secret = process.env.FINSTACK_CHATBASE_SECRET;
+    if (!secret) {
+        throw new Error('FINSTACK_CHATBASE_SECRET must be set');
+    }
+    const response = await client.get('/api/v1/chatbase/vendor_contacts', { 'X-Chatbase-Secret': secret });
+    if (response.status !== 'success' || !response.data) {
+        throw new Error(response.message || 'Failed to fetch vendor contacts');
+    }
+    let matched = response.data.vendor_contacts;
     if (args.connection && args.connection !== 'all') {
-        params.set('connection', args.connection);
+        const degree = CONNECTION_TO_DEGREE[args.connection];
+        matched = matched.filter((v) => v.degree === degree);
     }
-    const qs = params.toString();
-    const all = await client.get(qs ? `/api/vendors?${qs}` : '/api/vendors');
-    let matched = all;
     const q = args.query?.trim().toLowerCase();
     if (q) {
         const terms = q.split(/\s+/).filter((t) => t.length > 1);
         if (terms.length > 0) {
-            matched = all.filter((v) => {
+            matched = matched.filter((v) => {
                 const haystack = [
                     v.vendor,
                     v.name,
@@ -55,7 +36,6 @@ export async function searchVendorContacts(args) {
                     v.role,
                     v.notes,
                     v.location,
-                    v.bestFor,
                     ...(v.specialties ?? []),
                 ]
                     .filter(Boolean)

package/dist/handlers/index.js

@@ -1,5 +1,5 @@
 import { handleGetCustomerInvoices, handleGetCustomerPricingConfig, handleGetCustomerRevenue, handleGetCustomerSummary, handleGetPricingAddendumText, handleSearchCustomer, } from './customer.handler.js';
-import { handleGetVendor } from './vendor.handler.js';
+import { handleGetVendors } from './vendor.handler.js';
 const wrap = (fn) => {
     return async (args) => fn(args);
 };
@@ -10,5 +10,5 @@ export const handlers = {
     finstack_get_customer_invoices: wrap(handleGetCustomerInvoices),
     finstack_get_customer_pricing_config: wrap(handleGetCustomerPricingConfig),
     finstack_get_pricing_addendum_text: wrap(handleGetPricingAddendumText),
-    vendorproject_find_vendor_contact: wrap(handleGetVendor),
+    finstack_get_vendors: wrap(handleGetVendors),
 };

package/dist/handlers/vendor.handler.d.ts

@@ -1,11 +1,9 @@
-/**
- * Vendor contact directory handlers
- */
 import { type VendorConnection } from '../api/vendor.api.js';
-interface GetVendorArgs {
+interface GetVendorsArgs {
     query?: string;
     connection?: VendorConnection;
     limit?: number;
+    environment?: string;
 }
-export declare function handleGetVendor(args: GetVendorArgs): Promise<unknown>;
+export declare function handleGetVendors(args: GetVendorsArgs): Promise<unknown>;
 export {};

package/dist/handlers/vendor.handler.js

@@ -1,9 +1,11 @@
 /**
  * Vendor contact directory handlers
  */
+import { getClient } from '../api/client.js';
 import { searchVendorContacts, } from '../api/vendor.api.js';
-export async function handleGetVendor(args) {
-    return searchVendorContacts({
+export async function handleGetVendors(args) {
+    const client = getClient(args.environment ?? 'prod');
+    return searchVendorContacts(client, {
         query: args.query,
         connection: args.connection,
         limit: args.limit,

package/dist/tools/vendor.tools.js

@@ -1,7 +1,7 @@
 export const vendorTools = [
     {
-        name: 'vendorproject_find_vendor_contact',
-        description: "Look up WHO to contact at an external vendor or partner — the person to email, call, or get introduced to. This is about CRS's OWN vendors/partners (credit bureaus and data vendors like Equifax, TransUnion, Experian, CIC/Asurint, SentiLink), NOT CRS customers (use the finstack_* tools for customer accounts, billing, and pricing). Use whenever the user asks who to speak to / talk to / contact / reach out to / get an intro to, or who the point of contact or relationship owner is — for a vendor, a product or topic area (e.g. ECM), a role, or a specialty. Examples: 'who should I speak to for new ECM products', 'who is our pricing contact at Equifax', 'who handles compliance at Experian', 'who owns the TransUnion relationship'. Pass the key terms (vendor name, product/topic like 'ECM', role, or specialty) as `query` — it OR-matches across company, contact name, role, notes, location, and specialty tags (pricing, technical, legal, paperwork, champion, compliance, onboarding, sales, support, executive). Each result includes name, vendor, role, email, phone, location, connection degree, and specialties. Omit `query` to list the whole directory. Read-only — it cannot add, edit, or delete contacts.",
+        name: 'finstack_get_vendors',
+        description: "Look up WHO to contact at an external vendor or partner — the person to email, call, or get introduced to. This is about CRS's OWN vendors/partners (credit bureaus and data vendors like Equifax, TransUnion, Experian, CIC, LexisNexis, FICO, SBFE), NOT CRS customers (use the other finstack_* tools for customer accounts, billing, and pricing). Use whenever the user asks who to speak to / talk to / contact / reach out to / get an intro to, or who the point of contact or relationship owner is — for a vendor, a product or topic area (e.g. ECM), a role, or a specialty. Examples: 'who should I speak to for new ECM products', 'who is our pricing contact at Equifax', 'who handles compliance at Experian', 'who owns the TransUnion relationship'. Pass the key terms (vendor name, product/topic like 'ECM', role, or specialty) as `query` — it OR-matches across company, contact name, role, notes, location, and specialty tags (pricing, technical, legal, paperwork, champion, compliance, onboarding, sales, support, executive). Each result includes name, vendor, role, email, phone, location, LinkedIn, connection degree, and specialties. Omit `query` to list the whole directory. Read-only — it cannot add, edit, or delete contacts.",
         inputSchema: {
             type: 'object',
             properties: {

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@crscreditapi/finstack-mcp-server",
-	"version": "0.2.0-fac1a77",
+	"version": "0.3.0-61c51ea",
 	"description": "MCP server for Finstack",
 	"type": "module",
 	"main": "dist/index.js",