
The Dashboard
The Dashboard gives you a quick health check before diving into a specific collection:- Collections — how many collections you own or have access to
- Total Rows — the combined number of records across all collections
- Queries (7d) — how often agents and users queried your data in the last 7 days
- Activity (7d) — recent write operations on your data
Viewing Collections
Each collection appears as a card showing:- Its name and description
- The number of rows and columns
- The agents linked to it, when applicable
Creating a Collection
1
Open the creation form
Click New Collection (from the Dashboard) or Create (from the Collections page).
2
Name your collection
Enter a name (required) and a description (optional). A clear description helps teammates — and agents — understand what the data represents.
3
Choose how to start
- Empty (add rows later) — creates a blank collection you can fill later, manually or through an agent
- Upload CSV — imports a file and detects the schema automatically (see Importing Data)
4
Create
Click Create. Your collection appears in the list, ready to use.
Opening a Collection
Click any collection card to open its detail page. The header shows the name, description, and size (X rows • Y columns), and the content is organized in tabs:Deleting
Deleting a Collection
1
Open the collection
Click the collection card, or open the ⋯ menu on the card in the list.
2
Delete
Click Delete and confirm.
Deleting Records
To remove individual rows without deleting the collection, select them in the Data tab and use the Delete action — see Working with Data.Settings
The Settings page shows the technical information agents and integrations need:- MCP Endpoint — the URL agents use to access your collections (
/ai-collection/mcp, JSON-RPC 2.0) - Usage — your collections count, total rows, and query volume
Best Practices
One topic per collection
One topic per collection
Keep each collection focused on a single kind of record — deals, contacts, tickets. Mixed datasets are harder to query and produce confusing aggregations.
Write descriptions for your agents
Write descriptions for your agents
The description is visible to agents when they discover your collections. “Q3 2026 sales pipeline, one row per deal, amounts in EUR” tells an agent exactly how to use the data.
Prefer consistent column values
Prefer consistent column values
Aggregations group by exact values. “In Progress”, “in progress”, and “In-Progress” become three different groups — normalize your categories before importing.
Clean up unused collections
Clean up unused collections
Old collections still appear in agent tool listings. Deleting stale datasets keeps agent behavior predictable.
Next Steps
Importing Data
Upload a CSV with automatic schema detection
Working with Data
Browse, sort, and manage records