Fontes e entidades

As fontes de dados do workspace — APIs OpenAPI, servidores MCP, bancos de dados e produtos Kobana — e as entidades que o portal lê delas: registros, agregações e sincronizações.

Famílias nesta página

Família	Tools	read	write	destructive
integrations — Fontes de dados	19	5	11	3
entities — Entidades	20	10	8	2

integrations

Tool	Tipo	Permissão	Endpoint	O que faz
dashboards_data_sources_list	read	integrations.list	GET /v1/data_sources	List the data sources of the workspace — OpenAPI APIs, MCP servers and read-only databases — newest first, with status, config and operations_count.
dashboards_data_sources_get	read	integrations.show	GET /v1/data_sources/:id	Fetch one data source with its operations (endpoints, tools or tables it can read), each with its fields and whether it is enabled.
dashboards_data_sources_catalog_list	read	integrations.list	GET /v1/data_sources/catalog	List the Kobana products that can be connected as a data source with just a token (key, name, docs, base URLs).
dashboards_data_sources_connect_catalog	write	integrations.create	POST /v1/data_sources/catalog	Connect a Kobana product from the catalog: saves an OpenAPI data source from the spec shipped with the app and tests it.
dashboards_data_sources_analyze_spec	write	integrations.create	POST /v1/data_sources/openapi/analyze	Analyze an OpenAPI spec without saving anything: title, servers, security schemes, suggested auth and the operations that would be imported.
dashboards_data_sources_create_openapi	write	integrations.create	POST /v1/data_sources/openapi	Save an API described by an OpenAPI spec as a data source, import its operations and test the connection.
dashboards_data_sources_create_mcp	write	integrations.create	POST /v1/data_sources/mcp	Save an MCP server as a data source.
dashboards_data_sources_create_database	write	integrations.create	POST /v1/data_sources/database	Save a read-only database (PostgreSQL, MySQL, MariaDB, SQL Server or MongoDB) as a data source; connects and catalogs its tables or collections.
dashboards_data_sources_test_draft	write	integrations.create	POST /v1/data_sources/test	Test a connection before saving it.
dashboards_data_sources_update	write	integrations.update	PATCH /v1/data_sources/:id	Update a data source — name, is_active, and the connection fields of its kind (OpenAPI, MCP or database).
dashboards_data_sources_delete	destructive	integrations.delete	DELETE /v1/data_sources/:id	Delete a data source with its operations and its sync schedule.
dashboards_data_sources_test	write	integrations.update	POST /v1/data_sources/:id/test	Test a saved data source and record the outcome (status, last error); for an MCP server it also refreshes the tool list.
dashboards_data_sources_sync	destructive	integrations.update	POST /v1/data_sources/:id/sync	Queue a sync of every entity fed by the data source (full: true re-reads everything).
dashboards_data_sources_update_schedule	write	integrations.update	PUT /v1/data_sources/:id/schedule	Set how often the data source syncs: a 5-field cron (at most every 5 minutes) and timezone, or cron: null for on demand only.
dashboards_data_sources_replace_spec	destructive	integrations.update	PUT /v1/data_sources/:id/spec	Replace the OpenAPI spec of a data source and re-sync its operations; operations that keep their key keep their settings, the others are removed.
dashboards_data_sources_authorize	write	integrations.update	POST /v1/data_sources/:id/authorize	Restart the OAuth authorization of an MCP data source.
dashboards_data_sources_logs_list	read	integrations.show	GET /v1/data_sources/:id/logs	List the calls a data source made (HTTP requests, database queries), newest first, without headers nor bodies.
dashboards_data_sources_logs_get	read	integrations.show	GET /v1/data_sources/:id/logs/:log_id	Fetch one call of a data source whole: request and response headers and bodies, with secrets masked.
dashboards_data_sources_operations_update	write	integrations.update	PATCH /v1/data_sources/:id/operations/:operation_id	Turn one operation of a data source on or off (enabled).

