Connect Your AI to Funding Machine

Funding Machine ships with a built-in MCP server (Model Context Protocol) — the open standard AI assistants use to talk to external systems. Connect Claude, ChatGPT, or any MCP-capable agent and it can look up your applicants’ credit summaries, stored credit reports, funding plans, and deal stages directly, without copy-pasting.

Access is read-only and scoped to your account. Your AI can look up data, but it cannot change anything, submit deals, or touch billing.

What your AI can do

Once connected, your assistant has these read-only tools. Full credit-report JSON and PDF access requires a separate permission; the other tools remain available with standard read access.

Tool	What it returns
List locations	The CRM locations this connection can access. Agency connections use these location IDs with the other tools
Search contacts	Find CRM contacts by name, email, or phone, and get the contact IDs the other tools use
Credit summary	Latest credit score, DTI, underwriting decision, estimated funding ranges, and credit-repair flags for an applicant, with no raw report data or PII
Underwriting result	The full stored underwriting outcome: decisions, status codes, funding ranges, workflow path, and manual-review flags. Never re-runs underwriting
Funding plans	The ordered funding plan: recommended lenders and cards, expected amounts, approval probability, and next steps
Deal stage	Where an applicant sits in your pipeline right now, including stage, status, value, and last activity
Applicant pipeline	The contacts your team is tracking, most recently updated first, with follow-up status and upcoming appointments
Dashboard stats	Aggregate numbers for your account over a recent window: report volume, average score, decision breakdown, and funding totals
Credit report JSON	The full stored credit-report data for an applicant — scores, tradelines, inquiries, and public records exactly as saved — with Social Security numbers redacted. Latest report by default, or an exact report by requestId. Never triggers a new bureau pull
Credit report PDF link	A short-lived, pre-authorized download link (about 10 minutes) for an applicant’s stored credit-report PDF. Some migrated/legacy reports have no renderable PDF — the JSON tool still returns their stored data
Applicant next steps	The ordered conversion checklist composed from stored underwriting, funding-plan, agreement, application, pipeline, and strategy signals

Agency connections also have Resolve location to match an operator’s linked Slack channel or exact identity to one CRM location. It returns the location ID, stored name (or null), and matching signal. Confirm the name with the operator before reading records; ambiguous matches are returned as candidates. Example prompts once connected:

“Find the contact named Maria Lopez and give me her credit summary.”
“Summarize the funding plan for this applicant and draft a follow-up email.”
“Which applicants need follow-up this week, and who has an appointment set?”
“How did our funding volume trend over the last 90 days?”

Step 1 — Create an API key

In Funding Machine, go to Settings → Integrations
Under AI Integration (MCP), click Create key
Name the key after where you’ll use it (e.g. “Claude Desktop — ops team”)
Leave Allow full credit reports off for standard lookups and support. Enable it only for an assistant you trust with full bureau data and applicant identity information.
Copy the key immediately. For security, the full key is shown only once. If you lose it, revoke it and create a new one.

Keys look like fmk_... and are scoped to your account only. You can create up to 10 active keys and revoke any of them at any time from the same screen. Existing keys with only read continue to access summaries, funding plans, and diagnostics, but cannot read raw credit-report JSON or download report PDFs. To enable report access, create a replacement key with Allow full credit reports enabled, update your assistant, and revoke the old key. OAuth connections must explicitly request and receive consent for both read and credit_reports; refresh alone does not add permissions. Requesting credit_reports without read is rejected during client registration and authorization.

Treat API keys like passwords. Anyone with the key can read your applicants’ funding data. Never share keys in email or chat, and revoke a key right away if you think it leaked.

Step 2 — Connect your assistant

Your MCP endpoint is:

https://marketplace-app.myfundingmachine.com/api/mcp

(The exact URL is also shown on the Settings → Integrations screen.)

Claude (claude.ai and Claude Desktop)

Claude can connect two ways. Both use the endpoint URL above, and both end with read-only access to your account only. Option A: sign in with OAuth (works on a phone):

In Claude, open Customize → Connectors, click + Add → Add custom connector, enter a name and the endpoint URL above, and leave Request headers empty
Click Connect. Claude opens a Funding Machine page in the same window
Paste a Funding Machine API key (fmk_...) and tap Continue. The key is checked once. It is not stored in the browser and is never shown back on the page
Review what Claude is asking for: the key’s name, the Location it will reach, and the permissions. If you used an agency key, choose the Location to connect
Tap Allow (or Deny to cancel). You return to Claude and the Funding Machine tools appear in new conversations

