A2me MCP Server

A2Me MCP Server

v1 · read-only. A Model Context Protocol server that exposes read-only, privacy-redacted family-context tools for the A2Me family social platform — so assistants like Claude, ChatGPT, or KAI can answer "when is mom's birthday?" or help write a message to grandma, scoped to your own family.

Hosted at https://mcp.a2me.app/mcp and used in production for A2Me's Connect a2me feature.

Connect from an AI assistant

In Claude or ChatGPT, add a custom connector using the URL:

https://mcp.a2me.app/mcp

You'll be sent through OAuth to sign in to A2Me and grant read-only access; the assistant then has family-aware context scoped to your account.

Run it locally

npm install
npm run dev        # stdio transport, mock data by default

It runs on stdio by default (for local MCP clients) and supports a remote HTTP transport (MCP_TRANSPORT=http) for the hosted deployment. By default it uses mock data (A2ME_USE_MOCK=true); set A2ME_API_URL + A2ME_USE_MOCK=false to call a real API. See .env.example.

Available Tools

Example Scenarios

1. "Help me write a birthday card for my sister"

   • find_family_member → resolves "my sister" to Sarah Walker
   • get_birthday_card_context → returns interests (painting, hiking, coffee), tone suggestions

2. "When is grandma's birthday?"

   • answer_family_date_question → returns Margaret Walker's birthday (November 8)

3. "What's been happening in the family?"

   • get_recent_family_activity → returns recent posts, photos, events

4. "Help me write a thank you message to my dad"

   • get_message_context_for_person → returns Robert Walker's context, interests, suggestions

5. "Who's in my family?"

   • get_family_members → returns all family members with relationships

6. "What events are coming up?"

   • get_upcoming_family_dates → returns upcoming birthdays, anniversaries, events

Architecture

┌─────────────────────────────────────────────────────────┐
│                    MCP Client (LLM)                       │
│              (Claude, ChatGPT, KAI, etc.)                │
└───────────────────────┬─────────────────────────────────┘
                        │ stdio (MCP Protocol)
┌───────────────────────▼─────────────────────────────────┐
│                  A2Me MCP Server                          │
│  ┌─────────────────────────────────────────────────┐    │
│  │              Tool Registry (9 tools)              │    │
│  └──────────────────────┬──────────────────────────┘    │
│                         │                                │
│  ┌──────────────────────▼──────────────────────────┐    │
│  │         Family Context Resolver                   │    │
│  │   (fuzzy matching, relationship resolution)       │    │
│  └──────────────────────┬──────────────────────────┘    │
│                         │                                │
│  ┌──────────────────────▼──────────────────────────┐    │
│  │            A2Me API Client                        │    │
│  │   (currently mock, future: real HTTP calls)       │    │
│  └──────────────────────┬──────────────────────────┘    │
│                         │                                │
│  ┌──────────────────────▼──────────────────────────┐    │
│  │            Auth Context                           │    │
│  │   (currently mock, future: OAuth/Firebase)        │    │
│  └─────────────────────────────────────────────────┘    │
└─────────────────────────────────────────────────────────┘
                        │ (future)
┌───────────────────────▼─────────────────────────────────┐
│                   A2Me REST API                           │
│               (kinnectd-api service)                     │
└─────────────────────────────────────────────────────────┘

Authentication

Currently uses mock authentication — always returns an authenticated user ("Alex Walker") for local development.

Future production integration:

• OAuth2/Firebase token validation via A2Me API
• Token passed via MCP session context or environment
• Per-user data isolation (users only see their own family)

Required A2Me API Endpoints (Future)

Development

npm run dev        # Run with tsx (hot reload)
npm run build      # Compile TypeScript
npm run test       # Run tests
npm run test:watch # Watch mode
npm run lint       # ESLint
npm run format     # Prettier
npm run check      # Type check only

Privacy Design

This server is designed to be privacy-first:

• No email addresses, phone numbers, or physical addresses are ever returned
• Birthdays are shown as month-day only (no birth year)
• No financial or health information
• All data scoped to the authenticated user's family only
• Managed accounts (children) have additional protections

Tech Stack

• Runtime: Node.js 20+
• Language: TypeScript (strict mode)
• MCP SDK: @modelcontextprotocol/sdk
• Validation: Zod
• Testing: Vitest
• Transport: stdio (standard MCP transport)

License

Private — Kinnectd / A2Me