Lettance account

com.lettancePublished by lettance.comOfficial publisherv1.4.1Updated Oct 30, 2026

Your rental records in your own AI: homes, rent, repairs and renewal proposals. Sign-in required.

The publisher's own server: Lettance

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

Remote MCP endpoint that lets an AI assistant work with your Lettance rental records: homes, rent, repairs and renewal proposals.

What you can do
  • Access your Lettance rental records from within an AI assistant.
  • Review homes and rent details held in your account.
  • Look at repairs and renewal proposals tied to your tenancy.
  • The listing does not name individual tools, so the exact actions available are not documented here.
When to use it
Useful if you are a Lettance tenant or landlord who wants an assistant to look up your rental information, such as rent, repairs or renewal proposals, without switching apps.
Requirements
A remote MCP endpoint at lettance.com, reachable over streamable HTTP. Sign-in is required and authentication is OAuth-based, so you need a Lettance account. No environment variables or headers are declared.
Before you install
The server reads personal rental data, including homes, rent and repair records, so only connect it to an assistant you trust with that information. Sign-in is required and handled through OAuth; check which account you authorize. The listing does not say whether any tools change data.

Installation

In SourceWeft

  1. Open Lettance account in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.lettance%2Faccount/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "lettance-account": {
      "type": "http",
      "url": "https://lettance.com/mcp/account"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

4
  1. v1.4.1LatestOct 30, 2026
  2. v1.4.0Oct 26, 2026
  3. v1.2.0Oct 16, 2026
  4. v1.0.0Oct 15, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Lettance integrations