Datalust Seq MCP integration for AI agents.
Connect AI agents to Datalust Seq through 15 structured actions, including create saved query, create signal, delete saved query, and ingest event. Review au…
- ACTION CONTRACTS
- 15
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Datalust Seq integration exposes
The Datalust Seq Agent App exposes 15 provider-backed actions for data and developer tools work. Its current contract lets an authorized agent create a saved seq sql query while preserving server-provided template defaults, create a seq signal while preserving server-provided template defaults, and delete a saved seq sql query; protected queries also require project permission. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Datalust Seq account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Datalust Seq capabilities.
Showing 12 of 15 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
create_saved_queryREADCreate a saved Seq SQL query while preserving server-provided template defaults.
INPUTS: title / description / sql / isProtected / ownerId
create_signalWRITECreate a Seq signal while preserving server-provided template defaults.
INPUTS: title / description / filters / columns / isProtected
delete_saved_queryHIGH IMPACTDelete a saved Seq SQL query; protected queries also require Project permission.
INPUTS: queryId
ingest_eventREVIEWIngest one structured log event into Seq using compact log event format.
INPUTS: timestamp / message / messageTemplate / level / exception
delete_signalHIGH IMPACTDelete a Seq signal by its identifier; protected signals also require Project permission.
INPUTS: signalId
execute_queryREADExecute a Seq SQL-style query and return its structured JSON result.
INPUTS: query / rangeStartUtc / rangeEndUtc / signal / timeoutMs
get_eventREADRead one Seq event by its event identifier.
INPUTS: eventId / render
get_saved_queryREADRead one saved Seq SQL query by its identifier.
INPUTS: queryId
get_signalREADRead one saved Seq signal by its identifier.
INPUTS: signalId / partial
ingest_eventsREVIEWIngest a JSON array of structured log events as one newline-delimited CLEF batch.
INPUTS: events
list_saved_queriesREADList saved Seq SQL queries visible to the API key.
INPUTS: ownerId / shared
list_signalsREADList saved Seq signals visible to the API key.
INPUTS: ownerId / shared / partial
INPUT CONTRACTS
Know what the action needs before it runs.
create_saved_query
titleREQUIRED- The human-readable saved query title.
descriptionOPTIONALsqlREQUIRED- The Seq SQL query text, which may be empty for a placeholder query.
isProtectedOPTIONAL- Whether modifying the saved query requires Project permission.
ownerIdOPTIONAL
create_signal
titleREQUIRED- The human-readable signal title.
descriptionOPTIONALfiltersOPTIONAL- The filters combined by the signal.
columnsOPTIONAL- The columns displayed for the signal.
isProtectedOPTIONAL- Whether modifying the signal requires Project permission.
delete_saved_query
queryIdREQUIRED- The Seq saved query identifier.
ingest_event
timestampREQUIRED- The ISO 8601 timestamp at which the event occurred.
messageOPTIONAL- A fully rendered event message.
messageTemplateOPTIONAL- A message template rendered with event properties.
levelOPTIONAL- The event level, such as Information, Warning, or Error.
exceptionOPTIONAL- An exception or stack trace attached to the event.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Create Saved Query
Create a saved Seq SQL query while preserving server-provided template defaults. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
create_saved_queryControl Create Signal
Create a Seq signal while preserving server-provided template defaults. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_signalVerify with Execute Query
Execute a Seq SQL-style query and return its structured JSON result. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
execute_querySAFETY BOUNDARY
Operate Datalust Seq with explicit limits
- Authorize Datalust Seq with API key and grant only the provider access required by the selected actions.
- 4 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_saved_query` and `delete_signal` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Datalust Seq rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Datalust Seq task completed successfully.
CONNECTION MODEL
API key
Seq API key sent with the X-Seq-ApiKey header. The connection validator requires Read permission; add Ingest for event ingestion, Write for signals and saved queries, and Project when modifying protected entities. Create or copy a key from Data > Ingestion in your Seq instance: https://docs.datalust.co/docs/api-keys
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 9
- WRITE SIGNALS
- 2
- HIGH IMPACT
- 2
- REVIEW SIGNALS
- 2
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Datalust Seq.