
Inkbloc
io.github.epsteinjPublished by GitHub account epsteinjv0.1.2Updated Oct 24, 2026
Collaborative document workspace with interactive AI blocks
Overview
Inkbloc connects an assistant to a collaborative document workspace with interactive AI blocks, via a local npm package and an API key.
- What you can do
- The listing gives no tool list, so capabilities are inferred from the description only.
- It presents a collaborative document workspace in which documents can be shared and worked on with others.
- It adds interactive AI blocks inside those documents, so assistant-driven content can live alongside written material.
- No specific read, write or search operations are documented in the supplied material.
- When to use it
- Consider it if your team keeps work in Inkbloc documents and you want an assistant to work with that collaborative workspace and its AI blocks. Without a tool list or README, verify the actual capabilities before relying on it.
- Requirements
- Runs as a local process over stdio, installed from the npm package inkbloc-mcp, so a Node.js runtime is needed. Requires an Inkbloc API key supplied through the INKBLOC_API_KEY environment variable; the key is obtained from Inkbloc settings. Desktop client only.
Installation
In SourceWeft
- Open Inkbloc in the dashboard and add it to a workspace.
- 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.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.1.2LatestSep 16, 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.