Documentation

Connect CNTXT_ to
every AI you use.

One shared, private memory for your organisation. Connect it once per tool, and your AI assistants can recall your context and save new knowledge as you work.

Secure
Connect
Remember
Go further _
Before you start

One endpoint.
One key

Every tool talks to the same CNTXT_ endpoint. Your personal API key identifies you — anything saved with it is yours.

Where your key comes from: your organisation’s admin issues your personal key from the dashboard. It looks like cntxt_k_… — treat it like a password. If it ever leaks, tell us and we rotate it in seconds.
Your endpoint
https://api.getcntxt.com/functions/v1/cntxt/mcp

CNTXT_ speaks MCP — the open Model Context Protocol — so it works with any client that supports custom connectors or MCP servers. The four most common setups are below.

Per-client setup

Connect your tools

Replace YOUR_KEY with the personal key your admin issued you. Each connection takes about a minute.

01

Claude

Web, desktop and mobile — added once as a custom connector, available everywhere you use Claude.

  1. Settings → Connectors → Add custom connector
  2. URL — your endpoint with your key attached
  3. Leave the OAuth fields empty → Add. Claude will show the CNTXT_ tools.
Connector URL
https://api.getcntxt.com/functions/v1/cntxt/mcp?key=YOUR_KEY
02

Claude Code

One command in your terminal registers CNTXT_ for every Claude Code session.

Terminal
claude mcp add --transport http cntxt https://api.getcntxt.com/functions/v1/cntxt/mcp --header "Authorization: Bearer YOUR_KEY"
03

Cursor

Add the server to ~/.cursor/mcp.json and restart Cursor.

~/.cursor/mcp.json
{ "mcpServers": { "cntxt": {
  "url": "https://api.getcntxt.com/functions/v1/cntxt/mcp",
  "headers": { "Authorization": "Bearer YOUR_KEY" } } } }
04

ChatGPT

Plus or Pro plan, via a developer-mode connector.

  1. Settings → Apps & Connectors → enable Developer mode (under Advanced)
  2. Create → paste the URL-with-key form → no authentication → Create
  3. In a chat, enable the CNTXT_ connector under the tools menu.
Connector URL
https://api.getcntxt.com/functions/v1/cntxt/mcp?key=YOUR_KEY
Standing instructions

Teach your AI
the habit

Connecting gives your AI the memory tools. The block on the right teaches it to reach for them reliably — paste it into each tool’s custom or system instructions.

  • Claude: profile preferences or project instructions
  • ChatGPT: custom instructions
  • Claude Code / Cursor: a rules file (CLAUDE.md, .cursorrules)
Paste into each tool
You have CNTXT_, my organisation's shared memory layer (the `cntxt` tools).

On starting substantive work:
1. Call `memory_core` to load the always-on set.
2. Call `memory_search` with 1–2 queries describing the task. Ignore low-similarity noise.
3. Apply what you find silently — don't recite memories back to me.

Before finishing significant work (or when I say "save to CNTXT_"), write back what a colleague would need tomorrow, using `memory_add`:
- WRITE: decisions + reasoning, new/changed conventions, status changes, gotchas that cost real time.
- DON'T WRITE: session narration, minor fixes, anything already in memory (search first), and never secrets, keys or credentials.
- One self-contained fact per row, max ~2 sentences, understandable with zero context.
- Set `audience`: `org` to share with my organisation (default) · `private` for things only I should see · `open` only for externally safe facts.
- Status rows: find and `memory_delete` the stale status before adding its replacement.
- 0–4 writes per session; more means you're logging, not curating.
- End long sessions by telling me in one line what you wrote (or that nothing was worth it).
The tool roster

What your AI
can now do

Eleven tools across memory, goals and documents. Your AI picks the right one for the moment.

Tool What it does
memory_core Loads your organisation’s always-on facts.
memory_search Finds relevant knowledge semantically.
memory_add Saves a durable fact. You control the audience: org — your whole organisation · private — only you, invisible even to admins · open — safe for external surfaces.
memory_update Edits an existing memory.
memory_list Browses what’s stored.
memory_delete Removes a memory — curation, not just accumulation.
goal_add Adds a goal to your organisation’s goals ladder.
goal_list Lists goals and their current state.
goal_update Updates a goal’s status or detail.
document_search Searches inside your Library documents (PDFs, Word, text) and returns the exact passages, cited by document and page.
document_read Fetches a whole Library document.

One fact per memory, written so a stranger understands it. Save decisions, conventions, statuses and hard-won gotchas — not chat transcripts. When a status changes, delete the stale row and add the new one.

Your data, always yours

Export everything.
Any time

Download everything you can see, any time, as documented JSON. No request forms, no waiting — one command with your own key.

Terminal
curl -H "Authorization: Bearer YOUR_KEY" https://api.getcntxt.com/functions/v1/cntxt/export -o cntxt-export.json

Questions, feedback or a key rotation: dev@exponenture.com

Same knowledge. A brighter future.

Ready to give your AI
a memory?

We’ll help you connect your tools and shape the first memories together.

Let’s talk CNTXT_

Make room for
what you know

Tell us a little about your team. Prepare a short brief for your conversation with Exponenture.

This local site prepares a downloadable brief. Nothing is sent, and no meeting is booked. Your details stay in this page until you close or reload it.