entities

Tool	Tipo	Permissão	Endpoint	O que faz
dashboards_entities_list	read	portal-config.view	GET /v1/entities	List every entity of the workspace with its fields, source (data source, operation or SQL or join) and sync state.
dashboards_entities_get	read	portal-config.view	GET /v1/entities/:id	Fetch one entity by id: its fields, source, sync mode, owner field and sync state.
dashboards_entities_preview	write	portal-config.update	POST /v1/entities/preview	Call a read operation of a data source (or run a SQL query) and return a sample of records with the entity inferred from them (proposed fields, types, owner).
dashboards_entities_create	write	portal-config.update	POST /v1/entities	Register an entity from a data source operation (or SQL query) with the fields to keep, and queue its first full sync.
dashboards_entities_update	write	portal-config.update	PATCH /v1/entities/:id	Update an entity: name, key, special fields, owner match, sync mode, pagination, sync filters and the field list (matched by key; send the whole list).
dashboards_entities_delete	destructive	portal-config.update	DELETE /v1/entities/:id	Soft-delete an entity and its fields.
dashboards_entities_join_preview	write	portal-config.update	POST /v1/entities/join/preview	Preview a relation between two entities before saving it: how many records match on the given fields and the first combined rows.
dashboards_entities_join_create	write	portal-config.update	POST /v1/entities/join	Register an entity that relates two others (a join) with the fields picked from each, and queue its first sync.
dashboards_entities_join_update	write	portal-config.update	PUT /v1/entities/:id/join	Replace the relation of a join entity and the fields it brings, then re-sync its records.
dashboards_entities_records_list	read	portal-config.view	GET /v1/entities/:id/records	Query the synced records of an entity, with field filters, sort and limit/offset paging (not page/per_page).
dashboards_entities_records_get	read	portal-config.view	GET /v1/entities/:id/records/:record_id	Fetch one synced record of an entity — its values by field key and the record as the source sent it — with the entity.
dashboards_entities_records_clear	destructive	portal-config.update	DELETE /v1/entities/:id/records	Remove every synced record of an entity and reset its sync state, so the next sync reads the source from scratch.
dashboards_entities_aggregate	read	portal-config.view	GET /v1/entities/:id/aggregate	Count, sum, average, min or max over the synced records of an entity, optionally grouped by a field — what KPI and chart blocks show.
dashboards_entities_usage	read	portal-config.view	GET /v1/entities/:id/usage	List the portal pages (draft and published) whose blocks read an entity, with the block types — what breaks if it is removed or its key changes.
dashboards_entities_logs_list	read	integrations.show	GET /v1/entities/:id/logs	List the calls the sync of an entity made to its data source, newest first (method, endpoint, HTTP status, duration).
dashboards_entities_logs_get	read	integrations.show	GET /v1/entities/:id/logs/:log_id	Fetch one call of the sync of an entity whole: request and response headers and bodies (secrets masked when recorded).
dashboards_entities_sync	write	portal-config.update	POST /v1/entities/:id/sync	Queue a sync of one entity from its data source; full: true reads everything and drops what the source no longer has.
dashboards_entities_sync_get	read	portal-config.view	GET /v1/entities/:id/sync	Where the sync of an entity stands: status, last error, last (full) sync time, record count and stats.
dashboards_entities_tenant_syncs_list	read	portal-config.view	GET /v1/entities/:id/tenant_syncs	On an on_access entity, list where each tenant's sync stands (status, records, portal users carrying the tenant ID), most recently accessed first.
dashboards_entities_tenant_syncs_queue	write	portal-config.update	POST /v1/entities/:id/tenant_syncs	Queue one tenant's sync of an on_access entity now (full: true re-reads everything of the tenant).

---

Os campos de cada recurso estão na Referência da API e em dashboards_schemas_get.

Uma tool que você não pode rodar não aparece em tools/list. Se uma daqui não está lá, veja Autenticação.