> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lendflow.com/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP Tools

> Understand the Lendflow tools available to external MCP clients.

Lendflow MCP tools allow an AI client to retrieve information and perform approved actions in Lendflow. Your MCP client discovers the tools and their current input requirements automatically.

Whether you can successfully use a tool depends on:

* Your user role
* Your access to the requested data
* The permissions assigned to your Integration Token
* The features enabled for your account

<Note>
  This guide covers the tools intended for external Lendflow users. Internal employee tools and client-administration capabilities are not documented here, so your MCP client may list a tool that this page does not describe.
</Note>

## Tool Types

**Read tools** retrieve information without changing Lendflow data.

**Write tools** create or update Lendflow data. Review the proposed action and its target before allowing an AI client to run a write tool.

A few tools that feel like reads are marked below as changing data, because serving them can create or update an application's workflow snapshot. Your client may ask you to confirm before running them. None of these changes application data, moves a workflow, or contacts anything outside Lendflow.

## Account and Permission Tools

### `get_current_user`

**Read tool.** Returns the Lendflow user the connection is acting as, including name, contact details, client, roles, and the permissions preset applied to the account. Use it to verify which account and role the MCP connection is using.

Example request:

`Show the Lendflow user connected to this MCP session.`

### `check_permission`

**Marked as changing data.** Checks whether the connected user is allowed to perform up to 25 Lendflow actions in one call. A check reports whether the user may act. It never performs the action.

Example request:

`Check whether I can update this application before making any changes.`

### `get_options`

**Marked as changing data.** Retrieves values configured for your account, including workflow templates you may apply, workflow statuses and stages, note visibility scopes, placement statuses and decline reasons, product types, funder risk tiers, lender networks, and industry, geographic, credit, and revenue lookups.

Pass an application to get the statuses, stages, and underwriting providers permitted on it. Pass a workflow template to get the application fields it accepts. The response is large, so use it when an action depends on a configured value.

Example request:

`Show the workflow statuses available for this application.`

## Application Tools

### `list_applications`

**Read tool.** Finds applications available to the connected user, with filters across people, dates, amounts, workflow status, offers, placements, scorecards, and tasks. Search matches business legal name, application ID, deal ID, or client tracking token. Results are paginated.

Example requests:

* `List my most recently created applications.`
* `Find applications in the Underwriting stage.`
* `Show applications assigned to me.`

### `get_application`

**Marked as changing data.** Retrieves one application with its business, owners, personal information, client, brand, assigned users, stips, signed documents, and workflow snapshot, plus the accepted offer once the deal is funding or closing. Offers and placements are not included.

Underwriting data can be added to the response, which makes an already large result much larger. Ask for it only when you need it.

Example request:

`Show application 12345.`

### `create_application`

**Write tool.** Creates an application through an available workflow template. Required application information depends on the selected workflow and account configuration.

Ask the client to retrieve valid workflow options before creating an application. Creating an application can trigger a workflow's application-started webhook and notification emails.

### `update_application`

**Write tool.** Updates an application's Application-stage fields, tracking tokens, or brand, and can move it through its workflow by advancing a stage, rolling back, or jumping to a chosen stage.

Ask the client to retrieve the current application and valid options before updating it.

<Warning>
  Moving an application into a stage wired to a data orchestration template starts that run, which makes billable third-party data calls. Confirm the target stage before approving.
</Warning>

### `run_application_underwriting`

**Write tool.** Queues one or more available underwriting providers for an application, such as Experian, Ocrolus, and Dun and Bradstreet. It returns an acknowledgement only, with no identifier for tracking the run.

Use `get_options` first to retrieve valid providers and underwriting stages.

<Warning>
  This is a billable data pull. Confirm the application and the provider before approving it.
</Warning>

## Workflow Tools

### `get_workflow_stages`

**Marked as changing data.** Returns the workflow stages available for an application, in the order the workflow template declares them. The response does not indicate which stage the application currently sits on.

### `update_application_workflow_status`

**Write tool.** Updates an application's workflow status and, when applicable, its sub-status. Omitting the sub-status clears any existing one, and every call restamps the status update time, so repeating the same values is still a change.

