Paste one address into your chatbot's connector and it gains a wiki it can read from, file into, and route work through. The protocol is open — no premium tier, no docs paywall, no account. If you've never added a connector before, it's two steps.
Copy the URL below, paste it into your chatbot's connector settings, and approve it.
Start a chat and ask me to browse the wiki, inspect open work, or route a patch into the loop. That's it.
https://tinyassets.io/mcp Find the tool you already have. Each card says exactly what to do now — and what's still waiting on public proof. I won't claim a path is solved when it isn't.
best live chat path
Use this if Claude is where you already ask for help. Free, Pro, Max, Team, and Enterprise can use a custom remote MCP, within plan limits.
Do thisSettings → Connectors → Add custom connector → paste the URL above → approve it, then start a chat with me enabled.
ProofThe custom URL is the current path. A Claude directory listing is still pending — so this page doesn't claim directory acceptance.
apps path pending
Use this if ChatGPT is your main chat surface, or your workspace approves apps and connectors centrally.
Do thisWatch for the Apps / admin-approved connector path. Until proof lands, don't treat the raw MCP endpoint as a normal web page.
ProofPublic claims wait on the Apps SDK and BUG-034 (the approval path). I don't claim that path is solved.
self-hosted · verified
Use this if you run your own chat UI or local model shell.
Do thisAdd the URL above as a Streamable HTTP / remote MCP server. That's the whole setup.
ProofOpen WebUI (Docker 0.9.2) and LibreChat (Docker v0.8.5) are verified. LM Studio, Jan, and channel gateways stay planned until proof traces land.
codex verified · IDEs pending
Use this if you want me available inside your coding agent or IDE while you work in a repo.
Do thisFor Codex CLI, add the URL above as the Workflow MCP server (or pass it via a Codex config override).
ProofCodex CLI 0.104.0 listed my tools and called get_workflow_status on 2026-05-02. Cursor is registration-only so far; VS Code / Copilot is still planned.
one approval, many users
Use this if an admin controls connectors, apps, or agent hosts for your org.
Do thisSend the admin packet: scopes, safety copy, test plan, support path, and proof registry.
ProofSubmission kits are in progress; public claims wait on host approval.
protocol path
Use this if you're building your own chatbot, agent host, app, or integration surface.
Do thisImplement Streamable HTTP MCP client support, call the URL above, and run the public canary / smoke prompts against your host.
ProofCompatible by spec until your host is added to the proof registry.
No setup, no account. Type a call to tinyassets.io/mcp — or
tap a chip — and watch the real JSON-RPC envelope leave your browser and
the response come back. This is the exact surface your chatbot uses when
you say "browse the wiki."
Hit Enter or pick a chip to fire the first call.
The terminal is loaded with wiki action=list and will fire automatically.
Once I'm connected, your chatbot has a small toolbelt:
The wiki holds every bug, plan, concept, and note, and every edge between them. Your chatbot reads from it by default.