Top AI Repos — open-source AI, indexed and scored
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
The agent-first database
| Date | Stars |
|---|---|
| 2026-07-31 | 264 |
| 2026-08-06 | 264 |
Today
— stars today
This week
— stars this week
This month
— stars this month
Momentum
0.0
growth rate 0.00%/day
<div align="center"> <img src="readme-cover.png" alt="Dinobase" width="100%" /> # 🦕 Dinobase <strong>The data platform for agents.</strong> Dinobase syncs 100+ sources — APIs, databases, files, MCP servers — annotates your data, and makes it SQL-ready for agents. [](https://pypi.org/project/dinobase) [](LICENSE) [Docs](docs/) · [Getting Started](docs/getting-started.md) · [Connectors](docs/connectors/overview.md) </div> --- ⭐️ star this repo! Thank you for your support! --- **Your agents are flying blind.** Agent stacks built on per-connector tool calls have a structural gap: agents can't `JOIN` across APIs, have no semantic context to interpret field values, and receive paginated JSON that fills context windows. Take the question *"Which customers churned last quarter with declining usage AND open support tickets?"* — it spans three connectors and agents built on tool calls can't answer it reliably. This isn't a model problem. It's an architecture problem. Dinobase is the data platform that fills it. Plug in every source: each connector (SaaS APIs, databases, files, MCP servers) becomes a schema. Agents write one SQL query across all connectors, write data back via SQL mutations with a preview/confirm flow, and get back a single result set. In [benchmarks across 11 LLMs](benchmarks/): **91% accuracy vs 35%, 3x faster, 16-22x cheaper per correct answer.** --- ## Quick start ```bash # recommended — with uv uv tool install dinobase # or with pip pip install dinobase # or with pipx pipx install dinobase ``` ### 1. Connect your data ```bash dinobase add stripe --api-key sk_test_... dinobase add hubspot --api-key pat-... dinobase add linear --api-key lin_api_... dinobase sync # Or parquet files (no sync needed) dinobase add parquet --path ./data/events/ --name analytics # Or databases dinobase add postgres --connection-string postgresql://... # Or any MCP server — auto-discovers read-only tools and syncs them as SQL tables dinobase connector create posthog_mcp --transport stdio \ --command "npx -y @posthog/mcp-server" dinobase sync posthog_mcp dinobase query "SELECT * FROM posthog_mcp.list_projects LIMIT 10" ``` ### 2. Pick your agent interface **Configure your agent** — point your installed Dinobase at your agent in one step: <table> <tr> <td valign="top" width="50%"> **CLI** — for Claude Code, Cursor, Codex, Aider, any agent that runs shell ```bash dinobase install claude-code # Claude Code (~/.claude/CLAUDE.md) dinobase install cursor # Cursor (./AGENTS.md) dinobase install codex # Codex (~/.codex/AGENTS.md) ``` Writes usage instructions to the tool's instructions file. Agents run `dinobase info`, `dinobase describe`, and `dinobase query` directly. </td> <td valign="top" width="50%"> **MCP server** — for Claude Desktop, any MCP client ```bash dinobase install claude-desktop # Claude Desktop (writes config automatically) dinobase serve # any other MCP client ``` `dinobase serve` starts the MCP server on stdio. Run `dinobase mcp-config <client>` to get the JSON snippet to paste into your client's config. </td> </tr> </table> ### 3. Ask your agent a cross-connector question > "Which companies have closed-won deals over $100K but their subscription is past due?" The agent writes the SQL, Dinobase executes it across your connectors, and the answer comes back in seconds. ### 4. Write data back (reverse ETL) Agents can also mutate upstream data via SQL. Every mutation goes through a preview/confirm flow — nothing executes until confirmed. ```bash dinobase query "UPDATE stripe.customers SET name = 'Acme Inc' WHERE id = 'cus_123'" # Returns a preview: 1 row affected, will call Stripe API dinobase confirm <mutation_id> # ✓ Stripe API called (1/1 succeeded) # ✓ Data updated ``` ### 5. Use MCP servers as connectors — and call their
Excerpt of 11,667 characters
Read on GitHubWould you bet a product on this? Bounded 0–100 and slow moving.
matched fp:eea548a85b0c4558, topic:agents