yiaany/mekka
Developer toolsЭта страница переведена автоматически. Технические детали смотрите в оригинале. Открыть оригинал
Experimental source-available SQLite/libSQL backend for human-and-agent-native workflows, with Studio and scoped MCP access.
Обзор
Typed data API · local Auth · object Storage · Realtime primitives · Studio · scoped MCP access. Built for fast local iteration and human-and-agent-native workflows, with local SQLite and authenticated remote libSQL profiles. downloads, installs, builds, starts the backend, and opens Studio at http://127.0.0.1:8082. Mekka explores a compact backend surface for people and agents working on the same application. The current release runs on Bun and supports two SQLite-compatible data profiles: a local Bun SQLite database for development and an authenticated remote libSQL primary for self-hosted deployments. A typed data API, Studio, Auth, policy, migrations, Storage, Realtime primitives, and scoped MCP access ship in the same repository. The project is experimental and targets controlled local development and self-hosted beta evaluation. It does not claim full Supabase or PostgreSQL compatibility. The remote profile does not silently fall back to a project .sqlite file.
README
Показан фрагмент оригинального README. Открыть оригинал.
Why Mekka exists
Mekka explores a compact backend surface for people and agents working on the same application. The current release runs on Bun and supports two SQLite-compatible data profiles: a local Bun SQLite database for development and an authenticated remote libSQL primary for self-hosted deployments. A typed data API, Studio, Auth, policy, migrations, Storage, Realtime primitives, and scoped MCP access ship in the same repository.
The project is experimental and targets controlled local development and self-hosted beta evaluation. It does not claim full Supabase or PostgreSQL compatibility.
What runs today
| Surface | Local profile | Self-hosted libSQL profile |
|---|---|---|
| User data | Bun SQLite in the project data directory | Authenticated remote libSQL over HTTPS |
| Studio | Table Editor, restricted SQL Editor, Authentication, Agent Access | The same supported Studio surface; unsupported upstream routes redirect away |
| Schema and rows | Manifest-backed table, column, index, row, and restricted SQL APIs | The same contracts through the selected remote engine; no local user-data fallback |
| MCP metadata | inspect_schema, migrations, policy summary, constrained query explanation |
The same tools against remote libSQL |
| MCP row data | Explicit opt-in query_rows with mcp:data:read |
Explicit opt-in query_rows against remote libSQL |
Установка
npx mekkaКонфигурация
{
"mcpServers": {
"mekka": {
"type": "http",
"url": "https://mekka.example.com/mcp",
"headers": {
"Authorization": "Bearer <temporary-agent-access-token>"
}
}
}
}