Productivity · Remote MCP server
Mochii work graph
Mochii work graph: projects, tasks, meetings. Stiki OAuth. Not Nexus memory.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.chibitek/mochii- Version
- 2.4.2
- Status
- Active
- Category
- productivity
- Transport
- Streamable HTTP
- Published
- 2026-09-06
- Updated
- 2026-09-06
- Publisher
- com.chibitek · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via the domain chibitek.com · how
- Website
- mochii-mcp.chibitek.com
- Repository
- github.com/chibitek/mochii-mcp-server
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mochii-mcp.chibitek.com/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Mochii work graph
Mochii work graph is a remote MCP server: there is nothing to install. Its endpoint is https://mochii-mcp.chibitek.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from com.chibitek
| Server | Runs |
|---|---|
| Nexus MemoryOwner-scoped Nexus memory: search, facts, captures, KYC. Not Mochii's work graph. | Remote · HTTPLive check: sign-in required |
More productivity servers
| Server | Runs |
|---|---|
| MnemosyneKnowledge commons for agent lessons, questions, and direct long-form peer discussions. | Remote · HTTPLive check: ✓ handshake |
| MobAn AI-first personal CRM you run in natural language: contacts, reminders, notes, and more. | Remote · HTTPLive check: sign-in required |
| MobileValidateCheck phone numbers (WhatsApp, Telegram, carrier, spam reputation) and e-mail addresses. | Remote & Local · HTTP, stdioLive check: sign-in required |
| MochifyImage and PDF toolkit: convert to AVIF/WebP/JXL, resize, crop, remove backgrounds, optimize PDFs. | Remote & Local · HTTP, stdioLive check: sign-in required |
| MochiPDFRemote MCP server for HTML-to-PDF and screenshots with OAuth and API-key auth. | Remote · HTTPLive check: sign-in required |
| modelmuxModel multiplexer - route tasks to Codex, Gemini, and Claude CLIs with routing. | Local · stdio |
| Modusop MCPMCP server for ModusOp - projects, tasks, time tracking, and retainers for AI assistants. | Local · stdio |
| Molt2MeetDispatch real-world physical tasks to verified human operators. Escrow or direct-settlement. | Remote · HTTPLive check: ✓ handshake |