Skip to main content

MAIP integrations

The Machine Agent Identity Protocol (MAIP) ships with integrations that bring agent identity, receipts, and trust scoring into your existing workflows. Local evidence, hosted receipt submission and signature verification are separate operations. Configure and test the integration you use; installation alone does not create a complete audit trail.
Prerequisites: You need a Truthlocks account with an API key and at least one registered agent. See the machine identity guide to register your first agent.
Browse the available integrations on the Integrations Hub. Links are grouped by SDK, AI framework, editor and collaboration tool.

Developer tools

VS Code extension

A sidebar panel for browsing receipts, generating receipts from your editor, and viewing trust data. Install it from the Visual Studio Marketplace. What it does:
  • Browse and search MAIP receipts from the sidebar
  • Generate receipts for code changes directly from the editor
  • View agent trust scores and receipt chains
Installation:
  1. Open VS Code and go to the Extensions view (Ctrl+Shift+X / Cmd+Shift+X).
  2. Search for “Truthlocks MAIP”.
  3. Click Install.
Alternatively, install from the command line:
After installing, open the MAIP sidebar panel and enter your API key and agent ID to connect.

JetBrains plugin

MAIP integration for IntelliJ, PyCharm, and WebStorm with the same receipt browsing and generation capabilities as the VS Code extension.

Neovim plugin

Install the released truthlocks/maip.nvim plugin, with curl available on your PATH:
Use :MAIPListAgents, :MAIPCreateReceipt, :MAIPListReceipts, :MAIPVerifyReceipt, :MAIPShowTrust and :MAIPDashboard. Receipt metadata is not a verified signature. Automatic commit receipts are opt-in and observe supported completed commit events; there is no auto_receipt on-save option in this release. See the versioned README for Telescope configuration and the current interactive-test limits.

MCP server

Install the executable on the machine running your MCP host:
Supply credentials through the host’s secure configuration. Use a key and agent from the same environment. Ask the host to list available tools, then use maip_list_agents, maip_list_receipts and maip_verify_receipt. A positive signature result requires valid: true, signature_verified: true and verdict: "VALID". Transparency verification is a separate result. Writes are not automatically retried.

Team collaboration

Slack, Linear and Notion integrations require their own real application/workspace credentials in addition to Truthlocks authentication. Their complete provider-to-receipt acceptance is still outstanding. Do not treat source availability, local tests or a Truthlocks API key as proof that an external workspace is connected. Review the source package README for provider permissions and configuration: Slack, Linear, Notion. Use a dedicated test workspace before enabling real event processing.

Slack setup and validation

Slack is a source installation, not a published @truthlocks/maip-slack npm package. Its bot authentication and an authorized test-message submission passed provider checks. Full personal-user slash-command and hosted event workflows remain under validation. Follow the Slack README for the reviewed build and all required settings. Bind the app to SLACK_TEAM_ID and explicit personal SLACK_ALLOWED_USER_IDS. Use MAIP_AGENT_ID from an existing registered Truthlocks agent for creation; a Slack Member ID is not a machine identity. Supply a sandbox key and https://sandbox-api.truthlocks.com/v1 during evaluation. Commands are registered in Slack’s app settings. Both HTTP and Socket Mode provide /webhook/maip, but hosting the listener does not automatically subscribe Truthlocks events to it. Delegation approvals remain in authenticated Console review. Local replay protection is process-local; production delivery needs durable upstream tracking.

Notion setup and validation

Notion is a private source package, not an npm installation. Real QA acceptance created a child page and database schemas, inserted an existing workspace receipt, repeated the sync without duplicating that page, and checked provider readback. Continuous hosted automation and durable recovery remain under validation. Connect only the intended page using Notion’s ••• → Connections menu. Follow the Notion README to initialize databases once and reuse their IDs. Use WEBHOOK_SECRET with the versioned HMAC/timestamp contract; unsigned requests are rejected. Receipt status is metadata, so a completed receipt does not automatically check the Notion Verified box. Use explicit signature verification separately.

CI/CD

The MAIP action’s inputs are maip-api-url, maip-api-key and maip-agent-id. The older api-key and agent-id names are not declared inputs. For a reviewed source checkout with its built dist/index.js, an explicitly triggered QA workflow can use this step:
This is a local action path after checkout and build, not an unverified Marketplace tag. Pin reviewed releases when distributing the action. Check/comment publishing requires deliberate GitHub permissions and separate acceptance; never expose secrets to workflows from untrusted forks. See the action README.

