AI Database Querying

Your AI, Your Permissions. Query Anything You're Allowed To.

Because the LLM and database endpoints live in the same system, AI-powered database querying isn't a bolt-on integration — it's a natural consequence of the architecture.

How MCP Tool Calling Works

1

User sends chat request with database endpoint references

2

Adam connects to each endpoint's MCP server and discovers tools

3

Tool definitions sent to LLM alongside the conversation

4

LLM decides whether to call tools based on context

5

Adam verifies RBAC: does this user have access?

6

Tool result fed back into conversation (max 12 iterations)

Same permissions as the user. Always.

RBAC-Scoped AI Access

The AI operates under the exact same permissions as the requesting user. No privilege escalation — because the AI is authenticated through the same identity system.

  • Read-only if user is read-only
  • Invisible endpoints stay invisible
  • Same identity system for AI and data

Natural Language Queries

Ask questions about your data in plain English. AI queries your databases directly through MCP, constrained by your RBAC permissions.

  • No SQL required
  • Context-aware responses
  • Multi-database support

MCP Tool Orchestration

Up to 12 tool passes per turn. AI discovers available tools via cursor-based pagination, calls databases mid-conversation, and feeds results back into the conversation.

  • Namespace-qualified tools — {client}__{tool} for multi-tenant isolation
  • Cursor-based tool discovery with cached snapshots
  • Two tool sources: managed Adam endpoints + user-registered MCP servers

Tool Execution Metrics

Every tool call is instrumented with OpenTelemetry. Track attempts, failures, and latency per tool and per server.

  • Attempt & failure counters
  • Latency histograms
  • Per-tool observability

Conversation Persistence

Conversations stored in Postgres with two modes: persistent for long-running analysis, ephemeral for one-off queries. Full sequence tracking across sessions.

  • Persistent and ephemeral conversation modes
  • SSE streaming with heartbeat keep-alive
  • Resume conversations across sessions

Token Accounting

Prompt and completion tokens tracked per conversation, per user, per organization. Know exactly what your AI usage costs across every provider.

  • Per-conversation token tracking
  • Prompt and completion breakdowns
  • Organization-level usage aggregation

Ready to Connect AI to Your Data?

Join forward-thinking companies using ADAM to unify their AI and database infrastructure. Same auth. Same RBAC. Same API.