Monnet MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Monnet workspace motions, plans and approvals: Do workspace operations retain clear approval requirements rather than turning plan creation into automatic commitment?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Working with Monnet workspace motions, plans, comments and approvals from MCP clients.

What we know

Monnet workspace MCP exposing identity/workspace lookup, motion creation/update, comments, plan-step approvals and Monnet queries.

Maintenance / activity evidence

@monnet/mcp 0.9.15 published 2026-09-25T12:30:47.376Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Workspace/member role; some actions require editor role. Writes: Create/update motions; Comment; Approve/reject plan steps.
Monnet API key.
Sensitive access: Workspace data, API key

Write-capable collaboration integration; role boundaries and elicitation for approvals matter.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do workspace operations retain clear approval requirements rather than turning plan creation into automatic commitment?

The bounded review of the publisher's documented Monnet workspace motions, plans and approvals and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Write-capable collaboration integration; role boundaries and elicitation for approvals matter.
Workspace/member role; some actions require editor role.
Monnet API key.
Workspace motion/plan data are sent to Monnet service.
Reviewed write actions: Create/update motions; Comment; Approve/reject plan steps
Sensitive access: Workspace data, API key
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
Repository identity
Full public security/retention documentation
Requires MONNET_API_KEY.
Approval/comment workflows have role/elicitation requirements.
Public package evidence is thinner than repo-backed entries.

Original activity observations

@monnet/mcp 0.9.15 published 2026-09-25T12:30:47.376Z

Technical identity

npm/@monnet/mcp

Exact implementation source: https://www.npmjs.com/package/@monnet/mcp ↗
Reviewed resource type: MCP Server
Package identity: npm:@monnet/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 7, 2026

Package registry ↗
@monnet/mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Publisher provides paired uninstall `npx -y @monnet/mcp uninstall`; credential from monnet init or MONNET_API_KEY.
publisher documented install or connect · Publisher instructions
npx -y @monnet/mcp install
Configure / authenticate
MCP100 setup guide
Run publisher `npx -y @monnet/mcp install` to create supported client registration, or use README manual MCP JSON. Credential from `monnet init` or MONNET_API_KEY. Inspect generated config.
claude desktop or cursor mcpServers json · MCP100 composed guide
{ "mcpServers": { "monnet": { "args": [ "-y", "@monnet/mcp" ], "command": "npx", "env": { "MONNET_API_KEY": "mnk_REPLACE" } } } }
Check connection
Suggested check
Use published onboarding/read-only status in Monnet MCP after installed registration; do not create or modify work items.
Remove / uninstall / revoke
MCP100 setup guide
Publisher-provided paired command `npx -y @monnet/mcp uninstall` removes the corresponding host registration. Confirm affected clients before running. Package and account key cleanup are separate.
MCP client unregister, stopping hosted processes, package uninstall, OAuth disconnect and token revocation are distinct actions.
A claude mcp remove command is only valid for Claude Code when the local registration actually has that name. Other MCP hosts require their own UI/config cleanup.
Separate provider credential revocation · publisher documented: Monnet publisher `npx -y @monnet/mcp uninstall` removes MCP registration and stored key and ATTEMPTS TO REVOKE ITS API KEY; if server-side revoke fails it reports this and directs user to Settings → Monnet MCP. Do not claim success unconditionally.
Publisher-managed uninstall / registration cleanup · Publisher instructions
npx -y @monnet/mcp uninstall

Official Documentation & Sources

What it does

Monnet workspace MCP exposing identity/workspace lookup, motion creation/update, comments, plan-step approvals and Monnet queries.

Capability: Productivity & Collaboration
Resource type: MCP Server
Best fit: Working with Monnet workspace motions, plans, comments and approvals from MCP clients.

Representative uses

List workspaces/inbox
Create/update motions
Comment on work
Approve/reject plan steps

Limitations

Requires MONNET_API_KEY.
Approval/comment workflows have role/elicitation requirements.
Public package evidence is thinner than repo-backed entries.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Monnet API key.
Permissions: Workspace/member role; some actions require editor role.
Data handling: Workspace motion/plan data are sent to Monnet service.
Cost: unknown
Risk and cautions: Write-capable collaboration integration; role boundaries and elicitation for approvals matter.

Access scope and cautions

Write actions: Create/update motions Comment Approve/reject plan steps
Sensitive access: Workspace data API key
Risk level: moderate

FAQ

Based on reviewed evidence as of 2026-10-07. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: List workspaces/inbox; Create/update motions; Comment on work; Approve/reject plan steps.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @monnet/mcp. Recorded transport: stdio. Recorded environment-variable notes: MONNET_API_KEY; MONNET_API_URL optional. No configuration values are supplied here. Prerequisites: Node/npm. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Monnet API key.

Can it modify data or perform write operations?

Documented write actions include: Create/update motions; Comment; Approve/reject plan steps. Recorded permission boundary: Workspace/member role; some actions require editor role.

What data-handling boundary should I consider?

Workspace motion/plan data are sent to Monnet service. Recorded sensitive-access context: Workspace data; API key.

What limitations and risks should I check before use?

Write-capable collaboration integration; role boundaries and elicitation for approvals matter. Requires MONNET_API_KEY. Approval/comment workflows have role/elicitation requirements. Public package evidence is thinner than repo-backed entries. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

Is this an official MCP?

Monnet is listed as First-party MCP in MCP100’s current evidence.