DocJacket

com.docjacketPublished by docjacket.comOfficial publisherv1.0.0Updated Nov 14, 2026

Real estate transaction coordination: deals, key dates, tasks, contacts, documents and client email.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

DocJacket is a remote MCP server for real estate transaction coordination, letting an assistant work with deals, key dates, tasks, contacts, documents and…

What you can do
  • Work with real estate deals and their key dates
  • Track and manage tasks tied to transactions
  • Look up and manage contacts
  • Handle transaction documents
  • Handle client email related to deals
When to use it
Useful for real estate agents or coordinators who want an assistant to help keep transactions on schedule and organized across deals, deadlines, tasks, contacts and documents.
Requirements
A remote MCP endpoint at mcp.docjacket.com over streamable HTTP. OAuth authentication is required; no environment variables or headers are declared.
Before you install
The server requires OAuth sign-in to a DocJacket account and covers client email, contacts and transaction documents, so an assistant may read or act on sensitive client and deal data. No tool list is published, so the exact read and write capabilities are not documented here.

Installation

In SourceWeft

  1. Open DocJacket 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.docjacket%2Fserver/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": {
    "docjacket": {
      "type": "http",
      "url": "https://mcp.docjacket.com/mcp"
    }
  }
}

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

1
  1. v1.0.0LatestNov 14, 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.