myartefacts

com.myartefactsPublished by myartefacts.comOfficial publisherv1.0.0Updated Oct 31, 2026

Publish agent-made pages, decks and files to a private library, with share links.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowFiles & Storage

Overview

AI-generated overview

Publishes agent-created pages, decks and files to a private library with share links, hosted remotely at myartefacts.com.

What you can do
  • Publish pages, decks and files created by the assistant into a private library.
  • Generate share links so others can view published artefacts.
  • Organise output in a personal library rather than returning files inline.
  • No individual tools are listed, so exact operations are not documented in the supplied material.
When to use it
Useful when an assistant produces pages, slide decks or documents that should be stored and shared as links instead of pasted into chat, for example handing a report or deck to a colleague.
Requirements
A remote MCP endpoint at myartefacts.com over streamable HTTP. Authentication is required via OAuth; the Authorization header is optional for OAuth clients, and OAuth 2.1 with dynamic client registration is supported for clients such as ChatGPT and Claude. No local runtime or environment variables.
Before you install
An account and OAuth authorisation are required, and the server holds whatever artefacts you publish. Share links expose content to anyone who has the link, so check who can access a link before sending it. Publishing writes data to a third-party service.

Installation

In SourceWeft

  1. Open myartefacts in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. 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/com.myartefacts%2Fmyartefacts/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "myartefacts": {
      "type": "http",
      "url": "https://myartefacts.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 31, 2026

Score

67% 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
  • Auth declaredRequired10 pts
  • 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.