Skip to content

MCP Functionality

The Credence MCP connector lets compatible AI assistants work with your portfolio data in natural language. After you connect and authorize, the assistant uses the same portfolio roles and permissions as your Credence account.

This page describes what the connector can do. For installation steps, see MCP Setup.


What you can do

Your assistant can browse Credence data and create or update supported records within your account's permissions. Available actions depend on the record type and your permissions.

Ask in natural language about records in your portfolio scope, including:

Area What you can look up
Portfolios Portfolio detail and the portfolios you can access
Properties Property records and related context
Property hierarchy Ownership tree of legal entities and physical properties in your portfolios (not units or buildings)
Units Individual units within your properties
Leases Lease terms, status, and related tenancy detail
Rent roll Occupancy and rent-roll rows for your properties
Tenants Tenant records linked to your portfolios
Vendors Vendor detail and vendor lists
Vendor contracts Contract detail, contract lists, and charge information
Payables Payable records and open obligations
Receivables Receivable records and tenant balances
Bank accounts Bank-account records in your portfolios, including balances and account type
Transactions Bank-feed transactions linked to those accounts, including unmatched lines and which payable or receivable a transaction was allocated to
Accounts Credence accounts and customer chart-of-account records
Bundles Journal bundles, their workflow and reversal context, and the ledger lines they contain
Ledger entries Debit and credit lines included when you open a journal bundle
Capital events Capital event detail, funding sources, and uses
Fixed assets The fixed-asset register and individual asset details
Projects and jobs Project and development-job records, including job budgets, budget summaries, cost breakdown structures, and cost codes
Documents Metadata and short-lived view links for individual attachments on records you can access

Creating and updating records

New records use drafts where the record type has a draft lifecycle. Portfolios, properties, units, fixed assets, and document attachments save directly. Updates follow the record's edit permissions and review locks; an invalid update saves no changes. Data outside your scope is preserved.

Workflow submissions, approvals, payment actions, and ledger posting stay in Credence. Payment details and contacts are excluded from these writes. Attachments use separate document actions described below. Creating or updating requires write authorization; see MCP Setup.

Your assistant can create and update portfolios. Creating a portfolio does not automatically give you a role in it; ongoing access follows the normal portfolio-role assignments.

Your assistant can create and update fixed assets within your permissions. Creating an asset takes effect immediately. These actions do not post depreciation or create or change links to founding ledger entries; updates preserve existing ledger history.

For documents, your assistant can upload one file up to 10 MiB to exactly one supported parent: a property, CapEx project, tenant, lease, vendor, vendor contract, payable, receivable, or capital event. Loan contracts are excluded. Supported files are PDF, JPEG, PNG, Excel, Word, Outlook MSG, and EML. Uploads require an assistant that supports file uploads through the connector.

Your assistant can update a document's type, file name, effective date, or legal name. Uploads and metadata updates require permission to both view and change the parent record, including approved records. They preserve the parent's workflow state. Updating metadata cannot replace the file or move it to another parent.

On approved payables, permitted informational edits include invoice references, issued and due dates, payment timing, expense-period dates, notes, and charge payment notes. Contract selection, vendor charges, units, leases, and the received date remain protected because they affect financial attribution, VAT, or currency conversion. On approved receivables, informational edits include the name, notes, due date, and existing charge names. The lease, lease-charge assignments, and sent date remain protected. Amounts, accounts, currency, and accounting periods remain protected for both invoice types. Informational edits do not repost accounting entries or change payment state.

On approved vendor contracts, ordinary editors can update the description, executed date, and existing charge descriptions. On approved capital events, ordinary editors can update the description and notes. Broader edits follow the same elevated permissions and lifecycle rules as the corresponding Credence editor. Pending review, proposed edits, and closed or cancelled states may further restrict editing.

Supplying a charge collection reconciles its accessible rows. Include every accessible row you want to retain; omitted collections stay unchanged. Adding or removing rows requires full edit access, and linked financial records may impose additional restrictions. A request containing both allowed and prohibited changes is rejected in full.

For CapEx projects and Development jobs, your assistant can create drafts and update permitted details. On approved, active records, ordinary editors can update the description and reference ID; broader edits require the relevant permission to edit approved records. Closed records require that elevated permission for edits. Your assistant cannot set approval or activity status.

CapEx current-budget changes preserve budget history and liquidity overrides. Development job budgets are managed separately in Credence; creating or updating job details does not change cost-code budgets.

How lookups work

For most record types, your assistant can:

  • Open a specific record when you name an item, reference an ID, or provide enough detail to match one result
  • Browse an unfiltered list when you want to see what is available in your scope (for example, “list my properties” or “show payables I can access”)
  • Search to narrow results when you want matches by name, reference text, or entity ID (for example, “find lease for Acme Corp” or “search vendors with landscaping”)

For bank-feed transactions, your assistant can also:

  • List unmatched transactions still waiting to be allocated
  • Show how a transaction was allocated to payable or receivable charge items
  • Find transactions allocated to a payable or receivable when you already have that invoice

Use browsing when you want the full set you can access; use search when you already know what you are looking for. Both paths return only data your Credence permissions allow.

When a result represents a record that can be opened in Credence, your assistant can provide a full link to the Credence environment you connected. Unit results link to their parent property because units do not have standalone detail pages.

Many records include attached document IDs. Your assistant can open a specific document by its ID to retrieve its metadata and a fresh view link. Documents do not have a standalone list or search action.

Rent roll is slightly different: your assistant can browse or search rent-roll rows, but not open a single rent-roll record the way it can for leases or properties.


Limitations

  • Many Credence screens, workflows, and reports are not available through MCP.
  • Not all records support creation or updates.
  • Deletion is unavailable through MCP for every record type.
  • Heavy or multi-step analysis may still be easier in purpose-built reports and dashboards.

Support

Credence is not responsible for actions taken by your AI assistant. For connector behavior, access issues, or authorization problems, contact [email protected].