Server URL
What you can ask
Once connected, prompts like these work as they are:- “Someone is calling from +1 212 555 0123. Who is it and where is their deal?”
- “Which lenders should I send the ACME Plumbing deal to, and why?”
- “Summarise the bank statements on the Rivera deal: revenue trend, NSFs, open positions.”
- “Show me deals stuck in Missing docs for more than 5 days and draft follow-ups for each.”
- “Send the merchant portal link to the owner of ACME Plumbing.”
- “Log an offer from Northwind on the ACME deal: $70,000 at 1.32 over 9 months, daily payments.”
- “Which advances are renewal-ready this week? List the merchant, lender and paid-in percentage.”
- “What is in the pipeline right now, by stage?”
- “Here is Bizcap’s rate sheet. Add them as a lender with these criteria.”
Ask about…
- Find a business, person or deal by name, email or phone, or trace a document reference back to the lender that received it (
search) - Everything about a deal in one go: stage, business, owners, offers, submissions, documents and recent activity (
get_deal) - A business with its people, deals and advances, including the renewal outlook (
get_business) - Who an unknown caller or sender is, with their businesses and deals (
get_person) - Deals by phase, stage, status, rep, paper grade or how long they have been sitting (
list_deals) - What the bank statements say: month by month, summary, positions and which months are missing (
get_statement_analysis) - Which lenders fit a deal, scored, with every check explained (
get_recommended_lenders) - The offers on a deal, primary flagged, with payback (
get_offers) - Advances that have paid down far enough to renew (
list_renewal_ready_advances) - The pipeline: stages, phases and how many deals sit in each (
get_pipeline) - Whether DataMerch has anything on file for a merchant: defaults, slow pays and other notes from funders, using the workspace’s own DataMerch account (
check_datamerch) - Your lenders, with products, paper grades and approval rates (
list_lenders), or one lender in full with its criteria (get_lender) - Your team, with each person’s id, email and role, so deals can be assigned (
list_team_members) - One team member in full: role, manager or reps, rep code, commission, and every app and CRM permission (
get_team_member), and the permission templates (list_permission_templates)
Do…
-
Open a deal on an existing business or a new one, with duplicate checks (
create_deal) -
Update a deal’s details, including its originator and closer by id or email (
update_deal) -
Move a deal to another stage, mark it funded or mark it dead, under the same rules as the board (
move_deal_stage) -
Submit a deal to lenders; this sends real email or applications (
submit_deal) -
Log an offer a lender made, including a quoted buy rate and its max upsell (
log_offer) -
Make an offer the primary one (
set_primary_offer) -
Ask the merchant for documents by email, text or link; this messages a real person (
request_documents) -
Send the merchant their portal link; this messages a real person (
send_merchant_portal) -
Add a note to a business or a deal (
add_note) -
Create a follow-up task on a business or a deal (
create_task) -
Add a lender from its rate sheet or criteria email (
create_lender), then store its underwriting requirements so matching scores deals against them (set_lender_criteria). Paste the sheet and the assistant maps each line onto the criteria the matching engine checks; anything without a matching field is kept as a rule on the lender or in its notes, so nothing is dropped. -
Rename a lender or retire it (
update_lender,status: inactivekeeps its history), and delete one added by mistake (delete_lender). A lender with submissions, offers, advances, commissions or matched replies can’t be deleted; the assistant marks it inactive instead. -
Add a team member, exactly as Settings → Team does: they’re created in the CRM too, get a rep code, and count against the account’s user limit (
add_team_member) -
Change a team member’s role, manager or reps, rep code, commission, assigned data only, or any app or CRM permission (
update_team_member). Anything you don’t mention keeps its current value.
Agency connection
Agency admins can connect once and work in every account in the agency. On the sign-in screen, choose Sign in with your agency passkey instead of entering an email. The consent screen shows how many accounts the connection covers. An agency connection adds two tools:list_workspacesfinds accounts by name.use_workspacechooses the account to work in. It stays chosen for the connection until you change it.
workspace, so a single request can name the account: “add this lender in Shane’s account.” Actions are recorded in that account’s activity under your name, marked “(agency)”.
Regular connections don’t have the account tools and stay limited to their own account. You need an agency passkey first: open NextLevel MCA from the CRM as an agency admin and add one under Super Admin → Sign-in. Agency connections are listed on the same page under AI connections; Disconnect ends one right away without touching your passkey or other connections.
Connect
Connect from Claude
Add NextLevel MCA as a custom connector.
Connect from ChatGPT
Add it through developer mode connectors.
For developers
Every tool calls the same service code as the REST API with the same request context, so the server can never do anything the API cannot: workspace isolation, role-based field masking and stage rules apply unchanged. The server’s instructions describe the object model and flag which tools have side effects, so assistants orient without trial calls. The sign-in flow and token handling are on the Security page.