Create a new automation in the Prisme.ai workspace

Get a specific automation by its slug from the prisme.ai workspace

Update an existing automation on the prisme.ai workspace

Delete an automation from the prisme.ai workspace

List all automations in the Prisme.ai workspace

Search apps from the Prisme.ai app store

Get an app from the Prisme.ai app store with its configuration schema and automations. Use this to understand what config an app requires before installing it in the imports folder. The appSlug is case-sensitive.

Install an app from the Prisme.ai app store into a workspace. Use get_app first to understand the app's configuration schema.

List all installed app instances in a Prisme.ai workspace. Returns summary info only (slug, appSlug, appName, disabled). Use get_app_instance for full details.

Get details of an installed app instance by its slug

Update an installed app instance (config, disabled status, labels)

Uninstall an app instance from a workspace

Get only the configuration of an installed app instance

Update only the configuration of an installed app instance

Publish a workspace as a new app version in the Prisme.ai app store. On first publish, a slug is required to create the app. Subsequent publishes update the existing app.

Remove the write lock from a Prisme.ai workspace. Use this when a workspace is stuck in a locked state.

Create a new Prisme.ai workspace. Returns the created workspace with its ID.

Search for workspaces by name, description, or slug. Returns workspace IDs and names. Use this to find a workspaceId from a text search.

Call any Prisme.ai REST API endpoint, authenticated server-side with the configured environment token (the token is NEVER exposed to the model). Use for endpoints not covered by a dedicated tool — e.g. list organizations ('/orgs'), the current IAM context ('/me'), org members, API keys, etc. path is relative to the environment apiUrl base, which already includes '/v2' (so pass '/orgs', not '/v2/orgs').

Execute/test an automation already existing in the Prisme.ai workspace with optional payload

Search for events in Prisme.ai workspace using Elasticsearch DSL.

EVENT STRUCTURE:
Events contain the following key fields:
- @timestamp: Event timestamp (ISO 8601 format) - USE THIS FOR SORTING, NOT "timestamp"
- id: Unique event ID
- type: Event type (e.g., "runtime.automations.executed", "workspaces.pages.updated", "error")
- source: Metadata object containing:
  - correlationId: Groups all events from a single API request/operation
  - userId: User who triggered the event
  - sessionId: User session identifier
  - workspaceId: Workspace identifier
  - automationSlug: Automation name (for automation-related events)
  - http: HTTP request details (method, path, hostname, ip)
  - host: Service information (replica, service name)
- payload: Event-specific data (varies by event type)
- createdAt: Creation timestamp

COMMON QUERIES:
- Find all events for a specific request: {"bool": {"filter": [{"term": {"source.correlationId": "uuid-here"}}]}}
- Find automation executions: {"bool": {"filter": [{"term": {"type": "runtime.automations.executed"}}]}}
- Find events for specific automation: {"bool": {"filter": [{"term": {"source.automationSlug": "automation-name"}}]}}
- Find errors: {"bool": {"filter": [{"term": {"type": "error"}}]}}
- Exclude specific correlationId: {"bool": {"must_not": [{"term": {"source.correlationId": "uuid-here"}}]}}

SORTING:
- Always use "@timestamp" field for time-based sorting: [{"@timestamp": {"order": "desc"}}]
- DO NOT use "timestamp" as it's not mapped in the index

COMMON EVENT TYPES:
- runtime.automations.executed
- runtime.interactions.triggered
- runtime.dsul.updated
- workspaces.automations.created/updated/deleted
- workspaces.pages.created/updated/deleted
- error

ADDITIONAL INFO:
- SearchError are probably caused by your own previous failed attempt to create filters. This is usually not the event the user ask for. Keep searching for the events before the SearchError ones.
- Always use "source" to filter only the necessary fields. Only include the informations that are relevant to the user's request. Ignore durations, timestamps, IP adress if not asked for.

Supports full Elasticsearch DSL query syntax including aggregations, sorting, and pagination.

Returns Prisme.ai documentation by section. Call with 'index' first to see available sections.

