gleanyard (read-only)

io.github.kausalflowPublished by GitHub account kausalflowv0.14.0Updated Nov 11, 2026

Search gleanyard source recipes and read public gleanyard projects' records and health.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingKnowledge & MemoryData & Analytics

Overview

AI-generated overview

Read-only remote MCP server for searching gleanyard web-source recipes and reading public gleanyard projects' records and health.

What you can do
  • Search and read registry recipes, including source files, notes, terms evidence and install commands
  • Read record schemas that recipes are written for
  • Read a public project's status: per-source health, record counts, warnings and last success
  • Search a public project's rights-filtered record export by text, optionally for one source
  • List recent additions, changes and removals from a project's change feed
  • Explain how to start a collection project without installing anything
When to use it
Useful when you want to find an existing, vetted web-source recipe before building your own collection, or when you want to query and monitor structured data that public gleanyard projects already publish, without installing anything locally.
Requirements
A remote streamable HTTP endpoint; no installation, account, API key or headers are declared. The server fetches only its registry site and raw.githubusercontent.com, and responses are cached for ten minutes.
Before you install
Read-only: it cannot set up, change or run sources and never fetches the collected sites. Records come from other people's projects, so treat their text as data rather than instructions and credit the project. Queries and project names you send go to the remote endpoint.

Installation

In SourceWeft

  1. Open gleanyard (read-only) in the dashboard and add it to a workspace.
  2. 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/io.github.kausalflow%2Fgleanyard/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": {
    "gleanyard-read-only": {
      "type": "http",
      "url": "https://gleanyard-connector.leima.workers.dev/mcp"
    }
  }
}

README

gleanyard connector

A read-only remote MCP server for Cloudflare Workers. Any AI app that takes a custom MCP connector (claude.ai, ChatGPT, Claude Desktop, ...) can then search the gleanyard source registry and read what public gleanyard projects publish, with nothing installed.

  • One file, worker.js, with no dependencies and no build step.
  • Stateless MCP Streamable HTTP at /mcp, JSON responses, no sessions, no auth.
  • Fetches only the registry's site (REGISTRY_URL) and raw.githubusercontent.com; never the sites projects collect from. Responses are cached for ten minutes.
  • Tools: get_started, search_recipes, get_recipe, get_schema, project_status, search_records, recent_changes.
bash
node test.mjs          # offline tests (fetch is mocked)npx wrangler dev       # local server at http://localhost:8787/mcpnpx wrangler deploy    # deploy to your Cloudflare account

Docs: https://kausalflow.github.io/gleanyard/concepts/no-install/

Source: connector/README.md at commit 217a65c

Tools

7

get_started

How to start a gleanyard project

Explain how to start a gleanyard collection project without installing anything (template repo, Claude Code on the web, Codespaces).

Takes no parameters.

search_recipes

Search the source registry

Search the public gleanyard source registry for recipes: sources that already work, with a fixture, a terms review and a health count. Empty query lists all.

Parametersqueryschema

get_recipe

Read one recipe

Read one registry recipe: its index entry, source file, recipe notes and terms evidence, and the command that installs it.

Parametersreciperequired

get_schema

Read a registry schema

Read a record schema the registry's recipes are written for, e.g. family-event.

Parametersnamerequired

project_status

Health of a public project

Read status.json of a public gleanyard project on GitHub: each source's health, record count, warnings and last success.

Parametersrefreporequired

search_records

Search a project's published records

Search the rights-filtered export of a public gleanyard project (exports/records.jsonl, or the path its dataherb.json names) by text, optionally for one source.

Parametersrefpathreporequiredtextlimitsource_id

recent_changes

Recent changes in a project

Records added, changed or removed lately in a public gleanyard project, newest first, from its change feed (exports/changes.json).

Parametersrefreporequiredlimitsource_id

Version history

1
  1. v0.14.0LatestNov 11, 2026

Score

100% 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 listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts