---
title: API Reference
description: Map the public HTTP and MCP-facing surfaces of the repo back to the exact files that implement them.
---


This page is the map of the doors into Memory Crystal.
Some doors are MCP tools. Some are HTTP endpoints. Some are knowledge-base doors.

## What this means in practice

This page is not trying to be a full autogenerated API explorer.
It is the index that tells readers:

- which surfaces are public
- where those surfaces live in the repo
- which deeper docs page explains each one

## How it actually works

The most important public-facing backend surfaces are:

- `convex/crystal/mcp.ts`
- `convex/crystal/knowledgeHttp.ts`
- `packages/mcp-server/README.md`
- `mcp-server/README.md`
- `convex/schema.ts`

## Commands / examples

Best next pages:

- [Authentication](/api/authentication)
- [Memory endpoints](/api/memory-endpoints)
- [Knowledge-base endpoints](/api/knowledge-base-endpoints)
- [MCP Server](/integrations/mcp-server)

## Common mistakes

- calling this page “the API spec” when it is really the route map and grounding layer
- documenting endpoints without linking them back to the files that actually own them
- mixing public-safe HTTP/MCP docs with internal-only implementation notes

## Source of truth

Primary files behind this page:

- `convex/crystal/mcp.ts`
- `convex/crystal/knowledgeHttp.ts`
- `convex/schema.ts`
- `packages/mcp-server/README.md`
- `mcp-server/README.md`
