Release Notes

Changelog

Review the new features, improvements, and fixes shipped in each Monospace release.

0.5.0August 5, 2026

Guided onboarding, AWS IAM authentication, and date and time fields

This release adds a guided setup walkthrough for new instances, AWS IAM authentication for RDS and Aurora data sources, first-class filtering and display for date and time fields, audit logs for role and policy changes, and lifecycle endpoints with graceful shutdown.

Set up your instance with a guided walkthrough

Creating your first account leads into a three-step setup: name your workspace and pick its URL, connect a data source, then collect your connection details. Each step can be skipped, and your progress is kept if you reload the page partway through.

The Create a Workspace step of the setup walkthrough, with fields for the workspace logo, its name, and its URL shown against the instance host, alongside a Skip setup action

Shipped byMarc Backes

Shipped byJon Bellamy

Shipped byVicky Chen

AWS IAM authentication for RDS and Aurora

You can now authenticate a PostgreSQL, MySQL, or MariaDB data source to Amazon RDS or Aurora with AWS IAM instead of a database password, configured in the Studio rather than by hand-editing connector config. Choose AWS IAM as the authentication method, supply an AWS region, and either enter an access key pair or let the runtime environment provide credentials — an EC2 instance profile, EKS/IRSA web identity token, ECS task role, AWS SSO, or a shared profile. An optional role ARN is assumed on top of either. Each connection mints a short-lived token, TLS is pinned to verify-full, and the correct regional Amazon RDS certificate authority is trusted from an embedded bundle, so you no longer download the RDS CA PEM and set ssl.ca_cert by hand.

The Add new Data Source form for MySQL with Authentication Method set to AWS IAM, showing the AWS Credentials mode, AWS region, and access key fields

See PostgreSQL and MySQL & MariaDB for connector options.

Shipped byPrzemyslaw Hugh Kaznowski

Shipped byReza Baar

Date and time fields you can filter and format

You can now filter date, time, and date-time fields with calendar and time pickers, and choose how each one renders from Appearance on the field. Dates and date-times show either an absolute value, from short to full length, or a relative one that reads as "5 days ago" with the exact timestamp in a tooltip. Integer columns holding epoch milliseconds are handled as timestamps too, including 64-bit values beyond JavaScript's safe integer range.

A collection filtered on Updated At with the date picker open, showing a calendar, a time field, and a Set to Now action

See Filtering for operators and their request shape.

Shipped byHannes Küttner

Emoji icons for collections and views

You can now set a collection's or a view's icon to an emoji instead of an icon from the library. Pick one from Appearance on a collection, where the icon also takes a background color, or beside the name when you create or rename a view.

Shipped byHannes Küttner

Audit logs for roles and policies

The audit log records role and policy changes: role.create.v1, role.update.v1, role.delete.v1, role.assign.v1, and role.unassign.v1, plus the matching policy.* actions. Policy entries carry the entitlements each change granted and revoked, and assignment entries record the role and user involved. Every action in the audit log now has a readable label and appears in the action filter, including the authentication actions added in 0.4.0.

See Audit Logs for the full list of actions and how to query them.

Shipped byMaxence Maire

Shipped byHannes Küttner

Lifecycle endpoints and graceful shutdown

Every instance serves GET /api/system/live and GET /api/system/ready, both unauthenticated. /api/system/live always returns 200. /api/system/ready returns 200 once startup finishes and the system database responds, and 503 otherwise, with a per-check breakdown of accepting_traffic, startup, and system_db. On SIGTERM or SIGINT the engine marks itself not ready, stops accepting new connections, and drains in-flight requests, forcing exit after a 30-second grace period. Set MONOSPACE_CLUSTER__SHUTDOWN_DRAIN_DELAY to keep serving for a fixed window after readiness starts failing, so an orchestrator can take the instance out of rotation before the listener closes.

Shipped byMaxence Maire

Stricter API names

