npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@agentworkforce/mcp-workforce

v3.0.12

Published

An MCP server that exposes workforce primitives (workflows, memory, integration clients) to a harness running inside a workforce sandbox.

Readme

@agentworkforce/mcp-workforce

An MCP server that exposes workforce primitives (workflows, memory, integration clients) to a harness running inside a workforce sandbox.

The workforce runtime spawns this server automatically when a handler calls ctx.harness.run(...) — the harness (Claude Code, Codex, opencode) then has tool access to:

| Tool | Description | |---|---| | workflow.run | Invoke a workforce cloud workflow by name. Returns { runId, status }. | | workflow.status | Poll a previously-started workflow run for status/output. | | memory.save | Persist a memory entry to the workspace memory bag. | | memory.recall | Semantic search over the workspace memory bag. | | integration.github.comment | Post a comment on a GitHub issue/PR. | | integration.github.createIssue | Create a GitHub issue. | | integration.github.upsertIssue | Update an open issue matching matchTitle, or create one. | | integration.github.getPr | Fetch a PR with title, body, refs, author, and unified diff. | | integration.github.postReview | Post a PR review (COMMENT / APPROVE / REQUEST_CHANGES). |

Running stand-alone

export WORKFORCE_WORKSPACE_ID=ws_demo
export WORKFORCE_RUNTIME_TOKEN=<workspace-token>          # required for workflow.*
export SUPERMEMORY_API_KEY=<key>                          # required for memory.*
export RELAYFILE_MOUNT_ROOT=/path/to/relayfile/mount      # required for integration.*

npx @agentworkforce/mcp-workforce

The server speaks MCP over stdio. Integration tools don't talk to GitHub/Linear/etc. directly — they write canonical JSON files inside the Relayfile mount, and Relayfile's writeback worker turns those into real provider API calls. Relayfile holds the OAuth credentials; the MCP server itself never sees a provider token.

Persona-side wiring

The runtime injects this server automatically when ctx.harness.run spawns a harness. Personas that want to declare it manually can use:

"mcpServers": {
  "workforce": { "command": "npx", "args": ["@agentworkforce/mcp-workforce"] }
}

Configuration

| Env var | Purpose | Required when | |---|---|---| | WORKFORCE_WORKSPACE_ID | Workspace this server is bound to | always | | WORKFORCE_PERSONA_ID | Persona id (logged for audit) | optional | | WORKFORCE_RUNTIME_TOKEN | Workspace-scoped token for cloud API calls | workflow.* | | WORKFORCE_CLOUD_URL | Override cloud base URL | optional | | SUPERMEMORY_API_KEY | Memory adapter credentials | memory.* | | SUPERMEMORY_ENDPOINT | Override supermemory endpoint | optional | | RELAYFILE_MOUNT_ROOT | Relayfile mount root the integration clients write into | integration.* | | RELAYFILE_ROOT | Legacy alias for RELAYFILE_MOUNT_ROOT | optional | | WORKFORCE_WRITEBACK_TIMEOUT_MS | Per-call writeback wait; default 30000 | optional |

Tools that lack their required env throw a clear setup error at first call — the server itself still boots so partial wiring is debuggable.