Claude gets its own short-lived access that never exceeds the key. It gets only the permissions the key has, and only for one Location. Full credit-report access is granted only if Claude asked for it, the key has Allow full credit reports on, and you approve it. Revoking the key disconnects Claude too. The key does not sign you in to Funding Machine. If you’re working at a computer with your CRM open, you can skip the key on that page. In Funding Machine inside your CRM, go to Settings → Integrations and, under AI Integration (MCP), click Sign in for AI connections. The Claude page then continues on its own and shows what Claude is asking for. That connection is tied to the account you were signed in to.

If the page says the form or approval expired, enter your key again. It shows Too many attempts after repeated tries; wait a few minutes. A key that was revoked or mistyped is refused, and nothing is shared.

Option B: a fixed API key in the request headers:

Open Customize → Connectors, click + Add → Add custom connector, and enter a name and the endpoint URL above
Under Request headers, add Authorization with the value Bearer fmk_YOUR_KEY_HERE
Save. Claude sends that key on every request, so there is no sign-in step

On Team and Enterprise plans, a header added by an admin is shared by everyone who uses the connector, so use a key you are comfortable sharing that way. For Claude Desktop versions that use a JSON config file instead, add:

{
  "mcpServers": {
    "funding-machine": {
      "type": "http",
      "url": "https://marketplace-app.myfundingmachine.com/api/mcp",
      "headers": {
        "Authorization": "Bearer fmk_YOUR_KEY_HERE"
      }
    }
  }
}

ChatGPT

Open Settings → Connectors (requires a plan with custom connector support)
Click Create under custom connectors
Enter the endpoint URL and select Bearer token authentication
Paste your fmk_... key and save
Enable the connector in a conversation from the composer’s tools menu

Custom agents and frameworks

Any MCP client that supports the Streamable HTTP transport works. Pass the API key as a Bearer token:

import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js";

const transport = new StreamableHTTPClientTransport(
  new URL("https://marketplace-app.myfundingmachine.com/api/mcp"),
  {
    requestInit: {
      headers: { Authorization: "Bearer fmk_YOUR_KEY_HERE" },
    },
  },
);

const client = new Client({ name: "my-agent", version: "1.0.0" });
await client.connect(transport);
const tools = await client.listTools();

Managing access

Everything is controlled from Settings → Integrations:

See every key — its name, when it was created, and when it was last used
Revoke instantly — a revoked key stops working on the next request
Audit trail — the “Recent agent activity” list shows every tool call your connected AIs have made, so you always know what they looked up
Permissions — full credit reports are optional. Replace a key to change its permissions; revoke the old key after updating your assistant

Limits and security

Read-only: no tool can create, modify, or delete anything. The credit-report tools return only stored reports — they never start a new bureau pull and never re-run underwriting
Account-scoped: a key only ever sees data for the account it was created in
Report permission: raw credit-report JSON and PDF downloads require both read and credit_reports. Standard read access still includes credit summaries and underwriting results
Masked audit arguments: emails, search text, and other personal fields are masked in new MCP audit entries. Record IDs and structural selectors remain available for troubleshooting
Rate-limited: 60 requests per minute per key, so a runaway agent loop can’t hammer your data
SSNs are always redacted: the credit report JSON tool strips Social Security numbers before anything is returned. The report tools do return the rest of the applicant’s bureau data (name, address, tradelines), and the PDF link downloads the full report — so only connect assistants you trust with applicant data
Short-lived PDF links: report download URLs expire after about 10 minutes, so a link pasted into a chat can’t be reused later
Hashed at rest: we store only a one-way hash of your key — nobody, including support, can recover the full key after creation

Create one key per assistant or teammate instead of sharing a single key. When someone leaves or a tool is retired, revoke just that key without disrupting everything else.

Getting Started

Funding

Prospecting

Billing

Partners

CRM Platform Guide

API Reference

Staff

7F Fulfillment

Connect Your AI to Funding Machine

Connect Your AI to Funding Machine

What your AI can do

Step 1 — Create an API key

Step 2 — Connect your assistant

Claude (claude.ai and Claude Desktop)

ChatGPT

Custom agents and frameworks

Managing access

Limits and security

​Connect Your AI to Funding Machine

​What your AI can do

​Step 1 — Create an API key

​Step 2 — Connect your assistant

​Claude (claude.ai and Claude Desktop)

​ChatGPT

​Custom agents and frameworks

​Managing access

​Limits and security

Connect Your AI to Funding Machine

What your AI can do

Step 1 — Create an API key

Step 2 — Connect your assistant

Claude (claude.ai and Claude Desktop)

ChatGPT

Custom agents and frameworks

Managing access

Limits and security