An API name starts with a letter and contains only letters, digits, and underscores. Introspection derives one for you: unicode is transliterated to ASCII, your workspace's naming convention is applied, and a leading digit is prefixed with n — a source collection named 2024 sales becomes n2024Sales, and café table becomes cafeTable. Existing API names keep working; only names you create or edit are validated.

See API Names for the rule and how names are derived.

Shipped byGaetan SENN

The table layout scrolls smoothly through collections with thousands of items and dozens of columns.
Organization and account settings open as an overlay on top of your current workspace instead of navigating away to separate pages, and the workspace header gains a switcher listing your workspaces.
MONOSPACE_ENABLE_OTEL_EXPORT exports OTLP metrics alongside traces: query duration, in-flight queries, and connection-pool state per data source, plus HTTP request duration and in-flight request count. See Observability.
Filter a collection straight from its table: the column header menu has a Filter… action that seeds a clause on that column, opens the filter bar, and moves you to the operator and value.
Users carry a lastActivityAt field, stamped on every login and token refresh and filterable and sortable like any other field. The workspace Members list shows it as a Last activity column.
Files carry createdAt and updatedAt, both filterable and sortable. Existing files are backfilled with the migration timestamp, so original upload times are not recoverable.
The engine version, and its build revision when available, appear at the foot of the settings sidebars and in the /api/system/info response for authenticated callers.
MCP agents discover the workspace's built-in system database by passing includeSystem to read_data_sources, and can create collections on it without naming a namespace.
New Tabs and Collapsible layout blocks, a Notice block, and a semantic color picker that maps to your theme's neutral, primary, success, info, warning, and error tokens.
Block options across the library carry real labels instead of names derived from their property — modelValue reads as Value, collectionId as Collection, fieldId as Field. Text blocks are edited in place in the block editor.
The block library drops the Image and Button blocks, and input blocks no longer take a color option — set color on the surrounding layout instead.
Adding a data source whose collection names collide with existing collections deduplicates the API names instead of failing.
New fields appear in the order you create them rather than alphabetically.
System collections display as Policies, Roles, and Members instead of their raw API names.
Workspace members settings suggests both active and pending members as soon as you focus the input, marking pending invitees as unavailable.
A workspace cannot be named system or auth, which previously produced a workspace shadowed by engine routes.
A collection with no primary key shows a notice explaining that items cannot be read or written until one is set.
A listing whose primary key you cannot read shows a No Queryable Fields empty state instead of retrying a failing query.

Fixed a tab left idle losing your work — the access token now refreshes at three quarters of its lifetime instead of after it has already expired, and returning to a backgrounded tab triggers a catch-up refresh.
Fixed signing out not ending the session: a refresh landing mid-logout no longer leaves you signed back in on reload, and the previous user's cached data is cleared from the tab.
Fixed _every on a to-many relation ignoring related items whose filtered field is null. Such an item now excludes its parent, so filters that previously matched them return fewer results.
Fixed checkbox multi-select blocks doing nothing when toggled on a field whose value is null, and repeater blocks throwing on a null value.
Fixed the color picker throwing when opened on a field holding an invalid color. The stored value is left untouched until you enter a valid one.
Fixed a password manager's inline control dismissing a modal and discarding what you typed.
Fixed saved views failing to load.
Fixed meta.totalCount on MySQL and MariaDB reads that select more than one field.
Fixed picking a field from the toolbar filter menu appearing to do nothing instead of opening the filter bar.
Fixed a select filter showing an empty row when its stored value is no longer among the field's options. The value now renders and can be cleared.
Fixed the table layout's empty state Add Item and Reset Filters buttons doing nothing.
Fixed search not filtering events in the calendar layout, and switching view or date range waiting out a throttle before fetching.
Fixed an event whose start and end are identical being invisible in week and day views.
Fixed incomplete filter clauses reaching the query, where a half-filled clause skewed results and left an active-filter badge you could not clear.
Fixed reordering columns in the table layout resizing them, and gave the last column a resize handle.
Fixed long collection names truncating in the policy tables.
Fixed the policy editor hiding collections that carry only validation rules, which made those rules unreachable, and stopped the Create Permission picker offering system collections.
Fixed the audit log's Action filter seeding _contains, which rendered the clause incorrectly.
Fixed the override-permissions dialog having no way to back out — it now has Cancel, a close button, and click-outside dismissal.
Fixed field values clearing while the field drawer closes after a successful create.
Fixed the create-workspace form reporting validation errors as you tab through it rather than on submit.
Fixed a full name losing its spaces as you type it in the invite signup form.
Fixed wizard steps flashing a different step during the redirect after creating a space or page.
Fixed staged relation rows that overflow the last saved page offering a next page that cannot load.
Fixed the entitlements drawer showing a bare identifier instead of the space title.
Fixed row actions on a related item sliding in and clipping on the card edge when you hover the row, and made them reachable by keyboard.
Fixed Test Connection throwing on a partially filled data source form instead of showing inline field errors.
Fixed a MySQL or MariaDB connection failing with an unknown authentication plugin error that gave no hint the username may not exist.
Fixed nested rows staying editable in a read-only filter.
Fixed content in a resizable split panel reflowing while the panel animates.
Fixed the loader icon on progress toasts not spinning.
Fixed test fixture blocks appearing in the block library.

0.4.0July 14, 2026

Project to Workspace rename and authentication audit logs

This release renames the core Project resource to Workspace — a breaking change — and adds engine-side audit logging for authentication events, alongside a batch of Studio and API improvements and fixes.

Project is now Workspace

Breaking change. The rename reaches the database schema, so an existing instance will not boot against the old layout. Back up your database, then run the migration below once, directly against your system database, before starting the upgraded instance. It renames the system tables, columns, indexes, and foreign-key constraints; rewrites historical audit actions and invitation payloads; and renames every per-workspace monospace_project_<name>_meta and _data schema to monospace_workspace_<name>_…. The whole script runs in one transaction and takes an ACCESS EXCLUSIVE lock, so run it during a maintenance window.

ROLLBACK;

BEGIN;

SET LOCAL lock_timeout = '10s';

LOCK TABLE
  monospace_system.monospace_projects,
  monospace_system.monospace_project_members,
  monospace_system.monospace_invitations,
  monospace_system.monospace_migrations,
  monospace_audit.audit_logs
IN ACCESS EXCLUSIVE MODE;

-- System tables and columns
ALTER TABLE monospace_system.monospace_projects
  RENAME TO monospace_workspaces;

ALTER TABLE monospace_system.monospace_project_members
  RENAME COLUMN project_id TO workspace_id;

ALTER TABLE monospace_system.monospace_project_members
  RENAME TO monospace_workspace_members;

ALTER TABLE monospace_system.monospace_invitations
  RENAME COLUMN project_id TO workspace_id;

ALTER TABLE monospace_system.monospace_invitations
  RENAME COLUMN project_roles TO workspace_roles;

ALTER TABLE monospace_system.monospace_migrations
  RENAME COLUMN last_project_migration TO last_workspace_migration;

ALTER TABLE monospace_audit.audit_logs
  RENAME COLUMN project_id TO workspace_id;

-- Indexes
ALTER INDEX monospace_system.monospace_projects_id_primary
  RENAME TO monospace_workspaces_id_primary;

ALTER INDEX monospace_system.monospace_projects_api_name_unique
  RENAME TO monospace_workspaces_api_name_unique;

ALTER INDEX monospace_system."monospace_project_members_userId_projectId_unique"
  RENAME TO "monospace_workspace_members_userId_workspaceId_unique";

ALTER INDEX monospace_system.monospace_migrations_last_project_migration_unique
  RENAME TO monospace_migrations_last_workspace_migration_unique;

ALTER INDEX monospace_audit.audit_logs_project_id_idx
  RENAME TO audit_logs_workspace_id_idx;

-- Foreign-key constraints
ALTER TABLE monospace_system.monospace_workspaces
  RENAME CONSTRAINT "MonospaceProject_logo_fkey"
  TO "MonospaceWorkspace_logo_fkey";

ALTER TABLE monospace_system.monospace_workspace_members
  RENAME CONSTRAINT "MonospaceProjectMember_project_fkey"
  TO "MonospaceWorkspaceMember_workspace_fkey";

ALTER TABLE monospace_system.monospace_workspace_members
  RENAME CONSTRAINT "MonospaceProjectMember_user_fkey"
  TO "MonospaceWorkspaceMember_user_fkey";

ALTER TABLE monospace_system.monospace_invitations
  RENAME CONSTRAINT "MonospaceInvitation_project_fkey"
  TO "MonospaceInvitation_workspace_fkey";

-- Handle installations stopped exactly on renamed migrations
UPDATE monospace_system.monospace_migrations
SET last_system_migration = CASE last_system_migration
  WHEN '_20260217_110409_project_settings'
    THEN '_20260217_110409_workspace_settings'
  WHEN '_20260307_000638_project_timestamps'
    THEN '_20260307_000638_workspace_timestamps'
  ELSE last_system_migration
END;

-- Rewrite historical audit vocabulary
UPDATE monospace_audit.audit_logs
SET action = CASE action
  WHEN 'user.join_project.v1' THEN 'user.join_workspace.v1'
  WHEN 'user.remove_project.v1' THEN 'user.remove_workspace.v1'
  ELSE action
END
WHERE action IN (
  'user.join_project.v1',
  'user.remove_project.v1'
);

UPDATE monospace_audit.audit_logs
SET payload = jsonb_set(
  payload - 'project_roles',
  '{workspace_roles}',
  payload -> 'project_roles',
  true
)
WHERE payload ? 'project_roles';

-- Rename workspace metadata/data schemas and repair persisted metadata
DO $migration$
DECLARE
  item RECORD;
  old_data TEXT;
  new_meta TEXT;
  new_data TEXT;
BEGIN
  FOR item IN
    SELECT nspname AS old_meta
    FROM pg_namespace
    WHERE nspname LIKE 'monospace\_project\_%\_meta' ESCAPE '\'
    ORDER BY nspname
  LOOP
    old_data := left(item.old_meta, -5) || '_data';

    new_meta := regexp_replace(
      item.old_meta,
      '^monospace_project_',
      'monospace_workspace_'
    );

    new_data := regexp_replace(
      old_data,
      '^monospace_project_',
      'monospace_workspace_'
    );

    IF octet_length(new_meta) > 63 OR octet_length(new_data) > 63 THEN
      RAISE EXCEPTION
        'Workspace schema name exceeds PostgreSQL 63-byte limit: % / %',
        new_meta,
        new_data;
    END IF;

    IF to_regnamespace(new_meta) IS NOT NULL
       OR to_regnamespace(new_data) IS NOT NULL THEN
      RAISE EXCEPTION
        'Target workspace schema already exists: % or %',
        new_meta,
        new_data;
    END IF;

    EXECUTE format(
      'ALTER SCHEMA %I RENAME TO %I',
      item.old_meta,
      new_meta
    );

    IF to_regnamespace(old_data) IS NOT NULL THEN
      EXECUTE format(
        'ALTER SCHEMA %I RENAME TO %I',
        old_data,
        new_data
      );
    END IF;

    EXECUTE format(
      'UPDATE %I.monospace_namespaces
       SET db_name = CASE db_name
         WHEN $1 THEN $2
         WHEN $3 THEN $4
         ELSE db_name
       END
       WHERE db_name IN ($1, $3)',
      new_meta
    )
    USING item.old_meta, new_meta, old_data, new_data;

    -- Rename persisted entitlement values
    EXECUTE format(
      $sql$
        UPDATE %I.monospace_policies
        SET content = replace(
          replace(
            content::text,
            '"projectMembers:',
            '"workspaceMembers:'
          ),
          '"projectSettings:',
          '"workspaceSettings:'
        )::jsonb
        WHERE content::text LIKE '%%"projectMembers:%%'
           OR content::text LIKE '%%"projectSettings:%%'
      $sql$,
      new_meta
    );
  END LOOP;
END
$migration$;

COMMIT;

The resource you create inside an organization is now a workspace. In the Studio, "Project" becomes "Workspace" everywhere — the navigation selector, settings, members, and invitations. The change is uniform on the wire:

REST and MCP — the workspace-scoped path is /api/{workspace}/… (items, assets, openapi, mcp), and the system endpoints move from /api/system/projects to /api/system/workspaces.
SDK — createClient takes a workspace option instead of project, and the generator config in monospace.config.ts uses workspace too.
Fields and payloads — projectId becomes workspaceId, and invitation project_roles become workspace_roles.
Entitlements — project becomes workspace, projectMembers becomes workspaceMembers, and projectSettings becomes workspaceSettings.
Audit log — user.join_project.v1 and user.remove_project.v1 become user.join_workspace.v1 and user.remove_workspace.v1.

See Organization for the resource hierarchy and REST API for the request shape.

Shipped byRijk van Zanten

Audit logs for authentication events

Monospace now records authentication activity in the audit log: successful and failed logins, logouts, token refreshes, and password reset requests, confirmations, and changes. Each entry captures the actor, their IP address, and the outcome — and failures are recorded without revealing whether an account exists.

See Audit Logs for the full list of actions and how to query them.

Shipped byMaxence Maire

0.3.0July 8, 2026

API request panels and AI tool approvals

This release adds an API Request code panel to every collection, a tool-approval workflow for the AI assistant, many-to-many file fields, and a total-count option for read queries.

API Request Code Panel

Reproducing a Studio view in code meant hand-writing the request. Now every content collection has an API Request panel that turns what you're viewing — your fields, filter, sort, and pagination, or the open item and its values — into ready-to-run SDK and cURL snippets you can copy in one click. Open it from the code button in the header; it docks beside your content on wide screens and slides in as a drawer on narrow ones.

The API Request panel showing an SDK snippet generated from the collection's active fields, filter, and sort, with SDK and cURL tabs

See SDK and REST API for client setup.

Shipped byGuillaume Chau

Shipped byHugo Torzuoli

Shipped byHannes Küttner

AI Assistant Tool Approvals

The AI assistant used to run deletes and schema changes without a checkpoint. Now it pauses first: deleting items or changing the schema surfaces a Tool approval required panel where you approve, deny, or send back a different instruction. Tool inputs and outputs render as readable YAML instead of raw JSON, and approval never grants access beyond your own permissions.

The AI Assistant showing a "Tool approval required" panel for a delete action, with Approve and run and Deny buttons

See AI for the assistant and its tools.

Shipped byRijk van Zanten

Many-to-Many File Fields

A File field held a single file, so attaching several meant modeling a junction collection by hand. Now picking the Multiple Files option when adding a File field creates a many-to-many relation to your asset library from just a field name — the junction collection is generated and hidden for you, and attached files show as thumbnails in the item form and table.

See Data Model for fields and relations.

Shipped byMarc Backes

Total Count for Read Queries

Getting a total count used to mean a second query — or fetching every matching item just to count them. Now you can pass a meta option with totalCount on a read query to get the total number of matching items — ignoring limit and offset — alongside the data in one request. It's a top-level option; nested relation reads don't accept it.

See Get the Total Count for the request and response shape.

Shipped byKirill Bulatov

0.2.1July 3, 2026

Stricter query validation and access fixes

