Artifacta MCP Server

Official MCP server for Artifacta — an artifact store purpose-built for AI agents. Agents persist run outputs (files, reports, datasets, build results) with session and agent metadata, hand them off across sessions, and share them via expiring download links. Content-hash dedup means re-storing the same bytes is free.

Listed in the official MCP registry as io.artifacta/mcp.

Two implementations with the same tool surface, error contract, and path-confinement engine:

Install as a Claude Code plugin

For Claude Code, the fastest path is the plugin marketplace this repo doubles as — it wires up the hosted server and a skill that persists run outputs automatically:

/plugin marketplace add SagaPeak/artifacta-mcp
/plugin install artifacta@artifacta

This bundles the same hosted MCP connection as the Quick start below plus the persisting-outputs skill (/artifacta:persisting-outputs, or it auto-triggers when a session has outputs worth saving). Update the plugin with /plugin marketplace update artifacta. See the plugin setup guide.

Quick start

The fastest way to connect is the hosted server — no install, no API key:

claude mcp add --transport http artifacta https://mcp.artifacta.io/mcp

On first use your client self-registers via OAuth Dynamic Client Registration (PKCE) and opens a browser to authorize — no ak_live_ key to copy or store. See the hosted setup guide.

Local / CI (stdio)

For headless, air-gapped, or CI environments where a browser OAuth flow isn't available, run the package locally over stdio with an API key. Get a key at app.artifacta.io/dashboard/keys, then add to your MCP client config (Claude Desktop, Claude Code, Cursor, or any MCP client):

{
  "mcpServers": {
    "artifacta": {
      "command": "npx",
      "args": ["-y", "@artifacta-mcp/mcp"],
      "env": {
        "ARTIFACTA_API_KEY": "ak_live_..."
      }
    }
  }
}

Or run the Python implementation with pipx run artifacta-mcp.

See the per-package READMEs for config-file profiles, path confinement (--allow-path), destructive-tool gating (--allow-destructive), and troubleshooting: TypeScript · Python.

Tools

Plus MCP resources for whoami, artifact metadata, artifact bytes, and sessions.

Safety defaults: local-file uploads are confined to an explicit --allow-path allow-list, and destructive tools (public share links, deletes, session seals) are hidden from clients that can't confirm writes unless --allow-destructive is passed. publish_artifact and unpublish_artifact are idempotent write operations, not destructive ones — they are not gated behind --allow-destructive.

Hosted OAuth connections (mcp.artifacta.io) add a second layer: the consent screen grants one of three scopes — artifacts:read ⊆ artifacts:write ⊆ artifacts:destroy. All 13 tools are always advertised in tools/list; calling a tool the token wasn't granted for returns a tool error with code insufficient_scope naming the missing scope, and the fix is to re-authorize with the broader scope. Scope gating applies only to hosted OAuth — ak_live_ API keys and local stdio remain full-access, using --allow-destructive / confirmation flags instead.

Framework integrations

The Python package ships optional adapters for OpenAI Agents SDK (pip install 'artifacta-mcp[openai-agents]') and LangChain/LangGraph (pip install 'artifacta-mcp[langchain]').

Documentation

Full docs at docs.artifacta.io/mcp/overview.

Development

# TypeScript
cd typescript && npm install && npm test

# Python
cd python && python -m venv .venv && source .venv/bin/activate
pip install -e '.[dev]' && pytest

This repository is published from the Artifacta monorepo; issues and PRs are welcome here.

License

MIT — see LICENSE.