Early access

Describe it, and it gets built

Tell the assistant what you need to track and what should happen to it, and it builds the record types and the workflow for you.

Use the built-in AI Assistant, or bring the same workspace tools into Claude, ChatGPT, Codex and Cursor through MCP.

It works inside your account as you, not as a service account — so it can only reach what your own permissions already allow, and every action it takes lands in the same audit trail as if you had clicked it yourself.

Use your own AI client through MCP

Ask for it in your own words

The shortest way to understand it is to see the exchange.

In your account, as youIllustrative
We take motor claims. Each one has a policy number, a claimant, what happened, and any number of line items with their own evidence.
I can create a Motor claim record type with an Incident section and a repeating Line item section that nests its own evidence. Shall I publish it as version 1?
Yes — and email the assessor when one is over £5,000.
Published. I have drafted a workflow that triggers on a new claim, checks the amount, and sends the assessor a notification. It is waiting for you to activate it.

Every action above is one you could have taken yourself, and each lands in the audit trail under your name.

It does the work, you keep the decision

Nothing goes live because the assistant decided it should. It drafts, it explains what it is about to do, and the publishing and activating stay with you — which is also why letting it try something is cheap.

  • It signs in as you, never as a service account
  • It cannot reach anything your own permissions do not already allow
  • Every action lands in the audit trail under your name
  • A budget you set bounds any single run, with warnings before the ceiling

It reaches what you reach

The assistant drives the products' own operations, so its limits are your permissions rather than a shorter feature list.

126

operations it can carry out for you

Not a separate assistant-only feature list — these are the products' own operations, so it reaches what you reach.

  • Automation67Build, validate, version, activate and trace workflows
  • Data30Record types, fields, schemas, versions and data sources
  • Support9Raise, read and update tickets
  • Audit5Read the trail to answer what changed and when
  • Comments4Read and write the discussion on a record
  • Notifications4Templates and delivery
  • The assistant itself7Memory, documents and its own tools

Your AI client. Your workspace.

Bring the assistant’s tools into your AI chat

MCP (Model Context Protocol) connects Claude, ChatGPT, Codex, Cursor and other compatible AI clients to your SynaptaGrid workspace. Ask a question or describe a task, and the client uses the tools your account can access.

Data

Inspect record types, fields and schemas. Find records, then make the changes you request.

Automation

Inspect workflows and runs, build steps and mappings, and investigate a failed run.

Integrations

Find available external systems and read their activity contracts before configuring a workflow.

Audit

Read activity history to understand what happened and who performed an action.

Support and comments

Read support conversations and record discussions in the workspace you connected.

Notifications

Check your inbox. Template management is available when your workspace enables it.

The same workspace, wherever you ask

Use SynaptaGrid’s built-in AI chat or connect your own client. Each tool call runs with your signed-in account. Read the audit history to review recorded workspace activity. Available tools depend on your enabled products, features and permissions. Follow any approval prompts before an action continues.

Start with a specific request: “Show my record types”, “Check the latest workflow runs”, or “Read this support ticket”. For changes, name the target and the result you want. Confirm the connected workspace before working with its data.

Read the MCP connection guideGet the skill and client instructions

What it can do today

The assistant is in early access. The capabilities below are the ones in customers’ hands today.

It builds

Describe what you need, and it makes it

Record types, workflows, connections to systems you already run, and tools of your own — created from a conversation and published for you to review.

  • Build a data model by describing it

    Say what you need to keep track of, and the record types, field groups and typed fields are created and published for you.

    • Create record types, reusable field groups and typed fields from a conversation
    • Start from a sample document instead — it infers the structure, shows you the result, then applies it
    • Point it at an existing database, let it read the tables and turn them into a model
    • Start from a gallery of ready-made structures — addresses, invoices, contacts, companies, payments, line items
    • Save a structure you designed back to the gallery to reuse it
    • Load records in bulk once the model exists
  • Build a workflow the same way

    Describe the process and it creates the steps, the branching, the connections between them, and a version you can publish.

    • Create a workflow with its steps, transitions and branching rules
    • Attach the actions each step performs, and map record fields onto their inputs
    • Validate the workflow before publishing, then publish an immutable version
    • Set it to trigger on a record event, then activate it
    • Start from a workflow template, or fire a manual test run to watch it work
  • Register a system by describing it

    Give it a service’s API description and it registers the system, imports the operations as usable steps, and writes the field mappings.

    • Register an external service and point it at that service’s API description
    • Discover and import its operations so they become steps you can use
    • Author the mappings from your record fields to the request fields
  • Build your own assistant tools

    Define a single-purpose tool with typed inputs and outputs, and it becomes both something you can run and a named step available to your workflows.

    • Author a tool with a typed input and a typed output, no code required
    • Run it directly from your account
    • It appears automatically in your workflow action catalog as a named step

It reads

Ask it about what you already have

