Inventor Studio

io.github.Heavens-LavaPublished by GitHub account Heavens-Lavav1.0.3Updated Oct 24, 2026

Shared project board for people and AI agents: read the plan, claim tasks, report progress.

VerifiedSTDIODesktop onlyProductivity & Workflow

Overview

AI-generated overview

A local MCP server that connects an assistant to a shared Inventor Studio project board so it can read the plan, claim tasks and report progress.

What you can do
Read the shared project plan and board for a single Inventor Studio project, so the assistant can see what work is planned and who owns it. Claim tasks from the board on the assistant's behalf. Report progress back to the board so people and other agents see current status. All activity is scoped to the one project the supplied token belongs to.
When to use it
Useful when a team coordinates work with AI agents on a shared Inventor Studio project board and wants the assistant to pick up tasks and post status updates rather than working from a pasted plan.
Requirements
Runs locally as a desktop-only process, started with npx from the npm package inventor-studio. Needs an Inventor Studio project token (isk_...) from the project's Agents tab, supplied as the INVENTOR_TOKEN environment variable. No other authentication is declared.
Before you install
Requires a project token passed as INVENTOR_TOKEN; it grants access to that one project, so treat it as a secret. The server claims tasks and reports progress, which changes shared board state visible to other people and agents. Review what it posts before relying on it for coordination.

Installation

In SourceWeft

  1. Open Inventor Studio 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.

Tools

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

Version history

2
  1. v1.0.3LatestOct 20, 2026
  2. v1.0.0Oct 9, 2026

Score

25% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.