ZKshare

io.github.sp0obyPublished by GitHub account sp0obyv1.0.1Updated Nov 3, 2026

ZKshare stdio MCP: store/prove/share, semantic search, sandbox proxy to HTTPS /api/v1/context.

VerifiedSTDIODesktop onlyKnowledge & MemoryAI & ML

Overview

AI-generated overview

ZKshare MCP server that lets an assistant store, prove and share context, run semantic search, and call the ZKshare HTTPS API from a local stdio process.

What you can do
  • Store, prove and share context through ZKshare
  • Run semantic search over stored context
  • Forward tool calls to the ZKshare context API endpoint using your API key
  • Act as a sandbox proxy to the HTTPS context API
When to use it
Use it when you want an assistant to keep and retrieve shared context through ZKshare, for example storing, proving or searching context entries, and you already have a ZKshare API key.
Requirements
Runs locally over stdio via npx, so Node.js 18 or newer is needed. A ZKshare API key is required in the ZKSHARE_API_KEY environment variable. ZKSHARE_API_URL is optional and defaults to the hosted ZKshare service; set it only for a self-hosted API. Network access to the ZKshare API is required.
Before you install
The server requires a ZKshare API key (ZKSHARE_API_KEY), which is sent with every forwarded tool call to the configured API origin. Tool calls, including stored or shared context, are sent to that remote service, so review what data leaves your machine. Pointing ZKSHARE_API_URL at a non-official origin sends your key and data there instead.

Installation

In SourceWeft

  1. Open ZKshare in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

zkshare-mcp

Published on npm. Stdio Model Context Protocol server for ZKshare — forwards tool calls to POST /api/v1/context with your API key.

Registry name: io.github.sp0oby/zkshare on the official Model Context Protocol Registry preview (verification field mcpName in package.json must stay identical to the name field in server.json).

MCP Registry (registry.modelcontextprotocol.io)

ZKshare participates in (or prepares for) discovery via the official MCP Registry preview. Metadata lives in server.json next to this package; the runnable artifact stays on npm.

Having zkshare-mcp on npm (e.g. v1.0.0) is only half the story: the registry **checks the tarball’s package.json for mcpName — that field was added in repo for v1.0.1. Until 1.0.1 is published to npm, mcp-publisher publish may fail verification. npx -y [email protected] continues to work unchanged for users already on npm.

One-time prerequisites

  1. npm account with publish rights to zkshare-mcp.
  2. GitHub account (sp0oby) matching the io.github.sp0oby/… namespace when using GitHub device login.
  3. Install the publisher CLI (quickstart).

Publish flow (maintainers)

  1. Align versions — bump "version" in package.json, src/version.ts, and the version fields in server.json together.
  2. Build & publish npm — from this directory:
    • pnpm install && pnpm run build
    • npm publish --access public (prepublishOnly runs pnpm run build).
  3. Registry — install mcp-publisher, then from packages/zkshare-mcp/:
    • mcp-publisher login github — device flow; GitHub user must match the namespace (sp0oby).
    • mcp-publisher publish — uploads server.json (omit if you intentionally only ship npm).

Verify after publish

bash
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.sp0oby/zkshare"

If mcp-publisher errors on validation, confirm description stays ≤100 characters (registry JSON schema).

Alternate namespaces

To use DNS or another auth method instead of io.github.sp0oby — change mcpName, server.json → name, and redo ownership verification — see registry docs on authentication and DNS in the same docs tree.

Use (no repo clone)

Needs Node.js ≥ 18.

bash
npx -y zkshare-mcp

Your IDE normally runs this; set env in MCP settings.

Env

VariableRequiredDescription
ZKSHARE_API_KEYYesFrom zkshare.io/api-key
ZKSHARE_API_URLNoDefault https://zkshare.io. Use http://localhost:3000 only for a self-hosted API.

Cursor ~/.cursor/mcp.json

json
{  "mcpServers": {    "zkshare": {      "command": "npx",      "args": ["-y", "zkshare-mcp"],      "env": {        "ZKSHARE_API_KEY": "zk_live_YOUR_KEY_HERE",        "ZKSHARE_API_URL": "https://zkshare.io"      }    }  }}

On Windows, npx ships with Node (npx.cmd).

Develop in the zkShare repo

bash
pnpm installpnpm mcp

Source: src/cli.ts. Version is duplicated in package.json and src/version.ts for maintainers’ release bumps.

Source: packages/zkshare-mcp/README.md at commit db2f626

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

50% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts