A TypeScript implementation of a simple MCP server that exposes datetime information to agentic systems and chat REPLs
Workvivo is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Read-only Workvivo for Claude — feed, news, events, people and search via your signed-in session
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'WORKVIVO_HOST=${WORKVIVO_HOST}' --transport stdio workvivo-mcp '--' npx -y workvivo-mcp
# 2 — ask your agent for something these tools do
# workvivo_digest_space, workvivo_get_document, workvivo_list_events and 20 more
It needs WORKVIVO_HOST: this reads it from your environment, so export it first.
Workvivo costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Workvivo as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads WORKVIVO_HOST (Your organization's Workvivo host, e.g. acme.workvivo.us) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx WORKVIVO_HOST … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'WORKVIVO_HOST=${WORKVIVO_HOST}' --transport stdio workvivo-mcp '--' npx -y workvivo-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
It reaches a system of yours, so it needs settings only you can give it: WORKVIVO_HOST — Your organization's Workvivo host, e.g. acme.workvivo.us.. You set it in your own client’s config, on your machine — this marketplace never holds it.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
23 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Digest a whole space in one Markdown document: every page, linked documents, events, recent posts
| Parameter | Type | Required | Notes |
|---|---|---|---|
| space_id | yes | — | |
| feed_items | integer | no | Recent posts to include (default 10). |
| include_documents | boolean | no | Also download and extract linked documents (default false). |
| include_translations | boolean | no | With include_documents, also extract the language variants linked as "ES"/"PT"/"FR" (default false). |
| max_documents | integer | no | Documents to extract when include_documents (default 10). |
| max_document_chars | integer | no | Characters kept per extracted document (default 4000). |
Read a linked document (PDF, Word, text) as Markdown via your signed-in browser
| Parameter | Type | Required | Notes |
|---|---|---|---|
| document_id | integer | no | The id in a /document/link/<id> link. |
| url | string | no | Or the link itself (/document/link/<id> or /file/<id>). |
| offset | integer | no | Character offset to start from (default 0). |
| max_chars | integer | no | Most characters to return (default …). |
List upcoming events — times in UTC, location, RSVP state
| Parameter | Type | Required | Notes |
|---|---|---|---|
| space_id | yes | — | |
| page | yes | — | |
| view | yes | — |
Read one event in full (meeting passcodes redacted)
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event_id | yes | — | |
| view | yes | — |
Read the home feed, a space's feed or a person's posts
| Parameter | Type | Required | Notes |
|---|---|---|---|
| space_id | yes | — | |
| person_id | yes | — | |
| cursor | string | no | next_cursor from the previous page (home/space feeds). |
| page | yes | Page number for a person's feed (default 1). | |
| view | yes | — |
List company news articles — all, one space's, or the featured stories
| Parameter | Type | Required | Notes |
|---|---|---|---|
| space_id | yes | — | |
| featured | boolean | no | Only the featured stories (ignores page and space_id). |
| page | yes | — | |
| view | yes | — |
Read one news article in full, body as plain text
| Parameter | Type | Required | Notes |
|---|---|---|---|
| article_id | yes | — | |
| view | yes | — |
List your notifications with unread counts (does not mark anything read)
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | yes | — | |
| view | yes | — |
List a space's (or global collection's) content pages as a tree
No parameter schema on file.
Read one content page as Markdown, with an index of the pages and documents it links to
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | no | The page slug or id. Omit for the landing page. | |
| format | string | no | markdown (default) or json. |
| include_links | boolean | no | Append the "Links on this page" index (default true). |
Search the people directory by name
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Name (or part of one) to search for. |
| page | yes | — | |
| view | yes | — |
Read a colleague's profile — role, manager, bio, expertise
| Parameter | Type | Required | Notes |
|---|---|---|---|
| person_id | yes | — | |
| view | yes | — |
Read who you are signed in to Workvivo as: name, email, job title, department, location, cost
| Parameter | Type | Required | Notes |
|---|---|---|---|
| view | yes | — |
List the people on your team in Workvivo (as the directory defines it — your manager and peers or
| Parameter | Type | Required | Notes |
|---|---|---|---|
| view | yes | — |
Read one post (update) or shoutout (kudos) in full
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | yes | "update" for a post, "kudos" for a shoutout. |
| id | yes | — | |
| view | yes | — |
List recent shoutouts — who thanked whom, and why
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | yes | — | |
| view | yes | — |
Read the comments on a post, article, event or shoutout, with commenter names
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | yes | The item type: update (a post), article, event or kudos (a shoutout). |
| id | yes | — | |
| view | yes | — |
Read a Q&A question with its answers, votes and the accepted answer
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question_id | yes | — | |
| page | yes | Answers page (default 1). | |
| view | yes | — |
GET any other read-only Workvivo API path (credential fields redacted)
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | yes | Path relative to /api/, with an optional query string. |
Full-text search across articles, posts, events, people, spaces and documents
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | What to search for. |
| types | array | no | Content types to search (default: …). "user" = people, "term" = teams/departments, "docs" = documents. |
| page | yes | — | |
| view | yes | — |
List your spaces, all spaces, trending spaces, or search spaces by name
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scope | string | no | Which spaces (default "mine"; ignored when query is set). |
| query | string | no | Search spaces by name. |
| page | yes | — | |
| view | yes | — |
Read one space's details
| Parameter | Type | Required | Notes |
|---|---|---|---|
| space_id | yes | — | |
| view | yes | — |
Verify the fetchproxy bridge, the extension and your Workvivo sign-in end-to-end
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Workvivo or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.2.0. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Workvivo can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.