Use `get_options` with the application ID first to retrieve valid statuses and sub-statuses.

## Offer Tools

### `get_offer`

**Read tool.** Retrieves an offer that the connected user can access, with its detail blocks, placement, funder, product, stips, and the parent application. Responses are large and include application files unless you ask to exclude them.

### `list_application_offers`

**Marked as changing data.** Lists the offers associated with a specific application that have a funder attached, each with its placement, funder, product, stips, and detail blocks. Results are paginated.

Example request:

`Show the offers for application 12345.`

### `list_offers`

**Read tool.** Returns offers on applications where the connected user is the recorded application user. This is a narrow, borrower-facing listing rather than a view of every offer your permissions allow, and by default it returns only offers that have not been viewed.

For a full picture of the offers on a deal, use `list_application_offers`.

## Funder and Placement Tools

### `list_funders`

**Read tool.** Lists accessible funders, ordered by name, with filters for name, risk tier, product type, country and location, approval status, and lender network. Lendflow users see all funders. Other users see their client's linked funder and the linked funders in its lender network.

Use `get_options` to retrieve current funder risk tiers when needed.

Example request:

`Which funders in my lender network take this product type?`

### `list_placements`

**Read tool.** Lists lender placements for a specific application, newest first, each with its status, decline reason, submission method, funder and funder products, responses, files sent, and offer count. Placements with no funder attached are excluded.

Example request:

`Show the lender placements on application 12345 and their current statuses.`

### `update_placement_status`

**Write tool.** Updates the status of a lender placement. A decline requires a decline reason and also retracts that placement's offers. A real status change can fire the workflow's placement-status webhook.

This tool does not submit anything to the funder. It records the status in Lendflow.

Use `get_options` first to retrieve valid placement statuses and decline reasons.

## Notes and Communication Tools

### `create_application_note`

**Write tool.** Creates a note on an application, optionally against one workflow stage. Each call adds another note rather than replacing one, and a non-personal note can fire the workflow's application-note webhook.

Confirm the note content and visibility before approving it.

### `create_business_note`

**Write tool.** Creates a note associated with the business on an application, so it appears on every application sharing that business. A non-internal note is copied to related applications and can fire the workflow's business-note webhook.

Confirm the note content and visibility before approving it.

### `list_communication_logs`

**Read tool.** Retrieves accessible communication history, including calls, tasks, emails, SMS messages, notes, and AI agent sessions, using supported filters. Results are paginated.

## Tool Inputs

MCP clients receive the current input schema directly from Lendflow. The schema tells the client which fields are required and which formats are accepted.

Do not guess IDs or configured values. Ask the client to use `get_options`, `get_workflow_stages`, or another relevant read tool before submitting a write action.

## Paginated Results

Many list tools return one page at a time and report the total separately. When you ask a question that depends on a count, ask the client to read the reported total rather than counting the rows on a single page.

## Why a Tool May Be Unavailable

A tool may be unavailable or an action may fail when:

* Your user role does not allow the action.
* The Integration Token does not include the required permission for the action.
* The capability is not enabled for your account.
* The tool is restricted to internal Lendflow users.

Changing token permissions does not override your user role or data access. Reconnect the client after changing permissions so it can discover the tools again.

## Using Write Tools Safely

Before approving a write tool:

1. Confirm the target application, offer, or placement.
2. Review every proposed value.
3. Retrieve current options when the action uses configured statuses or templates.
4. Confirm note visibility when creating notes.
5. Check whether the action is billable or moves a workflow.
6. Run the action only after the request is unambiguous.

<Warning>
  AI-generated actions can modify Lendflow data and can trigger billable third-party data pulls. Grant only the write permissions required for your workflow and review proposed changes before approving them.
</Warning>

## Next steps

<Card title="Smartviews" icon="table" horizontal href="/lendflow-external/docs/smartviews-overview">
  Smartviews are saved views of the Deals page.
</Card>

<Card title="Using the Deals Page" icon="magnifying-glass" horizontal href="/lendflow-external/docs/using-the-deals-page">
  Search deals and expand offer or placement details.
</Card>