It reads your structure, your versions and your audit trail together, and it reads the documents you hand it — so a question about your account gets an answer grounded in your account.

  • Ask why a workflow did not run

    A read-only assistant correlates the workflow’s structure, its validation state, its published versions and the audit trail to explain what happened.

    • Explains why a workflow did not fire, rather than just reporting that it did not
    • Reads structure, versions and the audit trail together
    • Read-only — it diagnoses, it does not change anything
  • Hand it a document

    Upload a file and it reads it, so extracting structure from a real document does not start with retyping it.

    • Upload documents directly into a conversation
    • Classify, extract, summarize or remove personal data from text
    • Answers are grounded in your own content, with citations back to the source

It stays inside the lines

It cannot do what you could not

It acts as the person using it, never as a service account, and every run is bounded by a budget you set. This is the part a security review asks about.

  • It cannot exceed your own access

    Every action is checked four times before it runs: your organization’s grant, your personal grant, the assistant’s own allow-list, and a live permission check on the service being asked.

    • Administrators enable an assistant for the organization and choose which actions it may take
    • Each person’s access is then narrowed further from within that grant, never beyond it
    • The final check runs against the receiving service using your own credentials, not a shared key
    • Account administration stays out of reach by design — it cannot invite people, change roles, alter plans or touch billing
  • Connect your account to your AI client

    The platform is a remote MCP server, so an AI client can read your records and run your workflows as you, under your own sign-in.

    MCP — the Model Context Protocol — is how AI clients connect to external systems. Pointing one at your account is a sign-in, not a key: the client discovers where to authenticate and registers itself, you approve it as yourself, and from then on it sees exactly the tools your own permissions allow. Nothing is exposed by connecting that you could not already do.

    • A remote MCP server your AI client connects to over the network — nothing to install and run
    • Works with clients that support remote MCP servers, including ChatGPT, Claude (claude.ai, Claude Desktop and Claude Code) and Cursor
    • You sign in as yourself through the standard authorization flow; there is no shared key to distribute or rotate
    • The client registers itself rather than needing credentials issued by hand
    • Before a client that registered itself gets access, a consent screen names it, where its sign-in returns, what it may do and which workspace it will work in
    • Connected applications in your profile lists every client you approved; disconnecting one revokes its tokens, and reconnecting asks for your approval again
    • Which tools appear is decided by your own permissions, checked again on every call
    • Tool calls run through the same path and the same checks as the assistant itself — there is no second, looser code path
    • Every call lands in the audit trail attributed to you
  • Know what it costs before it runs

    Usage draws from a credit pool you top up, with per-person caps, warnings as you approach the limit, and a ceiling on any single run.

    • A shared credit pool with per-person allocation caps
    • Cost is reserved before a run starts, and a runaway run is stopped at a ceiling
    • Warning emails at 80%, 95% and 100% of an allocation
    • Top up in packs, with unused credit carrying over
    • Or bring your own provider keys and skip credit metering entirely
    • Or require self-hosted models only, so no request leaves your environment

Teach your client the workflow

Install the SynaptaGrid MCP skill

The connection provides live tools. The skill explains which product to use, how to select the workspace, and how to check results and handle access limits. Connect your account in Portal → AI → Connect MCP first; installing the skill does not grant access.

Claude web and Desktop

  1. Add the server URL from Portal’s Connect MCP page to Claude’s connectors and complete sign-in.
  2. Download the skill ZIP. In Customize → Skills, choose + → Create skill → Upload a skill and upload the ZIP.
  3. Enable the skill, then ask Claude to use the SynaptaGrid MCP skill for your workspace task.

Skills require code execution. If upload is unavailable, check your Claude organization’s skill policy.

Claude skill instructions

Claude Code

  1. Run the Claude Code connection command shown in Portal and complete OAuth sign-in.
  2. Extract the ZIP’s egav-mcp folder into ~/.claude/skills/. The file should be ~/.claude/skills/egav-mcp/SKILL.md.
  3. In a new session, use /egav-mcp with your request.
Claude Code skill instructions

Codex and Cursor

After connecting MCP, extract the ZIP’s egav-mcp folder into ~/.agents/skills/. Both clients can discover ~/.agents/skills/egav-mcp/SKILL.md.

In Codex CLI or the IDE extension, use $egav-mcp. In Cursor, select /egav-mcp. Restart the client if the skill does not appear.

Other connected clients

If your client supports file attachments but cannot install a standalone skill, download the instruction file and attach it as chat context. Ask the client to follow it for the current task. This provides guidance for that conversation.

Use Portal’s server URL and sign-in flow to connect. The instruction file cannot connect an account or enable a disabled feature.

Try a first request

Use the SynaptaGrid MCP skill to list the record types and workflows in my connected workspace. Confirm the workspace and report what you actually find. Keep this check read-only.

See it build something

The quickest way to judge it is to describe a form you already use and watch what it produces.