Agent instructions
Reusable Markdown instructions, project workflows, and tool notes that agents can retrieve across sessions.
Stop starting over with every AI tool
pumaDB keeps important facts, decisions, preferences, and handoff notes available across ChatGPT, Claude, Codex, and your own agents
Hosted MCP setup
[01] CONNECT MCP
One endpoint.
No database project.
Connect Codex, ChatGPT, Claude, OpenClaw, or any Streamable HTTP MCP client to the same memory. Sign in by email and pumaDB handles OAuth — no infrastructure to provision and no API key pasted into the client. Open the connection guide.
CODEXCHATGPTCLAUDEOPENCLAWANY STREAMABLE HTTP CLIENT
Connect
# Streamable HTTP MCP endpoint
>
https://api.pumadb.ai/mcp
# OAuth discovery and dynamic client registration supported
# Add pumaDB as a hosted MCP server
$
codex mcp add pumadb --url https://api.pumadb.ai/mcp
# Create a custom MCP app
>
Settings / Apps & Connectors / Advanced settings
>
Server URL: https://api.pumadb.ai/mcp
# Add a custom connector
>
Customize / Connectors / Add custom connector
>
Leave OAuth client fields blank
>
https://api.pumadb.ai/mcp
[02] MEMORY HANDOFF
pumaDB memory example
Root cause of the checkout bug: a race in the retry loop. Log it — I'll fix it tomorrow.
Logged against the checkout bug.pumadb.remember("bugs", { id: "checkout", cause: "retry race" })
NEW CHAT · NO HISTORY · NOTHING PASTED
Let's fix that checkout bug.
Picking up your note — the retry-loop race. Here's the patch.← pumadb.query("bugs", { id: "checkout" })
Saved in ChatGPT. Recalled in a new Claude chat. Same pumaDB account, nothing pasted. writes in reads out
[03] WHAT TO REMEMBER
Remember the details agents otherwise lose.
Keep small, structured records that make the next session useful: project facts, decisions, preferences, research, task state, and handoff context.
Project conventions
Repository facts, architecture notes, branch rules, naming patterns, and decisions that should not be rediscovered.
User preferences
Communication style, formatting defaults, review expectations, and other durable preferences keyed by person or workspace.
Research clippings
Sources, summaries, links, comparison notes, and follow-up questions from investigations that continue over time.
Task state
Open threads, blockers, handoff notes, pending commands, and lightweight status records for long-running work.
Reviewed technical references
Resources, code, Markdown, commands, and config examples stored as inert records for review before use.
[04] REST MCP
One memory surface. Two ways in.
Use REST from trusted server-side code, or let authorized agents call the same row operations through hosted MCP. Different doors. Same tables.
For code you trust
Backends, Workers, serverless functions, CLIs, and scripts using bearer API keys.
Bearer keyGET /v1/{table}
POST /v1/{table}
POST /v1/{table}/update_row
DELETE /v1/{table}
For agents you authorize
Agent-facing tools for clients connected to the hosted MCP server with OAuth.
OAuth tokens
remember
query
add
upsert
update_row
delete
One memory surface
same tables · same rows · same limits
[05] PLANS
Free for individuals.
Shared plans for teams.
Personal
For individuals and their agents
$0
Forever · no card
- 20 tables · 1,000 rows per table[ok]
- 25 MB total storage[ok]
- Hosted MCP + REST[ok]
- Version history and restore[ok]
- Viewer and download links[ok]
SKU PDB-P0
COLORWAY: BONE
COLORWAY: BONE
Organization Pro
Shared memory for your organization
$99
/month · per organization
- Everything in Personal[←]
- Shared org tables · admin and member roles[ok]
- Up to 100 team members[ok]
- 50 org tables · 2,500 rows per table[ok]
- 250 MB organization storage[ok]
SKU PDB-ORG99
COLORWAY: SIGNAL
COLORWAY: SIGNAL
Enterprise
Custom memory infrastructure for larger teams
Custom
Annual contract · scoped together
- Everything in Organization Pro[←]
- Custom team member limits[ok]
- Custom storage and table limits[ok]
- Security, procurement, and rollout support[ok]
SKU PDB-ENT
COLORWAY: TEAL
COLORWAY: TEAL
Rate limits and API behavior are identical on Personal and Pro — Enterprise is scoped with us.