Artifacts

io.github.mctx-aiPublished by GitHub account mctx-aiv2.2.0Updated Oct 24, 2026

Save decisions, plans, and notes from any AI session and retrieve them later — from any client. Ask

The publisher's own server: artifacts.boo

VerifiedSSEWeb executableKnowledge & Memory

Overview

AI-generated overview

Artifacts is a remote MCP server that lets an assistant save decisions, plans and notes from an AI session and retrieve them later from any client.

What you can do
Save decisions, plans and notes from an AI session so they persist beyond the conversation. Retrieve previously saved material later, from any connected client. Share a single store of session notes across different AI clients rather than keeping them per tool.
When to use it
Useful when you want decisions, plans or notes produced during AI sessions to be kept and looked up again later, especially across multiple clients.
Requirements
A remote MCP endpoint at artifacts.mctx.ai, reached over SSE. No packages, environment variables or headers are declared, and the manifest declares no authentication.
Before you install
The manifest declares no authentication, so consider what you store there and who else could reach it. Saved notes and plans are sent to a third-party hosted service. No write, delete or sharing behavior is documented, so verify how stored content is retained and exposed.

Installation

In SourceWeft

  1. Open Artifacts in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.mctx-ai%2Fartifacts/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "artifacts": {
      "type": "sse",
      "url": "https://artifacts.mctx.ai/v2.2.0"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v2.2.0LatestSep 16, 2026

Score

28% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Artifacts integrations