Connect MyAurum to your AI assistant.

A Model Context Protocol server that lets Claude Desktop, ChatGPT, and future personal-AI clients read your estate data directly from MyAurum. Read-only. Scoped. Sanitised by default.

✦ Available on the Premium plan.

Generate an API key → Quick start

What this lets you ask your AI

When does my Honda's insurance expire?

List everything held jointly with my wife.

Which properties have society nomination still pending?

What's coming due in the next 30 days?

Summarise my estate for me.

…answered directly from your MyAurum account. No copy-paste, no manual context.

Quick start

Generate an API key

Open MyAurum → Settings → Developer access → + Generate new key. Name it something memorable like "Claude Desktop". The plaintext key — starting with mya_pk_ — is shown exactly once. Copy it now.

Install Node.js

If you don't already have it, download from nodejs.org. Node 20 or newer.

Add MyAurum to Claude Desktop

Open Claude Desktop's developer config (Settings → Developer → Edit Config) and paste in the config below. Replace mya_pk_YOUR_KEY_HERE with the key you copied in step 1.

Show config snippet

{
  "mcpServers": {
    "myaurum": {
      "command": "npx",
      "args": ["-y", "@myaurum-app/mcp-server"],
      "env": {
        "MYAURUM_API_KEY": "mya_pk_YOUR_KEY_HERE"
      }
    }
  }
}

Restart Claude Desktop

MyAurum should appear in your MCP servers list. Try asking: "What's in my MyAurum estate?"

Available tools

Eight read tools today. All descriptive — they report on your data without recommending actions.

Tool	What it does
list_properties	Real estate, vehicles, watches, artwork. Filter by sub-category or holder.
get_property	Full detail on one property — including the complete bill payment history (property tax, society maintenance).
list_records	Financial records — FDs, MFs, bonds, PPF, NPS, EPF, insurance policies.
get_record	Full detail on one financial record.
list_items	Precious-metal holdings — coins, bars, jewellery. Filter by metal or holder.
get_upcoming_renewals	Everything coming due in the next N days — insurance, PUC/fitness, property tax, society dues, FD maturities.
get_overdue_bills	Anything currently overdue across the estate.
get_estate_summary	High-level summary — counts and totals by category, gaps (missing nominees, unfiled society nominations).

Scopes

Every key carries a list of scopes. The standard set lets the consuming AI read the high-level data needed to answer most questions:

read:property read:records read:items read:people read:summary

Opt-in: full PII

By default, encrypted PII fields — addresses, policy numbers, lawyer contacts, tenant details — come through as readable placeholders like [Policy number on file]. The AI gets enough context to talk about them ("your insurance is on file, expires Aug 30"), but the raw identifier stays inside MyAurum.

If you want the AI to see the full data — for example, to draft an email that quotes the policy number — tick "Allow full data access" when generating the key. The key then carries the additional scope:

read:full_pii

Use this only with AI clients you trust. Each key's PII state is shown in the Settings list with a clear FULL DATA or SANITISED chip.

Privacy

The MCP server stores nothing. Each tool call flows through to the MyAurum API and the response goes back to your AI client.
Your API key never touches our servers as plaintext — we hold only a SHA-256 hash for validation. If you lose your key, revoke it and generate a new one.
API keys are read-only in v1. Writes (recording a bill payment, adding a property) require the app. OAuth with write scopes comes in a later release.
Revoke any key at any time from MyAurum → Settings → Developer access → Revoke. Takes effect immediately.

A note on advice. MyAurum reports on your data — it does not give investment advice or make recommendations. The consuming AI is responsible for what it does with the data. If your AI client suggests buying or selling something based on what it sees, that's its interpretation, not ours. See our terms.

Help

Questions, integration requests, or bug reports — [email protected].