Using MCP with an Org

When you’re a member of a Realastat org, the MCP integration can access either your personal workspace or your org workspace, depending on how you authenticate.

How workspace context works in MCP

The MCP connection uses your active workspace at the time you authorized Claude Desktop. If you authorized while in your personal workspace, Claude sees your personal data. If you authorized while in your org workspace, Claude sees your org’s shared data.

If you switch workspaces in the Realastat app after authorizing, you may need to re-authorize to update the MCP connection’s context.

Connecting to an org workspace

In Realastat, use the workspace picker (bottom of the sidebar) to switch to your org workspace.
In Claude Desktop Settings → Developer, remove and re-add the Realastat MCP server config to force a fresh authorization.
When the authorization window opens, sign in. Realastat will detect your active org workspace and scope the MCP connection to it.

After this, Claude will read and write data from your org workspace:

What are the deals in our org's pipeline?

Add a note to the 456 Oak Ave deal: seller wants to close by end of month

List all contacts our team has added this week

Multiple orgs

If you belong to multiple orgs, you can only have one active MCP workspace at a time. To switch to a different org:

Switch to that org’s workspace in the Realastat app
Re-authorize the Claude Desktop MCP connection

Org-specific MCP use cases

Because org workspaces are shared, MCP is useful for team coordination:

Status updates: “Move all deals where the seller hasn’t responded in 14+ days to Dead”
Cross-team reporting: “Summarize deals by team member who analyzed them”
Shared contact management: “Find all sellers with a follow-up date in the next 7 days”
Pipeline review: “List every deal in Due Diligence with the seller’s phone number”

MCP actions respect your role. If you’re a Member (not Admin or Owner), you can read all org data but some write operations may be restricted.

Setting up MCP for your whole team

Each team member sets up Claude Desktop independently using the same config snippet:

{
  "mcpServers": {
    "realastat": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://realastat.com/api/mcp"]
    }
  }
}

Each person authorizes with their own Realastat account. The MCP server routes each person’s requests through their own permissions; an org member can’t access another member’s personal workspace, and a member can’t delete deals if their role doesn’t allow it.

Claude Desktop Setup Plans & Billing