SECTIONS:

• index: Table of contents and quick reference guide

• automations: Backend logic - triggers, instructions, expressions, memory scopes

• pages-blocks: UI components - Form, DataTable, RichText, Action, Chat, Charts, Carousel, Tabs, etc.

• workspace-config: Secrets management, workspace RBAC, one-product IAM notes, native events, versioning with Git

• advanced-features: Crawler, Custom Code, Agent Factory capabilities, Storage RAG, LLM Gateway, events

• products-overview: Current one-product platform architecture and integration patterns

• agent-creation: Agent Factory creation, prompt engineering, RAG, capabilities, evaluations

• api-selfhosting: REST/webhook API reference, one-product endpoint families, self-hosting deployment

• product-agent-factory: Agent Factory - agents, publishing, conversations, A2A, tools

• product-storage: Knowledge (Storage) - files, vector stores, indexing, RAG search

• product-llm-gateway: LLM Gateway - completions, embeddings, model catalog, routing

• product-capabilities: Capabilities catalog - MCP, file search, functions, skills, guardrails

• product-agent-evaluations: Agent Evaluations - test cases, runs, LLM-as-judge

• product-governance-v2: AI Governance v2 - IAM, API keys, service accounts, observability

• product-insights-v2: AI Insights v2 - Agent Factory analytics, criteria, feedback, GDPR

• product-collection-v3: AI Collection v3 - structured data MCP tools for agents

• product-prompt-library: Prompt Library - MCP prompts and showcases

• product-builder: Builder - DSUL workspaces, automations, pages, apps

• capability-workspaces: Backing guardrail, memory, search, vector provider, and connector workspaces

• legacy-products-overview: Legacy product architecture overview

• legacy-product-securechat: Legacy SecureChat product details

• legacy-product-store: Legacy AI Store product details

• legacy-product-knowledge: Legacy AI Knowledge and Knowledge Client details

• legacy-product-governance: Legacy AI Governance details

• legacy-product-insights: Legacy AI Insights details

• legacy-product-collection: Legacy AI Collection details

Validate Prisme.ai automation(s). Checks schema compliance, expression syntax ({{variables}} and {% code %}), unknown functions, naming conventions, and optionally strict mode. Accepts a file path, folder path (validates all .yml/.yaml/.json files), or automation object. Returns warnings (e.g., missing arguments declaration or naming convention issues) alongside errors even when the automation is valid.

Report bugs or feedback about the Prisme.ai MCP tools.

Use PROACTIVELY when you encounter issues - even mid-task. Don't wait for task completion.

Trigger on: tool errors, misleading documentation, or missing constraint information.

IMPORTANT: Report how to improve MCP tool guidance, NOT requests to change API behavior.

• GOOD: "Document that 'message' field is limited to 15 characters"

• BAD: "Increase the message limit to 50 characters"

Update an existing bug report or feedback.

Use this to cancel a report, edit its message, or change its type.

Retrieve bug reports and feedback submitted about the Prisme.ai MCP tools.

Download the current workspace from Prisme.ai and extract it to a local directory. This will overwrite existing files.

Upload the local workspace directory to Prisme.ai. Creates a backup version before importing. Version name (message) must not exceed 15 characters and only allows letters, numbers, hyphens, and underscores (no spaces).

Push a workspace to a git repository by creating a new version.

If the user asks to push to git, you MUST pass gitPlatform (or repositoryId) — do not call this tool without one of these selectors. Omitting both is only valid when the caller explicitly wants a non-git local snapshot.

Selector choice:

