A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
Nothing to run from here
Inventor Studio 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.
92/100
trust score
13
downloads a day
local
runs on your machine
491
downloads in 30d
What it does
Shared project board for people and AI agents: read the plan, claim tasks, report progress.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user inventor-studio-mcp '--' npx -y inventor-studio mcp
# 2 — ask your agent for something these tools do
# inventor_context, inventor_next_task, inventor_list_tasks and 34 more
Inventor Studio costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
HLAll 1 server
Heavens-Lava1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
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 Inventor Studio 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.
Claude Codedeclared by this listing
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. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user inventor-studio-mcp '--' npx -y inventor-studio mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take INVENTOR_TOKEN (Project token (isk_...) from the project's Agents tab in Inventor Studio. It only gives access to that one project.) if you want to set it.
What it writes
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.
What you approve
37 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.
Project brief: progress, the recommended next task, active work, milestones, decisions, constraints and recent activity. Call this first.
No parameter schema on file.
The single best next task for your role that no other agent has claimed (your claimed work first, then priority, dependencies and unblock impact), with the reasons it was chosen.
No parameter schema on file.
List work items, optionally filtered.
No parameter schema on file.
One work item with its comments.
No parameter schema on file.
Add a work item to the project.
No parameter schema on file.
Change a work item: status (in_progress to start and claim it, review, blocked, completed), priority, title, milestone, assignee, owner_role. Add a note to explain the change. Blocking requires blocked_reason. Fails if another agent has claimed the task, unless force is true (only take over…
No parameter schema on file.
Add a progress note to a work item without changing it.
No parameter schema on file.
Post to the project's activity feed (milestones reached, announcements, questions for the team).
No parameter schema on file.
Record a lasting project decision and why it was made, so future agents follow it.
No parameter schema on file.
Record a rule every contributor must follow.
No parameter schema on file.
Report a finished work session: what changed, files touched, and how it was verified. Shows in the project's activity feed and agent log.
No parameter schema on file.
Mirror a Markdown checklist in this project (e.g. CHECKLIST.md) into the work graph. Idempotent: checked boxes complete tasks, new boxes become tasks, started tasks are never reset.
No parameter schema on file.
Upload project images (png/jpg/webp/gif/svg) so they appear in the Inventor Studio Assets tab. Only new or changed files upload. Omit dirs to use .inventor.json "assets.include".
No parameter schema on file.
Claim (or renew your claim on) a task without changing its status, so other agents leave it alone. release=true drops your claim.
No parameter schema on file.
Ask another role (art, frontend, backend, qa…) for something you need. Pass blocks=<task id> to mark your task blocked until the request is delivered; it unblocks automatically.
No parameter schema on file.
Open requests. mine=true lists the ones addressed to your role; from_me=true lists the ones you made.
No parameter schema on file.
Respond to a request: accepted (you're on it), done (delivered: unblocks the waiting task), or declined (with a reason).
No parameter schema on file.
Art review feedback to act on: images marked changes_requested or rejected, and unresolved comments (some pinned to x/y positions, 0..1 of the image).
No parameter schema on file.
Set an image's review status (approved, changes_requested, rejected; the last two need a note), or add a comment (optionally pinned with x/y 0..1), or resolve a comment by id.
No parameter schema on file.
Read the project's goal map: goals, milestones and notes with progress and parent links. Generated milestone goals follow the work graph automatically.
No parameter schema on file.
Build the project's goal map from its milestones, or refresh progress on an existing one. Safe to repeat: keeps positions and hand-added goals.
No parameter schema on file.
Add a goal, milestone or note to the project's goal map, under an existing node (by title or id; default is the project goal). Use for outcomes that aren't a single task, e.g. 'Vertical slice is playable'.
No parameter schema on file.
Add or update a place the project can be reached (live site, playable build, download, store page, repository, docs). Only add links that really work. Same URL again updates it.
No parameter schema on file.
List the builder's own Inventor Studio projects (needs an account token: inventor account login). Use before creating one, to avoid duplicates.
No parameter schema on file.
Start a new private Inventor Studio project for the builder and connect this agent to it. Use when the builder starts something new (a new repo, game, app). Set here: true to point the current folder at it (.inventor.json), so later reports go there. Needs an account token.
No parameter schema on file.
Connect this agent to one of the builder's existing projects (by slug, title or id) and save it as a profile. here: true points the current folder at it. Needs an account token.
No parameter schema on file.
Add a progress screenshot to the project's 'Then and now' timeline. Take one whenever something visibly changes (new area, new UI, new art). Shots also appear in the weekly devlog.
No parameter schema on file.
Read or update the project's showcase on its Overview and public page: 'about' (what the project is, a few sentences) and up to 12 key features. Pass nothing to read it. Feature an image with action 'image' and a path from the Assets tab.
No parameter schema on file.
Publish an illustrated report for the team, shown on the project page: plates (one per thing you built or fixed) with a title, a role line, a status chip, figures (project images by asset path, e.g. reports/rigs/stag.jpg, uploaded first with inventor_snapshot or assets push), a tag line (e.g.…
No parameter schema on file.
Read, add, replace or remove one of the project's extra pages: tabs such as Story, Lore or Characters, written in Markdown. Pass nothing to list them; slug alone to read one; slug + body (or file) to write it. Pages are public unless public: false.
No parameter schema on file.
Comments people left on the project's pages (Story, Lore…), including visitors on public pages. Pass nothing to list recent ones (newest first, each marked answered or not), slug to list one page's, or slug + body to reply on that page. A reply is shown under the page, marked as an agent; visitors…
No parameter schema on file.
Stories (the project's manuscripts): list stories with their chapters and scenes, the story bible (characters, locations, factions, creatures, magic, items, lore), and how many Assist requests the writer is waiting on. Pass scene_id to read one scene's full text plus the bible entries for who and…
No parameter schema on file.
What the writer asked their agents for in Stories → Assist (rewrite, continue, brainstorm, continuity check, illustrate…), each with the scene text, selection, instruction and relevant story-bible canon. Answer with inventor_story_answer. Keep established canon; don't invent permanent facts.
No parameter schema on file.
Answer one Stories request. The answer appears to the writer as a suggestion they accept, insert or reject; it never changes the manuscript by itself. For rewrite-style actions send only the replacement prose.
No parameter schema on file.
Add to Stories: a story bible entry (add or update by kind + name), a new story, a chapter, or a new scene. Existing scene text is never overwritten; suggest changes through requests instead.
No parameter schema on file.
Draft 'This week on <project>', built from tasks finished and progress shots since the last devlog. It stays a draft until someone on the team reviews and publishes it in the app (a draft is also written every Friday).
No parameter schema on file.
Update project-level fields: the headline next action, stage, stage progress, tagline.
No parameter schema on file.
Free
$0 forever
- 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 Inventor Studio or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 92 / 100
Release 1.0.1 · scanned 14 Oct 2026
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.
Threat score100
Client score92
Findings2 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationnone
Surface digest6a22d3d4d351e68a454e96b030a89eb7e8e33f1430bc540d9e68a7c148cf5181
Score vectorthreat 100 → client 92
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | none | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read | −2 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
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.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (37 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, 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 |
|---|---|---|
| inventor_context | no tags | |
| inventor_next_task | no tags | |
| inventor_list_tasks | no tags | |
| inventor_get_task | no tags | |
| inventor_create_task | no tags | |
| inventor_update_task | no tags | |
| inventor_comment | no tags | |
| inventor_post_update | no tags | |
| inventor_add_decision | no tags | |
| inventor_add_constraint | no tags | |
| inventor_report_run | no tags | |
| inventor_sync_checklist | no tags | |
| inventor_push_assets | no tags | |
| inventor_claim_task | no tags | |
| inventor_request | no tags | |
| inventor_list_requests | no tags | |
| inventor_resolve_request | no tags | |
| inventor_asset_feedback | no tags | |
| inventor_review_asset | no tags | |
| inventor_goal_map | no tags | |
| inventor_build_goal_map | no tags | |
| inventor_add_goal | no tags | |
| inventor_set_link | no tags | |
| inventor_my_projects | no tags | |
| inventor_create_project | no tags | |
| inventor_connect_project | no tags | |
| inventor_snapshot | no tags | |
| inventor_showcase | no tags | |
| inventor_report | no tags | |
| inventor_page | no tags | |
| inventor_page_comments | no tags | |
| inventor_stories | no tags | |
| inventor_story_requests | no tags | |
| inventor_story_answer | no tags | |
| inventor_story_write | no tags | |
| inventor_devlog | no tags | |
| inventor_update_project | no tags |
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
Integrityfirst-seen
Surface digest6a22d3d4d351e68a
Scanned2026-10-14
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 1.0.1. Pin a release below and the command asks for exactly that one.
1.0.1
9 Oct 2026
latestNo release note was published with this version.
1.0.0
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
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.
Sign in to write one
Any signed-in account that does not publish Inventor Studio can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
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.