This release tightens API query validation, makes the policy "All" access override grant full access, and fixes Studio issues across permissions, filtering, and the schema visualizer.

Stricter Query Validation

Invalid field selections on a primitive field used to be accepted silently. Now the query engine rejects them: selecting nested subfields on a primitive field — or passing arguments to one — is rejected as an invalid query. Nested selections and arguments still work on relation fields, where they apply.

See Field Selection for valid field, relation, and nested-query syntax.

Shipped byMaxence Maire

Accurate "All" Access Override

A filter left on a single action used to survive the "All" access override, so "All" didn't actually grant full access. Now, in the policy editor, a collection's "All" override grants genuine unrestricted access — it clears any custom per-action filters and opens create, read, update, and delete together.

See Access Control for how policies and collection permissions combine.

Shipped byFlorian Wachmann

0.2.0July 2, 2026

A refreshed Studio, onboarding, and native JSON

This release refreshes the Studio, adds guided onboarding and a project connection screen, moves JSON fields to native JSON, introduces branded data source presets and permission-aware controls, and ships configurable CORS, query-parameter authentication, and anonymous usage telemetry.

Refreshed Studio Design

The Studio interface is restyled from the chrome inward. Project headers, the sidebar, and footers use consistent heights, spacing, and typography. Breadcrumbs now show the item you're viewing on a detail page, and the collection back control is labeled with the collection name.

An item detail page with the breadcrumb showing the current item and a back control labeled with the collection name

Shipped byHugo Torzuoli

Shipped byReza Baar

Shipped byFlorian Wachmann

Onboarding

New instances walk you through first-run setup. When no user exists yet, Monospace prompts you to create the first administrator — name, email, password, and terms acceptance. When an administrator was provisioned automatically, you confirm your details and accept the terms the first time you sign in.

The first-run screen prompting you to create the first administrator account

Shipped byMarc Backes

Connect to Your Project

Connecting a client to a project used to mean assembling the base URL and minting a key by hand. A new connection screen now gathers everything in one place: tabbed setup instructions for the SDK, MCP server, and REST API, an API key generated on the spot — personal or through a service account — and deep links to add the project's MCP server to supported tools.

The Connect screen's MCP tab with the client picker open, listing Claude Code, Cursor, and other agents

See SDK, MCP, and REST API for client setup.

Shipped byMarc Backes

Native JSON Fields

JSON fields used to travel as encoded strings you had to parse and re-stringify yourself. Now they use native JSON end to end: the API returns and accepts raw JSON, and in the Studio new JSON fields default to the native JSON type, edit in a pretty-printed code editor, and display as compact single-line JSON in tables.

Breaking change. JSON fields now use native JSON on the wire. The API returns them as raw JSON instead of encoded strings and no longer accepts a stringified JSON value on input, so update any client that parsed the old string form or sent JSON as a string. Filtering a JSON field also requires an explicit operator now — { filter: { metadata: 2 } } is rejected; use { filter: { metadata: { _eq: 2 } } }.

Shipped byFlavian Desverne

Shipped byGuillaume Chau

Shipped byHannes Küttner

Branded Data Source Presets

The data source picker listed only raw database engines. Now it opens on a branded connector picker: alongside PostgreSQL, MySQL, MariaDB, and SQLite, you can pick managed providers like Neon, Aiven, PlanetScale, and Aurora — each with its own name, logo, and setup notes. The preset is display metadata; the underlying connector still determines how the source connects.

The Add a Data Source connector picker showing branded presets including Aiven, AlloyDB, and Amazon Aurora

See Connectors for supported databases.

Shipped byHannes Küttner

Permission-Aware Studio

The Studio didn't reflect your permissions — it showed controls and navigation you couldn't actually use. Now it reflects them throughout: controls you can't use are disabled with a tooltip explaining why, role and policy pickers list only the values you may assign, and navigation entries you can't access are hidden. Opening a restricted page by URL redirects you to one you can reach.

