Skip to main content
This page groups three common MCP import patterns:
  • large tool surfaces that need taxonomy refinement
  • live commercial MCPs with product-shaped workflow grouping
  • authenticated imports that use custom headers

​
Firecrawl-style

If your MCP has many granular tools, start with deterministic import and then run taxonomy refinement:
Repository example: example/firecrawl-plugin Use this pattern when the first import is valid but too lexical or too fragmented.

​
Sumble-style

Use a live commercial MCP when you want a proof-quality example with real auth and workflow grouping. Full walkthrough: Typical commands:

​
PlayKit-style

Use custom header auth during import:
Use this pattern when the provider expects an API key in a header other than Authorization.

​
Which example to start from

  • choose Firecrawl-style when the tool surface is large and needs semantic cleanup
  • choose Sumble-style when you want a high-signal live MCP example with workflow grouping
  • choose PlayKit-style when the main complication is authenticated import via a custom header