Data & contentPublic source

Artifact Store MCP Server

Governed artifact registry for ADK-Rust Enterprise agents. Content-immutable, versioned, provenance-linked, hash-verified artifacts with policy-driven lifecycle.

Open the source Read the official guide ↗

What it gives an agent

A purpose-built capability behind one MCP connection.

The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.

Content-immutable — updates create new versions, never overwrite

Provenance-linked — every artifact tracks its lineage

Hash-verified — SHA-256 integrity on every version

Policy-driven lifecycle — retention classes prevent premature deletion

Redaction by derivation — redacted copies are new artifacts, originals preserved

Architecture

How Artifact Store MCP Server fits into an agent system.

The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

→

MCP client

Discovers schemas, sends calls, and receives typed content.

→

Artifact Store MCP Server

Validates the request and owns 15 documented tool contracts.

→

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · streamable HTTP · Server framework: ADK MCP SDK + rmcp

Artifact Store MCP Server architecture diagram from its official repository

Tool catalog

What can an agent ask Artifact Store MCP Server to do?

Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.

15 named tools

list_folders

Browse workspace folder hierarchy

read only

list_artifacts

List artifacts by folder, session, owner, type, or class

read only

get_artifact_metadata

Inspect provenance, retention, access, hash, source

read only

read_artifact

Read artifact content when policy permits

read only

write_artifact

Store a generated artifact with metadata and provenance

internal write

create_artifact_version

Add a new version to an existing artifact

internal write

redact_artifact

Create a redacted derived copy of a sensitive artifact

internal write

derive_artifact

Create an artifact derived from another with provenance link

internal write

link_artifacts

Add a provenance edge between two artifacts

internal write

export_artifact_package

Bundle related artifacts for audit or delivery

read only

verify_artifact_integrity

Validate hash and provenance trail

read only

get_artifact_lineage

Trace provenance chain for an artifact

read only

Governance

Understand the effect of every tool.

A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.

7 read only7 internal write1 external write

Policy-driven lifecycle — retention classes prevent premature deletion

MCP surface

What the current documentation declares.

MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.

Prompts

ADK MCP SDKrmcpRegistry manifest

Install and connect

Follow the project’s documented starting point.

Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.

Install

cargo install mcp-artifact-store

MCP client configuration

{
  "mcpServers": {
    "artifact-store": {
      "command": "/path/to/mcp-artifact-store",
      "env": { "ARTIFACT_STORE_PATH": "~/artifacts" }
    }
  }
}

Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.

Official documentation

Continue with the project maintainers’ source of truth.

This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.