AgentSkillsCN

fusebase

用于与 Fusebase MCP 服务器交互的技能。当用户希望与 Fusebase 工作空间、页面、文件夹、任务、标签、文件或成员进行交互时使用。涵盖身份验证、缓存管理、API 探索与持续优化。

SKILL.md
--- frontmatter
name: fusebase
description: Skill for interfacing with the Fusebase MCP server. Use this when the user wants to interact with Fusebase workspaces, pages, folders, tasks, tags, files, or members. Covers auth, caching, API discovery, and continuous improvement.
triggers:
  - fusebase
  - nimbus
  - workspace pages
  - fuse base
  - inkabeam

Fusebase MCP Skill

Interface with Fusebase (formerly Nimbus Note) via the reverse-engineered MCP server at c:\scripts\fusebase-mcp.

Known Workspaces (Cached)

NameWorkspace IDOrg IDHost
Ryan45h7lom5ryjak34uu268r1inkabeam.nimbusweb.me
Inkabeam44ieqib7z0eltarru268r1inkabeam.nimbusweb.me

Full cache at c:\scripts\fusebase-mcp\data\workspace_cache.json

Quick Reference

WhatWhere
MCP serverc:\scripts\fusebase-mcp\dist\index.js
Auth scriptnpx tsx scripts/auth.ts (in project dir)
Discovery scriptnpx tsx scripts/discover.ts (in project dir)
Configc:\scripts\fusebase-mcp\.env
Workspace cachec:\scripts\fusebase-mcp\data\workspace_cache.json
API logc:\scripts\fusebase-mcp\data\api_log.jsonl

Standard Operating Procedures

SOP: Create a Page

  1. •Resolve workspace — Check "Known Workspaces" table above for ID. If not found, call list_workspaces to refresh.
  2. •Optional: Resolve folder — Call list_folders with workspace ID if placing in a specific folder.
  3. •Create — Call create_page with workspaceId, title, and optional folderId.
  4. •Confirm — Verify the response includes globalId and title.

SOP: Read Workspace Content

  1. •Resolve workspace — Use cached ID from table above.
  2. •List structure — Call list_folders to get folder tree.
  3. •List pages — Call list_pages (optionally filtered by folder).
  4. •Get detail — Call get_page for specific page metadata.

SOP: Auth Troubleshooting

  1. •Auto-retry — Server auto-retries on 401 via headless Playwright.
  2. •Manual MCP — Call refresh_auth with interactive: true.
  3. •Manual CLI — cd c:\scripts\fusebase-mcp && npx tsx scripts/auth.ts

Caching Strategy

LevelCacheDurationRationale
Workspacesworkspace_cache.jsonPersistentRarely change — ID + name + folder structure
Foldersworkspace_cache.jsonPersistentRarely change — cached per workspace
PagesIn-conversation onlySessionChange frequently — always fetch fresh
TasksIn-conversation onlySessionChange frequently — always fetch fresh
Tags/Labelsworkspace_cache.jsonPersistentRarely change

Cache Refresh

Call list_workspaces to rebuild the full workspace + folder cache.

Available MCP Tools (15)

Auth

ToolDescription
refresh_authRefresh session cookies via Playwright (headless or interactive)

Content

ToolDescription
list_workspacesList all workspaces in the org
list_pagesList pages in a workspace (filterable by folder)
get_pageGet detailed metadata for a specific page
get_recent_pagesRecently accessed pages
create_pageCreate a new page in a workspace
list_foldersList all folders in a workspace

Files & Attachments

ToolDescription
get_page_attachmentsGet attachments for a page
list_filesList all files in a workspace

Metadata

ToolDescription
get_tagsWorkspace or page tags
update_page_tagsSet tags on a page
get_labelsColored label categories

Organization

ToolDescription
get_membersWorkspace or org members
get_org_usageStorage, member count, AI usage
search_tasksSearch tasks (by workspace/page)

Learnings Log

Document discoveries during each interaction. Batch improvements and implement together.

2026-02-08 — Initial Build

  • •Discovery: Fusebase has no public API; internal endpoints work via cookie auth
  • •Discovery: POST requests to Fusebase API succeed even when Node.js terminal output appears to hang — the API is slow to respond but does work
  • •Discovery: Two pages were successfully created via create_page but response monitoring failed due to terminal output truncation
  • •Pattern: GET requests respond faster than POST requests to Fusebase API
  • •Pattern: Workspace IDs are 16-char alphanumeric strings
  • •Improvement needed: Better response logging so we can confirm operations succeed
  • •Improvement needed: Workspace ID caching to avoid repeat lookups

Improvement Queue

PriorityImprovementStatus
P0Workspace cache (avoid repeat lookups)✅ Implemented
P0API response logging✅ Implemented
P1Cache folders per workspace✅ In workspace cache
P1update_page tool (edit page content)🔲 Not yet
P1delete_page tool🔲 Not yet
P2search_pages tool (full-text search)🔲 Not yet
P2move_page tool (change parent folder)🔲 Not yet

Architecture

code
c:\scripts\fusebase-mcp\
├── src/
│   ├── index.ts       # MCP server (15 tools)
│   ├── client.ts      # HTTP client with 401 auto-retry + logging
│   └── types.ts       # TypeScript interfaces
├── scripts/
│   ├── auth.ts        # Playwright cookie capture
│   └── discover.ts    # API endpoint crawler
├── data/
│   ├── workspace_cache.json  # Workspace + folder cache
│   ├── cookie.json    # Cookie expiry metadata
│   └── api_log.jsonl  # API call history
├── .browser-data/     # Playwright persistent profile
└── dist/              # Compiled JS

Extending the Server

  1. •Run npx tsx scripts/discover.ts to find new endpoints
  2. •Add methods to src/client.ts
  3. •Add types to src/types.ts
  4. •Register tools in src/index.ts
  5. •Compile: npx tsc
  6. •Update this skill file with new tools + learnings