mcpdirectory.dev
9,129 servers · updated 23 Sept

Artifacta MCP server

community Active last commit 57 d
{
  "mcpServers": {
    "artifacta": {
      "command": "npx",
      "args": [
        "-y",
        "@artifacta-mcp/mcp@latest"
      ],
      "env": {
        "ARTIFACTA_API_KEY": "<artifacta_api_key>"
      }
    }
  }
}
file .mcp.json (in your project root)install npx -y @artifacta-mcp/mcpversion 1.0.4

What it does

Artifacta is an artifact store for AI agents that lets them persist and share run outputs like files, reports, and datasets across sessions. It offers both hosted OAuth and local stdio access, with content-hash deduplication and expiring download links.

  • Store and retrieve files, reports, and datasets produced by agent runs with session and agent metadata attached.
  • Share artifacts with others via expiring presigned download links or public pages at artifacta.io.
  • Transfer outputs between agent sessions and persist them across disconnections.

Tools this server exposes

ToolDoes
whoamiVerify credentials and return tenant and plan information.
store_artifactUpload an artifact from inline content or a local file path.
request_upload_urlRequest a presigned upload URL for two-phase large file uploads.
complete_uploadComplete a two-phase presigned upload for large files.
get_artifactFetch artifact metadata by ID.
get_artifact_download_urlGet a presigned download URL with 1-hour expiry.
list_artifactsList and filter artifacts by session, agent, or metadata.
list_sessionsList active sessions.
seal_sessionSeal a session to prevent further artifacts from being added (requires --allow-destructive flag).
create_download_linkCreate a public expiring share link for an artifact (requires --allow-destructive flag).
delete_artifactSoft-delete an artifact (requires --allow-destructive flag).
publish_artifactPublish an artifact as a public page at artifacta.io/a/{slug}.
unpublish_artifactRemove an artifact's public page without deleting the artifact itself.

Before you enable it

An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.