KumaAnalytics

MCP setup guide

Connect an approved AI client in five steps.

A guided walkthrough of the hosted MCP connection: what to confirm before you start, how to scope access, how to configure your client, and how to verify that results match your underwriting engine.

Get MCP AccessBack to MCP overview

Before you start

What you need in place.

Setup takes about ten minutes. Most issues come from missing prerequisites rather than the configuration itself.

MCP access begins with the MCP Access plan. Every screenshot below is an illustrative product view; your dashboard may differ slightly as the platform evolves.

  • An active MCP Access, Team, or Enterprise plan
  • Organization admin or owner permissions in Deal Screen
  • A saved buy box so screening results reflect your investment policy
  • An AI client that supports remote MCP connections

Guided setup

Step by step, with screenshots.

Complete the steps in order. Each one ends with a short checklist you can verify before moving on.

01

Confirm your plan includes MCP access

Open Settings → Plan and confirm the MCP connection is enabled. If you are on Starter or Pro, upgrade to MCP Access first — the connection cannot be created without it.

  • MCP connection shows as Enabled
  • Monthly analysis allowance is sufficient for automated runs
  • Underwriting model version is noted for your records
app.kumadealscreen.com

Plan & usage

MCP Access · Active

Analyses used

38 / 150

MCP connection

Enabled

Model version

v2026.06

Settings → Plan: MCP access is enabled on the MCP Access plan and above.
02

Create a scoped MCP connection

In Settings → MCP, create a connection for each AI client you plan to approve. Name it after the client and team, choose the organization it can read, and enable only the tools that team needs.

  • One connection per AI client, never a shared token
  • Tool access limited to what the workflow requires
  • Copy the server URL and token — the token is shown once
app.kumadealscreen.com

New MCP connection

Connection name

Acquisitions — Claude Desktop

Organization

Kuma Capital Partners

Server URL

https://mcp.kumadealscreen.com/v1

Access token

kds_mcp_live_••••••••••••••••4f2a

Enabled tools

screen_commercial_dealcalculate_maximum_offeranalyze_downside_casecompare_dealsgenerate_investment_memolist_due_diligence_questions
Settings → MCP → Create connection: scope the key to an organization and a tool set.
03

Add the connection to your AI client

Paste the server URL and bearer token into your client's MCP configuration, then restart the client so it reloads the server list. Store the token in your password manager or secret store, not in a shared document.

  • Token stored as a secret, not committed to a repository
  • Client restarted after editing the configuration
  • Connection labeled clearly for auditability
claude_desktop_config.json

MCP client configuration

{
  "mcpServers": {
    "kuma-deal-screen": {
      "url": "https://mcp.kumadealscreen.com/v1",
      "headers": {
        "Authorization": "Bearer kds_mcp_live_…"
      }
    }
  }
}
Paste the connection block into your AI client's MCP configuration file.
04

Verify with a test screen

Ask the client to run a quick screen on a known deal. Compare the returned maximum bid, DSCR, and cash-on-cash figures against the same deal screened in the dashboard — they should match exactly.

  • Tool list matches the tools you enabled
  • Results match a dashboard screen of the same deal
  • Run appears in your usage history with a model version
AI client — connected tools
Connected to Kuma Deal Screen · 6 tools available
screen_commercial_deal — ready
calculate_maximum_offer — ready
analyze_downside_case — ready

Test prompt

“Run a quick screen on a 24-unit multifamily at $4.2M, 5.6% cap, using our standard buy box.”

Returned

Maximum bid $4.08M · Base DSCR 1.31x · Downside DSCR 1.24x

A successful connection lists your enabled tools and returns a signed test result.
05

Roll out with controls in place

Once verified, extend access to the rest of the acquisition team using role-based permissions. Review usage history monthly, and rotate tokens whenever team membership changes.

  • Permissions reviewed per role
  • Usage and saved analyses reviewed monthly
  • Tokens rotated on personnel changes
Treat MCP tokens like production credentials. Rotate them on personnel changes, keep one connection per client, and review usage history so every automated run stays attributable.

Troubleshooting

If something does not connect.

The client cannot see any tools.

The token is usually missing the Bearer prefix, or the client was not restarted after the configuration change. Re-check the Authorization header and restart the client.

Some tools appear but others are missing.

Tool availability is governed by plan and connection scope. Open Settings → MCP and confirm the missing tools are enabled on that specific connection.

Results differ from the dashboard.

Confirm the connection is scoped to the same organization and that the buy box in use is the one you expect. Results are versioned, so compare the model version on both runs.

Requests are being rejected.

You may have reached your monthly analysis allowance or the token may have been rotated. Check usage in Settings → Plan and issue a new connection if needed.

Contact supportReview security and access controls

Important disclaimer

What the MCP is, and is not.

The MCP is a workflow and decision-support product. It does not provide investment, lending, tax, legal, appraisal, or financial advice. Users remain responsible for validating data, assumptions, and investment decisions.

Ready to connect your AI workflow?

Start on the MCP Access plan and run your first automated screen the same day.

Screen a DealSee a Sample Analysis