AI model connectors

Python wrappers capture events emitted through the configured integration. Local hashes are not server signatures. Provider credentials, Truthlocks credentials and hosted submission are configured separately; inspect the metadata you send and do not assume hashing removes privacy obligations.

Supported frameworks

Complete local LangChain example (no hosted request):
payload_hash describes local evidence. For hosted submission use MAIPClient.create_receipt and verify the returned server receipt_id; the LangChain README contains the async submission example. For asynchronous automatic hooks, flush and close the wrapper and inspect submission results before shutdown. Calls outside the configured wrapper are not observed.

Data and ML pipelines

Kafka connector

The Go connector submits message fingerprints as MAIP data.attestation receipts using an existing agent. Its HTTP client uses /v1/agent-receipts, preserves partial batch outcomes, and requires a confirmed signature for successful verification. Install github.com/truthlocks/kafka-maip-connector@v0.1.0 with go get. See the release and complete example. The API key selects the workspace and environment; a caller-supplied tenant ID does not override authorization. Message bytes and raw message keys are not uploaded. The producer/consumer wrappers buffer receipts in memory. Broker delivery and receipt delivery are separate operations; a successful Kafka write does not guarantee a receipt was retained. Required audit delivery needs a durable application outbox and explicit failure handling. Consult the release evidence before production use.

Event streaming

Install Go event-stream v0.1.0:
The library includes a concrete Redis client and adapter interfaces for NATS JetStream, EventBridge and Kinesis. Redis reconnecting consumers scan their own pending entries before new messages; failed processing remains unacknowledged. Keep consumer names stable across restarts. Claiming another consumer’s pending entries still requires an explicit recovery process. The published artifact passed an isolated real Redis restart/acknowledgement test and the complete Go race suite. Other backend adapters require real, authenticated client implementations. These adapters transport event envelopes; they do not automatically mint or verify MAIP signatures. Kafka receipt generation is a separate connector, described above.
The standalone gateway is not ready for deployment: its backend client factories are not wired, and it now refuses startup rather than reporting unperformed publications as accepted. There is no released truthlocks_streaming.StreamingGateway Python API corresponding to the older example on this page.
Deduplication now uses a bounded exact cache of confirmed event identities, scoped to tenant and source. Failed publications are not cached. Retries default to zero; explicit retries provide at-least-once delivery, not exactly-once guarantees. The batch middleware handles one event at a time so it cannot guess failed items from aggregate counts. Cache eviction and process restart can permit duplicates. The receipt validator checks structure and local hash links; it is not a signature verifier. Keep authenticated routing, durable retention and cryptographic validation in your application design.

MLflow, DVC and Delta Lake

Install mlflow-maip, dvc-maip or delta-lake-maip for the corresponding metadata builders. These packages produce local structured evidence; installing one does not make every framework operation a signed hosted receipt. There is no supported truthlocks_mlflow.TruthlocksPlugin.enable API corresponding to the older example. Use the complete local and hosted examples in the source READMEs: MLflow, DVC, Delta Lake. Provider metadata and artifact URIs do not independently verify artifact bytes or prove that an external operation occurred. Hosted signature verification does not establish transparency-log inclusion unless that separate check succeeds.

Docker

Container source files do not establish that a public image has been released or passed acceptance. The previously listed truthlocks/*:latest images and combined Compose example have not been verified as a working deployment and are not a supported quickstart. Do not infer image availability from those historical names. Use the published package release and its README for each integration. If building a container from reviewed source, pin that revision and dependencies, supply secrets through your runtime, and test the actual provider connection. Slack additionally requires its real application credentials; a Truthlocks API key alone is insufficient. The standalone event-stream gateway remains unavailable as described above.

Next steps

Machine identity

Register your first agent and understand the MAIP protocol.

Agent authorization

Configure scopes, sessions, and tool access for your agents.

Downloads

Find published CLI, SDK and IDE releases and their installation instructions.

Integrations hub

Browse all integrations by category.

Linear

Real provider authentication, SDK issue lookup and a receipt comment with readback passed in an explicitly authorized QA issue. This does not establish hosted webhook receipt creation or continuous synchronization. The source listener verifies Linear’s HMAC signature and signed timestamp, and restricts events to configured organization and team IDs. Project milestone automation remains unavailable rather than emitting estimated evidence. See the Linear setup and limits.