Lendflow

Returns the option and reference values behind Lendflow's tools and dashboard filters, resolving a name or a label into the ID another tool needs: product types, note visibility scopes, placement statuses and decline reasons, funder risk tiers and lender networks, and the industry, geographic, credit score and revenue lookup lists. Those lookup lists make the payload large. list_application_workflow_stages returns one application's stages.

get_options

Returns one lender placement on an application in full, addressed by placement ID, where list_application_placements returns one thin row per placement.

get_placement

Returns the payload one workflow template accepts, stage by stage: the block ids with an example value for every field in each block, and the field names each block requires. That block data is what create_application and update_application take as top-level arguments, and list_workflow_templates returns the template ids.

get_workflow_template_sample

Issues a short-lived API token an MCP app uses to call the Lendflow API as the current user.

issue_app_access_token

Returns the data orchestration templates one underwriting stage declares on an application's workflow snapshot. stage_id comes from list_application_workflow_stages and must name a stage of type Underwriting, so any other stage is rejected. A draft template is listed but cannot be run, which the status field distinguishes.

list_application_data_orchestration_templates

Lists the files uploaded to one application, where list_application_required_documents lists the documents its workflow asks for and whether each is complete.

list_application_files

Returns the offers on one application that have a funder attached, where get_offer returns one offer with its term and closing details.

list_application_offers

Returns the lender placements on one application, newest first, where get_placement returns one placement in full. Placements with no funder attached are excluded.

list_application_placements

Lists the required documents for one application and whether each is complete, where list_application_files lists the files uploaded to it.

list_application_required_documents

Returns the stages defined in one application's workflow snapshot, in the order the application's flow runs them, with no branching information. Which stage the application currently sits on comes from get_application.

list_application_workflow_stages

Returns the statuses and sub-statuses one application can be moved to, each with its name, color and visibility, as defined by the workflow template behind it. update_application_workflow_status takes a status and sub_status from this list. These are status values, not the workflow stages list_application_workflow_stages returns.

list_application_workflow_statuses

Searches applications, with a large set of filters over people, dates, amounts, workflow status, offers, placements, score cards and tasks. get_options lists the values many of those filters accept, and list_funders the funder IDs the offer and placement filters take. Each row is a summary carrying the application name, client, workflow stage, amount and offer, placement and call counts, where get_application returns one application in full.

list_applications

Returns the brand names configured on one client. get_client returns that client in full but carries none of them. create_application takes one of these ids as brand_name_id, and the brand_names filter on list_applications matches the names.

list_client_brand_names

Returns the id and name of each client organization, ordered by name, with optional client-name search and approved and is_funder filters. get_client returns one client in full by ID.

list_clients

Searches the calls, tasks, emails, SMS messages, notes and AI agent sessions recorded across Lendflow, including the notes that create_application_note and create_business_note add. Each row embeds the whole underlying record, down to call transcriptions and summaries and the full text of an email, so a broad search returns a large payload.

list_communication_logs

Returns a summary row per funder, ordered by full_name, with optional search, risk tier, product type, country, area, city, approval and lender network filters, and selected_ids to order chosen funders first. get_funder returns one funder in full by ID.

list_funders

Returns the workflow templates, ordered by name, with nothing of each template's content. get_workflow_template_sample returns the payload a template accepts, and create_application accepts an active template that either the user's own organization owns or Lendflow publishes to every organization.

list_workflow_templates

Renders an interactive app the user can drop files into to upload documents to an application.

show_upload_application_documents_app

Updates one application's Application-stage block data, tracking tokens, UTM parameters, client tracking token or brand, and moves it between workflow stages. Block data is passed as additional top-level arguments keyed by block id, such as business or personal, and get_application_workflow_sample gives the block ids and field names the application's own workflow snapshot accepts. Stage movement has three forms, where move_to_next_stage advances one stage, rollback returns to the previous stage, and move_to_stage_id jumps to a chosen stage by passing through every stage in between with force applied and no validation. The application must already have a workflow snapshot. Stage movement can start a data orchestration run, and an orchestration run, whether started that way or by data_orchestration_template_id, makes billable third-party bureau calls. A data_orchestration_template_id the requester is not permitted to run, or that cannot run against this application, is rejected. A submitted note saves even when notes comes back empty, which happens when the requester may not read the deal's notes.

update_application

Overwrites the workflow status and sub-status on one application's workflow snapshot, leaving the application's own status column untouched. Omitting sub_status clears any existing sub-status, and every call stamps the status update time and resets the status color, so repeating identical values is still a write. Values are not checked against the workflow template's configured statuses that list_application_workflow_statuses lists, and an application with no workflow snapshot is rejected.

update_application_workflow_status

Sets the status of one lender placement belonging to a given application. It requires the ID of a placement-type stage from that application's current workflow, and a decline reason when the status is Declined. Declining also retracts that placement's offers, and no status change submits anything to the funder, while repeating the same values leaves the placement unchanged.

update_placement_status