Mmcp.market

MCP server

by monnet.ai·ai.monnet/mcp·v0.9.5

MCP server for Monnet — motions, plans, files, approvals, and the team's company brain.

B82/100grade B
What users say
No reviews yet
Be the first
Safety scan
B82/100

full report

Adoption
Growing

0 stars1.1k downloads/wk

Reviews

Write one

Nobody has reviewed MCP yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

MCP tools (32, 10 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • approve

    Approve a plan step on a motion. Requires editor role on the motion.

  • ask_monnet

    Ask Monnet a question in the context of a specific motion.

  • commentwrite action

    Post a public comment on a motion, either top-level or as a reply within

  • create_playbookwrite action

    Write a new playbook for a workspace: the instructions Monnet follows when a request lands on that recurring workflow. Call list_playbooks first. Show the draft to the person and get their agreement before calling this — it becomes how Monnet handles that workflow for the whole team. Owners and admins only.

  • create_threadwrite action

    Open a new thread in a Monnet workspace from a free-form prompt. A thread is a pre-motion conversation: Monnet picks it up in the background and shapes the idea with the author, and it becomes a motion — a doc, a plan, people to coordinate — only when it earns one. Returns the thread's id and URL immediately; call `get_motion` with the returned short_id to read where it got to.

  • create_wiki_folderwrite action

    Create a folder in the company brain. Only once a subject already carries several pages that want holding together — a brain the size of a team's is a handful of folders and a couple of dozen pages,

  • create_wiki_pagewrite action

    Create a page in the company brain. Call get_wiki_tree first: most material belongs on a page that already exists, and a brain with one page per source is a filing cabinet, not a brain.

  • delete_wiki_folderwrite action

    Delete a company-brain folder. Its pages are re-parented, not deleted — deleting a folder never throws away a document. The user is asked to confirm before it happens.

  • delete_wiki_pagewrite action

    Delete a company-brain page, with its comments and its version history. Not reversible, and links pointing at it break.

  • delete_wiki_sourcewrite action

    Delete one of the company brain's raw source files, and the stored document with it. Not reversible. Every page that linked it is repaired in the same move — the link becomes [Source removed], and what the page says is left untouched.

  • edit_playbook

    Revise a playbook the workspace already has. Pass only the fields that change — the others are carried over. The previous version is not kept, so this stops to ask the person before it writes. Owners and admins only.

  • edit_wiki_page

    Change a company-brain page: rename it, and/or replace an exact string in its body. Read the page first — the match is literal, whitespace included.

  • get_inbox

    Fetch the user's inbox — the motions they follow, in two buckets: 'priority' is what is waiting on them

  • get_motion

    Read a Monnet motion's full details — summary, body, status, priority, plan steps with assignees, member roles,

  • get_wiki_schema

    Read the rules this team's company brain is built on — how pages are typed and templated, when to create one versus extend one, and the link format.

  • get_wiki_tree

    List every folder and page in a workspace's company brain, nested, with each page's id.

  • list_motions

    List motions in a workspace, filterable by status. Returns short ids so you can follow up with get_motion on a specific one.

  • list_playbooks

    The playbooks a workspace has written for Monnet — a playbook is how the team wants one recurring workflow handled, and Monnet loads it when a request lands on it. Call this before writing one: a workflow that already has a playbook wants an edit, not a second copy.

  • list_wiki_sources

    List the raw material feeding a workspace's company brain: uploaded files, plus motions the team closed and shared workspace-wide.

  • list_workspaces

    List the Monnet workspaces you are a member of, plus any you have been invited to and not

  • mark_wiki_source_ingested

    Take a source out of the company brain's queue, once what it says is in the wiki.

  • monnet_whoami

    Verify your Monnet MCP connection and list the API keys on your account.

  • move_wiki_node

    Move a page or a folder into another folder, or to the wiki root. Links survive a move — they point at the id, not the path — so reorganising is safe.

  • push_wiki_source

    Add a text document to a workspace's company brain as raw material — notes, a transcript, a spec. The nightly job reads it and folds what it says into the pages it belongs on.

  • read_motion_file

    Read a file attached to a motion. Text, markdown, CSV, JSON and source files come back as their contents;

  • read_wiki_page

    Read one company-brain page's full contents, as markdown. Read the page before editing it — edit_wiki_page replaces an exact string, and the ## Sources section at the bottom has to be kept current.

  • read_wiki_source

    Read one of the company brain's raw source files — the material a wiki page was compressed FROM.

  • reject

    Reject a plan step on a motion, with an optional reason. Requires editor role on the motion.

  • rename_wiki_folder

    Rename a company-brain folder. Safe — nothing links to a folder by name, and the pages inside keep their ids.

  • requeue_wiki_sourcewrite action

    Put a digested source back in the company brain's queue, so the nightly job reads it again.

  • search_wiki

    Search INSIDE company-brain pages — their titles and their bodies. Use it to find where a fact already lives before writing it somewhere new;

  • update_motionwrite action

    Update a motion's summary, body, priority, or plan. All fields are optional —

Public scan report

scanner v0.1.5 · 2026-09-19 · same rubric, same numbers if you re-run it

no findings
  • Code scan89 source files scanned25/25
  • Live reliabilityno gateway calls yet and no remote to proben/a
  • Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 1 days ago15/15
  • Maintainer identitynamespace and repository owner differ; GitHub account older than a year; website matches verified namespace7/10
Overall 82/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

Install directly

Runs npx -y @monnet/mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add mcp -- npx -y @monnet/mcp
Add to Cursor

MCP: common questions

Is MCP server safe?
Mostly: it is graded B (82/100). Read the MCP safety report
How do I install MCP?
It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
Does MCP need an API key?
Yes. The registry entry asks for MONNET_API_KEY.
Is MCP maintained?
The last commit was 3 days ago (2026-09-18). The latest release is v0.9.5.

More from monnet.ai