- Your Postgres
- Your agent
- Your views
- Your plugins
The CRM you can rebuild.
A CRM is a view on a database. Every table in your Postgres is browsable and editable in place, an agent can do anything you can (or bring your own over MCP), and views, layouts and plugins change when you ask, for you or for everyone.
A database client, an agent and a view layer
Three layers on one API. Whatever a person can do in Dataembed, an agent can do too, and both land in the same activity log.
Every table, on connect
Connect a Postgres over verified TLS and every table opens as an object, read-write by default. Values stay real columns: edit cells inline, follow foreign keys in a side panel, import CSV after a dry run, export CSV or JSON.
Query it, chart it, change it
A read-only SQL console, typed aggregates (count, sum, group by) and charts built on them. Schema changes are typed operations, like adding a column or creating a table, that show their SQL before they run.
One agent for every AI job
The side-panel copilot, AI fill over a column, imports found on the web and plugin building all run on one agent on Claude Managed Agents, with web search, web fetch and a sandbox for code.
Undo first
Record edits and view, layout and plugin changes run at once and show Undo, whoever makes them. When an agent asks for what can't be undone, like a delete or a schema change, it waits for a person's approval.
Everyone, or just me
Every view and page layout has an Everyone layer and a Just-me layer. Your tweaks save to Just me and Save for everyone promotes them. Ask the agent for a change and it lands in Just me, live.
Plugins all the way down
The core ships as plugins on the same API. Plugins built inside Dataembed are a UI spec rendered with the app's own components, with a sandboxed frame as the escape hatch, and no server code.
How it works
Connect your Postgres and every table is browsable at once. Dataembed keeps your views, layouts, plugins and an activity log, never a copy of your rows.
- 01
Connect
- 02
Shape
Views, layouts and plugins, for you or for everyone. Ask the agent to change them.
- 03
Enrich
AI fill and imports from the web run as jobs you can watch and cancel.
- 04
Operate
Work in the grid or the SQL console, ask the copilot, or point your agent at /api/mcp.
Bring your own agent
Everything you can do in the app is a tool, built from the API contract. Dataembed's own agent uses the same MCP tools as yours: sign your agent in, or give it a read, write or admin key. What can't be undone waits for a person's approval, whichever agent asks, and every change lands in the activity log under the agent's name.
- activity_comment
- activity_list
- activity_undo
- approvals_get
- approvals_list
- attributes_reorder
- attributes_update
- connected_apps_list
- connected_apps_revoke
- data_sources_get
- data_sources_list
- jobs_cancel
- jobs_get
- jobs_list
- layouts_get
- layouts_update
- objects_get
- objects_list
- objects_reorder
- objects_update
- plugins_create
- plugins_get
- plugins_list
- plugins_list_actions
- plugins_manifest_schema
- plugins_reset
- plugins_run_action
- plugins_update
- records_aggregate
- records_create
- records_delete
- records_get
- records_import
- records_list
- records_related
- records_search
- records_update
- records_update_many
- schema_preview
- sql_query
- views_update
- workspace_describe
- workspace_get
- workspace_leave
- workspace_members
claude mcp add --transport http dataembed https://<your-dataembed>/api/mcp> Which deals closing this month have no next step?
● dataembed - records_list (object: deals)
● dataembed - records_update (object: deals, recordId: 18)
Two deals had no next step; I added one to Globex renewal.