Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By cyanheads
Build, test, and release MCP servers built on @cyanheads/mcp-ts-core with scaffolding, design, testing, security auditing, and automated publishing workflows
npx claudepluginhub cyanheads/cyanheads --plugin workflows-mcp-serverMCP definition linter rules reference. Use when `bun run lint:mcp` or `bun run devcheck` reports a lint error or warning (`format-parity`, `schema-is-object`, `name-format`, `server-json-*`, etc.) and you need to understand the rule, its severity, and how to fix it. Every rule ID the linter emits has an entry in this doc.
DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, the token-sharing pattern for multi-agent collaboration, env config, and Cloudflare Workers fail-closed behavior.
Reference for core and server configuration in `@cyanheads/mcp-ts-core`. Covers env var tables with defaults, priority order, server-specific Zod schema pattern, and Workers lazy-parsing requirement.
Canonical reference for the unified `Context` object passed to every tool and resource handler in `@cyanheads/mcp-ts-core`. Covers the full interface, all sub-APIs (`ctx.log`, `ctx.state`, `ctx.elicit`, `ctx.sample`, `ctx.progress`), and when to use each.
McpError constructor, JsonRpcErrorCode reference, and error handling patterns for `@cyanheads/mcp-ts-core`. Use when looking up error codes, understanding where errors should be thrown vs. caught, or using ErrorHandler.tryCatch in services.
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Orchestrate complex workflows with DAG-based execution, parallel tasks, and run history tracking
Stateful workflow engine MCP server for multi-step automation
Claude Code integration for MCP Task Orchestrator — schema-aware context, note-driven workflow
Multi-agent workflow orchestration via YAML. Ships the conductor skill so the assistant can validate, run, debug, and author workflow files for the conductor CLI.
Core workflow engine - Execute workflow-as-markdown definitions with validation-driven completion
Prefect workflow orchestration - read-only MCP server for diagnostics, CLI skill for mutations
Search PubMed/Europe PMC, fetch articles and full text (PMC/EPMC/Unpaywall), citations, MeSH terms.
MCP server for the ClinicalTrials.gov v2 API. Search trials, retrieve study details and results, and match patients to eligible trials.
Send, manage, and replay ntfy push notifications via MCP. STDIO or Streamable HTTP.
MCP server for the PubChem chemical database. Search compounds, fetch properties, safety data, bioactivity, cross-references, and entity summaries. STDIO & Streamable HTTP.
No description provided.
Store, query, and create YAML workflow playbooks for LLM agents via MCP. STDIO or Streamable HTTP.
Four tools covering the full workflow library lifecycle — discovery, retrieval, and creation for both permanent and temporary workflows:
| Tool | Description |
|---|---|
workflow_list | List all permanent workflows in the index, with optional category and tag filters. |
workflow_get | Retrieve a complete workflow definition by name, with global instructions prepended. |
workflow_create | Write a new permanent workflow YAML to the library. |
workflow_create_temp | Write a temporary one-shot workflow, indexed but excluded from list results. |
workflow_listList permanent workflows from the in-memory index.
includeTools: true to surface the unique server/tool pairs used across each workflow's stepsworkflow_getRetrieve a complete workflow by name, including the global instructions document.
version to get the highest available match; specify a version for an exact lookupglobal_instructions.md content as globalInstructions — apply these when executing the workflow; null when the file is absentworkflow_list{{input.foo}}, {{steps.X.output.Y}}) are returned verbatim — the server never interpolates themworkflow_createWrite a new permanent workflow to the library.
categories/<slugified-category>/<slugified-name>-workflow.yamlname@version already exists — bump the version to create a new revisioncreated_date and last_updated_date automaticallyworkflow_create_tempWrite a throwaway workflow to the temp/ directory.
workflow_get but excluded from workflow_list resultsBuilt on @cyanheads/mcp-ts-core: