Skip to main content
hc
Submit
mcpSource-backedReview first Safety ✓ Privacy ✓

Artidrop MCP Server for Claude

Artidrop remote MCP server for publishing HTML, Markdown, and multi-file sites from AI agents with shareable URLs via streamable HTTP, optional API keys, and AFAuth agent identities.

by Artidrop·added 2026-06-16·
Claude CodeCodexCursorClaude Desktop
HarnessClaude CodeCodexCursorClaude Desktop
Review first — review before installing

Open the source and read safety notes before installing.

Safety notes

  • Publish and update tools create publicly reachable URLs when visibility is public or unlisted.
  • Pass content verbatim through MCP; reformatting can break HTML, script, or markdown rendering per official guidance.
  • Anonymous publishes are limited to five per hour per IP; authenticated keys raise limits but billable access may apply.
  • AFAuth agent signup provisions accounts without portal keys; review attestation and ownership policies before production use.

Privacy notes

  • Published artifacts, titles, and content are stored on Artidrop infrastructure according to its privacy terms.
  • API keys and OAuth tokens grant publish and management access; store them in connector headers, not chat logs.
  • Private visibility restricts reads to owners, but MCP tool output may still appear in Claude session history.

Prerequisites

  • Artidrop API key from https://artidrop.ai for authenticated list, update, and delete tools, or accept anonymous publish rate limits.
  • Claude Pro, Team, or Enterprise with Connectors support, or another MCP client with streamable HTTP transport.
  • Review of Artidrop visibility settings (public, unlisted, private) before publishing sensitive content.
  • Human review of generated HTML or Markdown before publishing externally shareable artifacts.

Schema details

Install type
cli
Reading time
4 min
Difficulty score
35
Troubleshooting
Yes
Breaking changes
No
Collection metadata
Estimated setup
10 minutes
Difficulty
intermediate
Tool listing metadata
Full copyable content
{
  "mcpServers": {
    "artidrop": {
      "url": "https://artidrop.ai/mcp",
      "type": "http"
    }
  }
}

About this resource

Overview

Artidrop is a hosted Model Context Protocol server for publishing agent-generated HTML, Markdown, and multi-file sites. The discovery document at /.well-known/mcp.json registers the streamable HTTP endpoint at https://artidrop.ai/mcp.

Full API and MCP tool documentation is published at artidrop.ai/llms-full.txt.

Features

  • Remote streamable HTTP MCP at https://artidrop.ai/mcp.
  • Anonymous tools: publish, publish_site, get, and versions.
  • Authenticated tools with API keys: list, update, update_site, and delete.
  • Optional OAuth 2.1 and AFAuth agent identities documented in llms-full.txt.
  • Shareable artifact URLs for HTML, Markdown, and ZIP-based sites.

Use Cases

  • Publish agent-generated reports or dashboards as shareable URLs.
  • Version and update Markdown documentation produced during Claude sessions.
  • Deploy multi-file static sites from agent workflows with publish_site.
  • Prototype agent-first publishing with AFAuth signed requests.

Installation

Claude (Connectors)

  1. Add a custom connector under Settings → Connectors.
  2. Enter https://artidrop.ai/mcp or append ?key=sk_... for authenticated tools.
  3. Complete OAuth if prompted for interactive login flows.

Claude Code

claude mcp add --transport http artidrop https://artidrop.ai/mcp

Source Notes

Verified against Artidrop llms-full.txt and MCP discovery on 2026-06-16:

  • MCP integration documents streamable HTTP at POST https://artidrop.ai/mcp.
  • Discovery metadata is published at https://artidrop.ai/.well-known/mcp.json.
  • Anonymous and authenticated tool lists are documented with rate limits and visibility options.
  • Official guidance requires passing publish content verbatim without reformatting through MCP.

Duplicate Check

Checked content/mcp for Artidrop or agent publishing MCP coverage. No existing MCP entry covers ai.artidrop/artidrop as a publishing layer for AI agents.

