Back to browse

Results for “database(48 found)

GitHub

Lightweight, agent-optimized database CLI with one-shot schema introspection, column profiling, and ERD generation.

6Python
●●●Banger

Dbcli – Database CLI Built for AI Agents

One-shot database profiling beats five MCP tool calls; zero token overhead for agents.

Solve My ProblemShip ItCozy
justvugg
103mo ago
GitHub

Agent-friendly CLI for reading/writing large Markdown files

53TypeScript
●●Solid

Markdown as a Database

Section selectors with descendant, child, and regex matching for agent context.

Big BrainNiche Gem
molefrog
1321mo ago
GitHub

PostgreSQL-compatible SQL, graph, and vector database built from scratch in Rust.

46Rust
●●Solid

Rust Database from Scratch

Unified SQL, graph, and vector engine when Neon and pgvector already split these concerns.

Bold BetBig Brain
ayoubnabil
8527d ago
GitHub

PostgreSQL-compatible SQL, graph, and vector database built from scratch in Rust.

46Rust
●●Solid

Aion a Rust Database

Unifies SQL, graph, and vector data in one Rust engine, but still in early alpha.

Bold BetNiche Gem
K9987plus
601mo ago
GitHub

Cognitive memory database for AI agents — consolidates duplicates, detects contradictions, fades stale memories via temporal decay. Rust, AGPL, ships as library / MCP server / HTTP cluster.

162Rust
●●●Banger

A memory database that forgets, consolidates, and detects contradiction

Vector DBs store memories; this one forgets, consolidates, and flags contradictions like human memory.

Big BrainZero to OneWizardry
pranabsarkar
48332mo ago
GitHub

The first database built to let AI agents think their way to the right answer using structural reasoning, rather than guessing based on vector similarity.

60Rust
●●Solid

Vector databases are the wrong primitive for AI agents

Knowledge graphs beat vector similarity for structured relationship queries.

Big BrainBold Bet
ajainvivek
113mo ago
GitHub

The agent-first data platform

261Python
●●●Banger

I built a database for AI agents

91% accuracy vs 35% for MCP tool calls — SQL JOINs beat per-source API chaining.

Big BrainZero to OneSolve My Problem
Kappa90
12102mo ago