new.estate — listing drafts

estate.newPublished by new.estateOfficial publisherv1.2.0Updated Oct 31, 2026

Create drafts of personal real estate listings on your new.estate account from a conversation.

The publisher's own server: Publish.fun

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that lets an assistant draft personal real estate listings on a user's new.estate account from a conversation.

What you can do
  • Create drafts of personal real estate listings on the user's new.estate account from a conversation.
  • No tool list is published, so the exact operations available are not documented; the stated scope is listing drafts rather than publishing or managing live listings.
When to use it
Useful when someone wants to turn a conversation about a property into a starting draft of a personal real estate listing in their new.estate account, instead of filling in the listing form by hand.
Requirements
A remote streamable HTTP endpoint at new.estate; no local package or runtime is needed. A new.estate account with OAuth sign-in is required. No environment variables or headers are declared.
Before you install
It writes draft listing content into the user's new.estate account, so review anything created before relying on it. Access is granted through OAuth to the account, so check which permissions are requested. The tool list is not published, so confirm what it can change before connecting.

Installation

In SourceWeft

  1. Open new.estate — listing drafts 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/estate.new%2Fpublish/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": {
    "new-estate-listing-drafts": {
      "type": "http",
      "url": "https://new.estate/api/mcp/publish"
    }
  }
}

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

2
  1. v1.2.0LatestOct 31, 2026
  2. v1.1.0Oct 29, 2026

Score

67% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • 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 Publish integrations