Skip to main content
The Claude Code plugin is the recommended path for Claude Code users. It adds Artifacta’s hosted MCP server the same way as the hosted endpoint — one URL, OAuth, no API key — and bundles a skill that teaches Claude Code when and how to persist run outputs to Artifacta, so you get the behavior without writing the prompt yourself.
The plugin and the plain hosted MCP connection expose the same Artifacta tools over the same OAuth flow. The plugin adds one thing on top: the persisting-outputs skill. If you already connected via claude mcp add --transport http artifacta … you do not need the plugin too — install it only if you want the skill. For CI, restricted networks, or explicit credential control, use the local stdio package instead: see Install in Claude Code (stdio).

​
Prerequisites

  • Claude Code installed (claude --version).
  • A free Artifacta account. Sign up at app.artifacta.io/signup — you log in with this account during the OAuth step below.
Nothing else. There is no package to install and no API key to create.

​
Install — two commands

Inside a Claude Code session (these are Claude Code slash commands, not shell commands), add the marketplace, then install the plugin from it: 
/plugin marketplace add SagaPeak/artifacta-mcp
/plugin install artifacta@artifacta
The first command registers SagaPeak/artifacta-mcp as a plugin marketplace (marketplace ID artifacta). The second installs the artifacta plugin from that marketplace, which wires up the hosted MCP server (https://mcp.artifacta.io/mcp) and the persisting-outputs skill in one step — no manual .mcp.json edits.

​
What you get

  • The full hosted Artifacta MCP tool surface — whoami, store_artifact, list_artifacts, create_download_link, and the rest, gated by the same read / write / destroy consent tiers as the plain hosted connection (see Permissions).
  • The persisting-outputs skill (plugin/skills/persisting-outputs/SKILL.md in the plugin). Invoke it explicitly with /artifacta:persisting-outputs, or let it auto-trigger — Claude Code reaches for it whenever a session produces outputs (files, reports, datasets, build results) worth saving, and it drives the store_artifact / request_upload_url + complete_upload tools for you.

​
Authenticate

Installing the plugin does not log you in — like the plain hosted connection, Artifacta needs a one-time browser OAuth login before its tools are usable.
1

Run /mcp

In a Claude Code session, type /mcp, select artifacta from the list, and choose Authenticate.
2

Log in and consent

Claude Code opens your browser to Artifacta. Sign in with your account, then on the consent screen tick the permissions you want to grant (read / write / destroy) and click Authorize.
3

Done

The browser redirects to a local loopback callback — a brief “you may close this tab” page is expected. Return to Claude Code; /mcp shows artifacta as connected, and the granted tools plus the persisting-outputs skill are available in the session.
Confirm the connection with a smoke prompt:
“What’s my Artifacta plan?”
Claude Code calls the whoami tool (available at every permission tier) and reports your tenant, plan, and usage.

​
Updating

Marketplace metadata is cached locally. Pull the latest plugin version with: 
/plugin marketplace update artifacta
Because the plugin has no version field of its own — the repo’s git commit is the version — this always gives you the latest published state of the plugin.

​
Uninstalling

/plugin uninstall artifacta@artifacta
This removes the plugin, its MCP server registration, and the persisting-outputs skill from Claude Code. It does not revoke the OAuth grant on Artifacta’s side — do that from app.artifacta.io if you’re removing access entirely, or run claude mcp logout artifacta first if you plan to reconnect without the plugin.

​
What’s next

  • Install in Claude Code (Hosted) — the same hosted OAuth connection without the plugin wrapper or skill, if you want to manage the MCP server entry yourself.
  • Install in Claude Code (stdio) — the local package with an ak_live_ API key, for CI, restricted networks, and explicit credential control.
  • MCP overview — the full tool and resource surface, shared by hosted, stdio, and the plugin.