Editorial Disclosure

Submitted as an independent community MCP entry by kiannidev, based on public Artidrop llms-full.txt and MCP discovery documentation. No paid placement, referral, or affiliate relationship.

Sources

#publishing#html#markdown#remote-mcp#agents

Source citations

Add this badge to your README

Show that Artidrop MCP Server for Claude is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/ai-artidrop-artidrop-mcp-server.svg)](https://heyclau.de/entry/mcp/ai-artidrop-artidrop-mcp-server)

How it compares

Artidrop MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

FieldArtidrop MCP Server for Claude

Artidrop remote MCP server for publishing HTML, Markdown, and multi-file sites from AI agents with shareable URLs via streamable HTTP, optional API keys, and AFAuth agent identities.

Open dossier 		Inferventis MCP Server for Claude

Inferventis hosted MCP server with 20 financial tools for FX rates, stocks, crypto, news, and URL reading over streamable HTTP, with many free tools and optional premium API keys.

Open dossier 		Agentgateway MCP Gateway

Apache-2.0 agentic proxy that can expose stdio, HTTP, SSE, and Streamable HTTP MCP servers through a managed gateway with federation, OAuth/JWT authentication, RBAC/CEL policy, CORS, TLS, observability, and Kubernetes Gateway API support.

Open dossier 		Dagu MCP Server

Built-in Streamable HTTP MCP server for Dagu that lets AI agents read workflow state, inspect DAG specs and logs, preview or apply workflow changes, and start, enqueue, retry, or stop DAG runs.

Open dossier
Trust
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Categorymcpmcpmcpmcp
Sourcesource-backedsource-backedsource-backedsource-backed
AuthorArtidropInferventisagentgatewaydagucloud
Added2026-06-162026-06-142026-06-062026-06-06
Platforms
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo————
Safety notes✓Publish and update tools create publicly reachable URLs when visibility is public or unlisted. Pass content verbatim through MCP; reformatting can break HTML, script, or markdown rendering per official guidance. Anonymous publishes are limited to five per hour per IP; authenticated keys raise limits but billable access may apply. AFAuth agent signup provisions accounts without portal keys; review attestation and ownership policies before production use.✓Makes outbound network requests to Inferventis and third-party financial data providers. URL reader tools fetch arbitrary web pages; treat returned content as untrusted. Premium tools may incur API usage charges when keys are configured. Do not rely on MCP output for automated trading without independent verification.✓Agentgateway can aggregate and expose many downstream MCP targets through one endpoint; every target's permissions become part of the gateway surface. Stdio targets are spawned by the gateway process, so commands such as package runners or containers inherit the gateway host's trust boundary. Demo configs use permissive CORS and local authorization servers; lock down origins, headers, issuers, audiences, JWKS, and resource metadata before production use. CEL/RBAC policies can inspect MCP tool names, arguments, results, prompts, resources, request bodies, JWT claims, API keys, and backend metadata; test policies before relying on them. Remote MCP proxying, OAuth provider adaptation, Kubernetes routing, TLS termination, and guardrails are infrastructure changes that should go through normal security review.✓Dagu is a workflow engine; MCP access can expose shell commands, Docker containers, Kubernetes Jobs, SSH commands, SQL queries, HTTP calls, agent harnesses, and other workflow steps. The MCP server registers `dagu_change` and `dagu_execute` as destructive-capable tools, so require preview/review before applying DAG changes or starting/stopping production runs. API keys can be scoped to the MCP surface; avoid reusing broad admin credentials for agent access. Workflow edits may change schedules, parameters, retries, secrets usage, queues, resource limits, notifications, and downstream infrastructure actions. Keep the Dagu server and MCP endpoint behind trusted network boundaries, TLS, and authentication for shared or remote deployments.
Privacy notes✓Published artifacts, titles, and content are stored on Artidrop infrastructure according to its privacy terms. API keys and OAuth tokens grant publish and management access; store them in connector headers, not chat logs. Private visibility restricts reads to owners, but MCP tool output may still appear in Claude session history.✓Ticker symbols, URLs, and search queries you send are processed by Inferventis and upstream data vendors. Premium API keys are credentials; store them in MCP headers or env vars, not in chat or source control. Fetched page content may include tracking parameters from the original URL.✓MCP requests, tool arguments, tool results, prompt names, resource names, session IDs, JWT/API-key claims, raw request/response bodies, logs, traces, and telemetry may pass through the gateway. CEL policy and observability features may buffer or inspect request and response bodies depending on configuration. OAuth/JWT metadata, bearer tokens, API keys, DCR secrets, Keycloak/Auth0/Okta settings, and upstream MCP credentials must be protected as secrets. Any data returned by downstream MCP tools can still be sent onward by the MCP client to the configured model provider.✓DAG specs, run parameters, logs, documents, audit records, secrets references, API keys, environment variables, and workflow outputs may be exposed to the MCP client. Workflow logs can contain credentials, customer data, internal hostnames, database query results, command output, file paths, or incident context. Dagu stores state locally by default and can also run distributed workers; review where DAG files, logs, audit entries, and secrets are persisted. Any workflow state returned through the MCP client may be sent onward to the configured model provider.
Prerequisites
  • Artidrop API key from https://artidrop.ai for authenticated list, update, and delete tools, or accept anonymous publish rate limits.
  • Claude Pro, Team, or Enterprise with Connectors support, or another MCP client with streamable HTTP transport.
  • Review of Artidrop visibility settings (public, unlisted, private) before publishing sensitive content.
  • Human review of generated HTML or Markdown before publishing externally shareable artifacts.
  • Claude Pro, Team, or Enterprise with Connectors support, or Claude Code with HTTP MCP transport.
  • Internet access to reach the Inferventis Cloud Run endpoint in europe-west1.
  • Optional Inferventis API key for premium market data tools that require authentication.
  • Awareness that financial data is informational and not investment advice.
  • Agentgateway binary, container image, or source checkout from the upstream release/container/docs path.
  • At least one downstream MCP target, such as a stdio command, remote MCP server, SSE server, or Streamable HTTP server.
  • MCP client that can connect to the exposed Streamable HTTP or SSE route.
  • Auth, CORS, TLS, route, and policy configuration reviewed before shared or remote exposure.
  • Dagu installed from Homebrew, GitHub Releases, npm, Docker/GHCR, Helm, or another upstream-supported installation path.
  • A running Dagu HTTP server with the built-in MCP endpoint enabled through the normal server path.
  • MCP client that supports Streamable HTTP server configuration.
  • API key with MCP surface access when Dagu authentication is enabled.
Install
claude mcp add --transport http artidrop https://artidrop.ai/mcp
claude mcp add --transport http inferventis https://mcp-server-295985738387.europe-west1.run.app/mcp
docker pull ghcr.io/agentgateway/agentgateway
brew install dagu
Config
{
  "mcpServers": {
    "artidrop": {
      "url": "https://artidrop.ai/mcp?key=sk_YOUR_KEY",
      "type": "http"
    }
  }
}
{
  "mcpServers": {
    "inferventis": {
      "url": "https://mcp-server-295985738387.europe-west1.run.app/mcp",
      "type": "http",
      "headers": {
        "X-API-Key": "YOUR_INFERVENTIS_KEY"
      }
    }
  }
}
{
  "mcpServers": {
    "agentgateway": {
      "url": "LOCAL_AGENTGATEWAY_MCP_URL",
      "headers": {
        "Authorization": "Bearer AGENTGATEWAY_MCP_TOKEN"
      }
    }
  }
}
{
  "mcpServers": {
    "dagu": {
      "url": "LOCAL_DAGU_MCP_URL",
      "headers": {
        "Authorization": "Bearer DAGU_MCP_API_KEY"
      }
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.