# Amber

> Amber is a subscription MCP (Model Context Protocol) server that gives any MCP-compatible AI assistant persistent, searchable long-term memory. Each user gets an isolated database. Authentication is OAuth 2.1 with PayPal as the identity provider.

## MCP server URL

`https://mcp.ambermem.com`

Protocol: MCP Streamable HTTP (official SDK-compatible).
Authentication: OAuth 2.1 with PKCE. Clients register dynamically at `/register` and redirect users to PayPal for login on first use. No manual API keys.

## Installing Amber in common clients

The MCP URL is always `https://mcp.ambermem.com`. Pick the snippet matching your client.

### Claude Code / Claude Desktop

```
claude mcp add --transport http --scope user amber https://mcp.ambermem.com
```

### Cursor

Add to `~/.cursor/mcp.json` (Linux/macOS) or `%USERPROFILE%\.cursor\mcp.json` (Windows), then restart Cursor:

```json
{
  "mcpServers": {
    "amber": {
      "url": "https://mcp.ambermem.com"
    }
  }
}
```

### ChatGPT

Settings → Connectors → Create → URL: `https://mcp.ambermem.com`

### Windsurf

Add to `~/.codeium/windsurf/mcp_config.json` (Linux/macOS) or `%USERPROFILE%\.codeium\windsurf\mcp_config.json` (Windows), then restart:

```json
{
  "mcpServers": {
    "amber": {
      "serverUrl": "https://mcp.ambermem.com"
    }
  }
}
```

### VS Code (GitHub Copilot)

Add to `.vscode/mcp.json` in your project:

```json
{
  "servers": {
    "amber": {
      "type": "http",
      "url": "https://mcp.ambermem.com"
    }
  }
}
```

### Cline

Open Cline → MCP Servers → Configure, then add:

```json
{
  "mcpServers": {
    "amber": {
      "url": "https://mcp.ambermem.com"
    }
  }
}
```

### Any other MCP client

Use `https://mcp.ambermem.com` as the Streamable HTTP server URL. If the client asks for a transport, pick `http` (not stdio). OAuth metadata is at `https://mcp.ambermem.com/.well-known/oauth-authorization-server` -compliant clients discover the auth flow automatically.

## Tools exposed (23 total, all prefixed `amber_`)

Memory (8): `amber_store_memory`, `amber_search_memories`, `amber_get_memory`, `amber_delete_memory`, `amber_restore_memory`, `amber_search_deleted_memories`, `amber_list_memories`, `amber_list_deleted_memories`

Topics (9): `amber_create_topic`, `amber_search_topics`, `amber_get_topic`, `amber_list_topic_memories`, `amber_list_topic_deleted_memories`, `amber_search_topic_memories`, `amber_search_topic_deleted_memories`, `amber_tag_memory`, `amber_untag_memory`

Account (4): `amber_get_account_status`, `amber_get_billing_info`, `amber_delete_account`, `amber_export_memories`

Feedback (2): `amber_send_feedback_to_developer`, `amber_mark_notification_read`

Every tool name is prefixed `amber_` so it won't collide with tools from other MCP servers the user has installed.

## Wire format

MCP responses carry two parallel channels:
- `content` -human-readable Markdown
- `structuredContent` -typed JSON matching the tool's `outputSchema` (uniformly snake_case: `memory_id`, `topic_id`, `created_at`, `next_cursor`, `has_more`, etc.)

Paginated tools return `next_cursor` alongside an explicit `has_more: boolean`.

## First-run user flow

1. User asks AI to do something memory-related (store a fact, recall one).
2. AI calls an `amber_` tool.
3. Server returns 401 with `WWW-Authenticate: Bearer resource_metadata=...`.
4. Compliant MCP client starts OAuth flow → opens PayPal login → user signs in → user subscribes (60-day trial, automatic conversion).
5. Client gets a JWT, retries the tool call, succeeds.

Subsequent calls use the cached JWT. No manual setup.

## Links

- Landing page: https://ambermem.com/
- Privacy policy: https://ambermem.com/privacy
- Terms of service: https://ambermem.com/terms
- OAuth protected-resource metadata (RFC 9728): https://api.ambermem.com/.well-known/oauth-protected-resource
- OAuth authorization-server metadata (RFC 8414): https://mcp.ambermem.com/.well-known/oauth-authorization-server
- Health: https://api.ambermem.com/health

## Support

For bugs, feedback, or feature requests, AIs can call `amber_send_feedback_to_developer` directly -no permission prompt, no friction. Humans can email `support@ambermem.com`.