Offline Protocol packages, workflows and integration guides over HTTPS. Read-only.
Scored across 15 tools
The list/get/search triples for packages, skills, and workflows are clearly distinct, and generate_architecture, resolve_packages, and preview_scaffold target different stages of the planning lifecycle. Minor overlap exists: search_packages and search_capabilities can both surface packages via capability, and get_template and preview_scaffold both report template/file details, so a few boundary calls are possible.
All 15 tools use lowercase snake_case with a consistent verb_noun structure (get_package, list_skills, search_workflows, generate_architecture). The pattern holds across every tool with no stylistic deviations.
Fifteen tools is at the upper end of the ideal range but remains well-scoped for a read/planning server: three resource families each get list/get/search, plus capability, example, template, scaffold, and architecture helpers. It is slightly heavy and a couple of the parallel triples could be consolidated, but no tool feels gratuitous.
Core read/planning coverage is solid, with list/get/search for packages, skills, and workflows plus capability, example, and scaffolding tools. Minor asymmetries remain: no list_templates, get_example, or get_capability, so some search results are dead ends for detailed retrieval, but agents can work around these gaps.
Turn an app idea into an Offline Protocol plan: matching workflow, platform, packages, starter template and architecture documents, returned as text. Returns an error, not a guess, when the idea needs a framework the planner has no starter for (such as Flutter or native Swift) unless a platform is given.
Inputs: prompt (required), platform.
Get one Offline Protocol package's registry entry: capabilities, peer dependencies, platform requirements, integration notes and examples.
Inputs: name (required).
Read one Offline Protocol integration guide (skill): API usage, code samples and practices for one area, such as mesh networking, identity or groups.
Inputs: name (required).
Get an Offline Protocol starter template's metadata: variables, post-generation steps, notes and file list. Creates no files.
Inputs: name (required).
Get one Offline Protocol workflow in full: capabilities, packages per platform, starter templates and the reference architecture (screens, services, events and data models).
Inputs: name (required).
List every Offline Protocol SDK package in the public registry with its version, supported platforms, capabilities and license.
Inputs: no named parameters.
List every Offline Protocol integration guide (skill) with the situations it covers.
Inputs: no named parameters.
List every Offline Protocol product workflow with its capabilities and supported platforms.
Inputs: no named parameters.
Preview what an Offline Protocol starter would contain for an app: workflow, template, packages and file list. A dry run that writes nothing; creating the project needs the local Offline Protocol CLI.
Inputs: name (required), prompt, platform, template, +3 more.
Resolve Offline Protocol packages, or a workflow, for one platform into an exact install list: versions, required and peer dependencies, install commands and license notes.
Inputs: platform (required), packages, workflow.
Search Offline Protocol capabilities, such as peer discovery or encrypted groups, and see which packages, workflows and guides provide each one.
Inputs: query (required).
Search Offline Protocol reference example apps and integrations by keyword.
Inputs: query (required).
Search Offline Protocol SDK packages by name, capability or description keywords. Returns ranked matches.
Inputs: query (required).
Search Offline Protocol integration guides (skills) by topic. Returns matching guide names.
Inputs: query (required).
Search Offline Protocol product workflows, such as local handoff, nearby chat, backend delivery or OfflineID sign-in, by keywords describing what you want to build.
Inputs: query (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Read-only U.S. healthcare dataset metadata, schemas, immutable downloads, and checksums.
Read-only catalog of app-building materials: fonts, APIs, MCP servers, libraries, templates, data.
Read-only access to Kanbai's public project templates and SOPs. Public, no authentication.
Read-only MCP server over the developer docs for the portfolio's JSON API, MCP, A2A and NLWeb.
Add one secure layer between your agents and this server.