These gates are a convenience layer. The backend remains the source of truth for every permission check.

Shipped byHannes Küttner

Dedicated Project Schemas

User collections used to share the public schema, where separate projects could collide. Now each project uses two dedicated schemas on the system data source: monospace_<project>_meta for system metadata and monospace_<project>_data for the collections you create. When a data source exposes more than one namespace, the Add Collection form also lets you choose which namespace a new collection belongs to.

Breaking change. On the first boot after upgrading, Monospace provides migration instructions for moving an existing project to the new layout — monospace_<project> is renamed to monospace_<project>_meta, and user collections move from public into monospace_<project>_data. Back up your database before updating.

Shipped byFlavian Desverne

Shipped byMarc Backes

Configurable CORS

Browser apps on another origin couldn't call your API. Now the engine can send CORS headers so they can. CORS is off by default — enable it with MONOSPACE_CORS__ENABLED and set the allowed origins with MONOSPACE_CORS__ORIGIN.

See CORS for the full configuration.

Shipped byHannes Küttner

Access Tokens in Query Parameters

Passing an access token used to require the Authorization header. Now you can pass it as an access_token query parameter too, alongside the header and the session cookie — for clients that can't set request headers. Sending more than one of these at once is rejected with a 400.

See Authentication for all token sources.

Shipped byRijk van Zanten

Anonymous Usage Telemetry

Monospace sends anonymous usage telemetry to guide development. Pings carry a random install ID, the version, a configuration snapshot, and operation counts — never credentials, connection details, or your data. Disable scheduled telemetry with MONOSPACE_TELEMETRY__ENABLED=false. Instance-owner details captured during onboarding sync separately; opt out with MONOSPACE_INSTANCE_OWNER_SYNC_ENABLED=false.

See Telemetry for the opt-out variables.

Shipped byHannes Küttner

Shipped byBram Geron

0.1.0June 23, 2026

Single sign-on, MCP, and the AI assistant

This release adds single sign-on, an MCP server for AI agents, audit logging, MySQL and MariaDB data sources, and an in-Studio AI assistant.

Single Sign-On

Let members sign in with your organization's identity provider instead of a Monospace password. Set up Google, GitHub, Microsoft Entra, Okta, and other OAuth 2.0 providers from Settings → Sign-in Providers — common providers come with presets.

The Add sign-in method dialog with provider presets

See Configure SSO to connect a provider.

Shipped byReza Baar

Shipped byFlavian Desverne

MCP Server

Connect AI agents to your project through a Model Context Protocol server. Each project exposes its own endpoint at /api/{project}/mcp over streamable HTTP. Agents authenticate with an API key and can query, create, update, and delete items, inspect and modify the schema, and list data sources. Every call runs under the permissions of the key you connect with.

An AI agent inspecting and updating a project schema through the Monospace MCP server

See Configure MCP for setup and client configuration.

Shipped byRijk van Zanten

Audit Logs

Monospace now records key activity — user and account changes, invitations, project membership, and schema migrations — to an audit log. Each entry captures who made the change, the outcome, and when it happened. Administrators can read and filter the log through the system API.

Audit logs in Monospace

See Audit Logs for the event catalog and how to query them.

Shipped byMarc Backes

Shipped byFlavian Desverne

MySQL & MariaDB

Connect MySQL and MariaDB databases as data sources, alongside PostgreSQL. Add a connection from Data Model → Data Sources using the connection parameters or a connection string, with optional TLS.

See MySQL and MariaDB for connection options.

Shipped byBram Geron

AI Assistant

Chat with an AI assistant directly in the Studio. It can query your data, create, update, and delete items, and read or change your schema — all under your own permissions. Configure an AI provider under Settings → AI.

Configuring the AI assistant's model, and the assistant analyzing data in the Studio

See AI for the assistant and the MCP server.

Shipped byRijk van Zanten

No Aggregates

Understand the current limitations around data aggregation natively in the Monospace API.