• gitPlatform — the default for pushing to git on Prisme.ai. Pass the platform repository id (key under the workspace's platformRepositories). If you don't know the id, pass any plausible value; the tool will reject it and return the list of available platform repos so you can retry. Prefer this selector unless the user specifically names a workspace-level repo.

• repositoryId — only when the user explicitly references a repo declared on the workspace itself (under repositories: with mode read-write).

Response includes pushedToGit: true|false — if false after a "push to git" request, the call was wrong; retry with gitPlatform.

Common errors:

• 400 "not up-to-date": the remote has newer commits — pull the workspace and retry.

• A successful push holds a ~30 min write lock on the workspace; use unlock_workspace to release it early.

Pull a workspace version from a git repository, or roll back/import an existing workspace version.

If the user asks to pull from git, you MUST pass gitPlatform (or repositoryId) — do not call this tool without one of these selectors. Omitting both is only valid when the caller explicitly wants to roll back/import an existing workspace version.

Selector choice:

• gitPlatform — the default for pulling from git on Prisme.ai. Pass the platform repository id (key under the workspace's platformRepositories). If you don't know the id, pass any plausible value; the tool will reject it and return the list of available platform repos so you can retry. Prefer this selector unless the user specifically names a workspace-level repo.

• repositoryId — only when the user explicitly references a repo declared on the workspace itself.

Response includes pulledFromGit: true|false — if false after a "pull from git" request, the call was wrong; retry with gitPlatform.

Upload a file to the Prisme.ai workspace's file storage. Returns the uploaded File object(s) with url, id, name, mimetype, size. The file source can be provided in one of three ways: path (local filesystem), url (remote URL fetched by the MCP), or dataUri (data:mime;base64,... string). Exactly one of these must be set.

List files in the Prisme.ai workspace. Supports pagination, sorting and Elasticsearch-style filtering via the query parameter.

Get metadata for a single file by id. Returns the File object including url, name, mimetype, size, metadata.

Delete a file from the Prisme.ai workspace storage by id.

Legacy AI Knowledge API: query an AI Knowledge project with RAG or retrieve context only. For new one-product agents, use Agent Factory messages/send or messages/stream with Storage-backed file_search.

Use method='query' (default) for full RAG response with LLM answer. Use method='context' to retrieve document chunks only without LLM response.

Requires a legacy AI Knowledge project API key (from AI Knowledge > API & Webhooks).

Legacy AI Knowledge API: direct LLM completion without RAG. For new direct model calls, use LLM Gateway v1/chat/completions or v1/embeddings.

Methods:

• chat: Simple completion using project's configured prompt/model

• openai: OpenAI-compatible chat completions endpoint

• embeddings: Generate embeddings for text

• models: List available models configured in the project

IMPORTANT: Before changing a model in a legacy AI Knowledge project, always call this tool with method='models' first to retrieve the list of available models and verify the model name exists.

Requires a legacy AI Knowledge project API key.

Legacy AI Knowledge API: document CRUD operations. For new RAG data, use Storage files/vector_stores APIs.

Methods:

• get: Get a document by ID

• list: List documents in a project

• create: Create a new document (text or URL)

• update: Update document metadata/content

• delete: Delete a document

• reindex: Reprocess a document

• download: Download original document file

Requires a legacy AI Knowledge project API key.

Legacy AI Knowledge API: project/agent management. For new agents, use Agent Factory /v1/agents APIs.

Methods requiring project apiKey (existing project):

• get: Get a project by ID

• update: Update project configuration

• delete: Delete a project

• tools: Get available tools for a project

• datasources: Get available datasources for a project

Methods using user's Bearer token (no apiKey needed):

• list: List accessible projects

• create: Create a new project (returns new project with apiKey)

• categories: List project categories

For methods using Bearer token, use workspaceName/environment to resolve credentials.

Register (or rotate) a user-created Prisme.ai API token for an environment. PRIVACY: calling this tool means the token travels through the conversation and is sent to the LLM provider. PREFER the out-of-band CLI instead — tell the user to run node <plugin>/build/index.js set-token <environment> --config-dir <dir> in their own terminal (the exact command is included in the 'no credentials' error); it prompts for the token with hidden input and never exposes it to the chat. Only use this tool if the user explicitly chooses to paste the token here despite that. The token is validated with a probe call to the API before being persisted to the MCP config dir (credentials.json, mode 600); an invalid token persists nothing. Pass apiUrl (and optionally studioUrl) to register an environment that is not configured yet.