Developer · Remote MCP server
Marigold
Comment on AI-generated webpages; feedback flows back to your coding agent. Free, MIT, local-first.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.immuneeb/marigold- Version
- 0.9.1
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-07-25
- Updated
- 2026-07-25
- Publisher
- immuneeb (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/immuneeb) · how
- Website
- marigold.page
- Repository
- github.com/immuneeb/marigold-collab (folder packages/local)
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://marigold.page/api/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | marigold-draft | 0.9.1 | stdio |
How to connect Marigold
Marigold is a remote MCP server: there is nothing to install. Its endpoint is https://marigold.page/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: marigold-draft version 0.9.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y marigold-draft@0.9.1.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"marigold": {
"command": "npx",
"args": [
"-y",
"marigold-draft@0.9.1"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| MapleReview comments pinned to a running frontend, read and resolved by your coding agent. | Local · stdio |
| MapnosticsCodebase intelligence for AI agents - dead code, blast radius, ownership. | Remote & Local · HTTP, stdioLive check: sign-in required |
| Marboba MCPMarBoba IDP catalog as MCP tools: projects, APIs, runbooks, on-call, SLOs. Bring your own LLM. | Local · stdio |
| marchward.aiRuntime authority for AI agents: credential mediation, spend cap, approval gates, audit log. | Local · stdio |
| MarkdownMarkdown MCP - search, extract sections, list headings, find code blocks. | Local · stdio |
| Markdown Lane Check - llms.txt, .md twins, Accept: text/markdownSix checks: llms.txt, llms-full.txt,.md twins, Accept: text/markdown, sitemap.md, alt link. Free. | Remote · HTTPLive check: ✓ handshake |
| Markdown Renderer APIRender markdown to styled HTML with light/dark/github themes. x402 micropayment. | Remote · SSELive check: ✗ no handshake |
| Markdown to HTML APIConvert markdown to clean HTML with headings, lists, code blocks. x402 micropayment. | Remote · SSELive check: ✗ no handshake |