prismera logo

Documentation

Connect AI Assistants

Prismera serves its public API as a Model Context Protocol server. Add it to Claude, Cursor, or any MCP client, sign in with your Prismera account, and work with your lease portfolio in natural language — bounded by your own permissions, and fully audited.

ClaudeCursorAny MCP client

The Server URL

https://api.prismera.ai/mcp

Authentication is OAuth 2.1 — the client discovers the sign-in flow on its own; there is nothing to configure beyond the URL.

CursorOne click

Opens Cursor and pre-fills the server. Confirm the prompt, then sign in.

Add To Cursor
Claude

Choose Add custom connector and paste the URL above.

Open Connectors

Any other MCP client takes the same URL through its own “add server” flow.

Set It Up

  1. 1

    Add a custom connector

    In Claude, open Settings → Connectors → Add custom connector. In Cursor or another MCP client, follow its own “add MCP server” flow — the details below are the same everywhere.

  2. 2

    Enter the server URL

    Name the connector (for example Prismera) and paste the server URL above. If the client asks about an OAuth client ID, choose register one automatically — no manual registration is needed.

  3. 3

    Sign in and allow access

    Your browser opens the Prismera sign-in, then an authorization screen showing exactly what the assistant is requesting. Click Allow Access. You can revoke it at any time by disconnecting the connector.

  4. 4

    Ask

    The tools appear in the conversation and the assistant calls them as needed — listing documents, reading abstracts, pulling rent schedules. If your account belongs to several workspaces, just say which one to use; the assistant can list them.

The Tools

Collections And DocumentsBrowse the collections you can see and the leases, amendments, and supporting documents inside them — filtered by status or kind, or searched across names, tenants, and property addresses, and paged through in full.
Structured AbstractsEvery extracted field with its value, its source passage, its page, and the document in the chain that supplied it. Amendments are folded onto the lease by default, so the assistant reads the terms actually in effect.
Base Rent SchedulesA lease's computed rent timeline with every amendment applied: escalations expanded into real dollar rows, options resolved with their exercise-notice windows, free rent and deferrals reflected.
AttributesRead — and, with the right permission, assign or change — the key/value tags your team puts on collections, statuses, and documents, usually an identifier carried over from another system. Tag a collection with your property code, and the assistant can find that whole package by the code later.
Workspaces And ReferenceThe workspaces your account belongs to, and the complete Prismera API reference on demand when an exact request or response shape is needed.

Reading is the bulk of it: documents, abstracts, and rent schedules cannot be created, edited, or deleted through the connector. The one thing an assistant can write is an attribute — the key/value tag used to cross-reference a record with another system — and only when the signed-in member already holds that permission in their workspace. Everything it reads carries page numbers and per-field provenance, so answers stay verifiable.

Workspaces

Signing in identifies you, not a workspace. If your account belongs to exactly one workspace, every request resolves to it automatically. If you belong to several, the assistant is told to list them and pass your choice with each request — you will see it ask, or you can simply name the workspace in the conversation. Membership is re-checked on every single tool call, so access added or removed in Prismera takes effect immediately, with no need to reconnect.

Access And Control

  • The assistant acts as the signed-in member — it sees exactly what that person can see in the app, and nothing more.
  • Attribute writes additionally require the matching permission in that member’s workspace; a member without it gets an error, not a change.
  • Every tool call is written to the workspace audit trail, marked as coming from the connector.
  • Requests are rate-limited per person.
  • Disconnecting the connector — or removing the member — ends access immediately.

Server-To-Server Instead?

Automated integrations that can't run a sign-in flow can authenticate with a workspace API key as the bearer token — created by a workspace administrator, bound to one workspace, with its own scopes and limits. Sync-style workloads belong on the underlying REST API; signed-in users will find the full reference and key setup inside the app under Docs.

Troubleshooting

Finding the authorization server fails

The client has to reach the server over HTTPS from a network that allows it. Retry, and if it persists, send support the time of the attempt.

A tool answers workspace_required

Your account belongs to more than one workspace. Tell the assistant which one to use — it can list them for you.

A tool answers document_not_found

The id does not exist, or it is not visible to you. The two are deliberately indistinguishable, so that the connector cannot be used to probe for records you cannot see.

A tool answers forbidden on an attribute write

The signed-in member does not hold the attribute permission in that workspace. An administrator grants it in Prismera; nothing changes on the connector.

A tool answers rate_limit_exceeded

The assistant is told how long to wait and will retry. Sustained sync-style workloads belong on the REST API with a workspace API key.

Further Reading

This page is the complete connector reference — everything an administrator needs to evaluate and approve it. Customers signed in to Prismera have more at app.prismera.ai/docs: the full REST API reference, authentication and key management, workspace administration, and product guides for every feature the connector reads from. The assistant can also pull that API reference itself, so it is never guessing at a request shape.

Not On Prismera Yet?

The connector reads the portfolio your team already runs through Prismera. See the platform first — then plug your assistant into it.

Request Access