What can @anthropic-ai/mcpb do?

mcp bundle schema validation and compilation, tool definition and resource bundling with dependency resolution, mcp bundle type generation from typescript/javascript definitions, bundle metadata and manifest generation, bundle distribution and deployment packaging, bundle testing and validation framework, bundle versioning and compatibility management, interactive bundle configuration and scaffolding

@anthropic-ai/mcpb

MCP ServerFree

Tools for building MCP Bundles

Open Source

/ 100

8 capabilities

Capabilities8 decomposed

mcp bundle schema validation and compilation

Medium confidence

Validates MCP bundle configurations against the Model Context Protocol specification schema, then compiles them into optimized bundle artifacts. Uses JSON schema validation to enforce required fields, type constraints, and nested resource definitions before packaging, ensuring runtime compatibility with MCP clients and servers.

Solves for

I need to validate my MCP bundle configuration before deploying it to ensure it meets the protocol specI want to catch schema errors early in development rather than at runtime when clients try to connectI need to compile multiple tool definitions and resources into a single deployable bundle artifact

Best for

MCP server developers building tool bundles for Claude and other LLM clients

teams standardizing MCP bundle packaging across multiple projects

developers integrating MCP into CI/CD pipelines who need automated validation

Requires

Node.js 16+

Valid MCP bundle configuration file (JSON or YAML format)

@anthropic-ai/mcpb package installed

Limitations

Validation is schema-only — does not execute tool functions to verify runtime behavior

Does not validate cross-references between tools and resources at compile time

Limited to MCP specification version constraints — may require updates when protocol evolves

What makes it unique

Anthropic-native MCP bundle tooling that enforces the official Model Context Protocol specification schema directly, with tight integration to Anthropic's MCP ecosystem and Claude client requirements

vs alternatives

Purpose-built for MCP bundles by the protocol creators, whereas generic JSON schema validators lack MCP-specific constraints and context awareness

tool definition and resource bundling with dependency resolution

Medium confidence

Packages multiple tool definitions, resources, and their dependencies into a single MCP bundle with automatic dependency graph resolution. Handles tool metadata (name, description, input schema), resource definitions (URIs, MIME types), and inter-tool dependencies, organizing them into a flat or hierarchical bundle structure that clients can discover and invoke.

Solves for

I want to bundle 10+ related tools (e.g., file operations, database queries) into a single MCP serverI need to ensure tools that depend on each other are packaged together with correct initialization orderI want to expose both tools and static resources (templates, configs) through a single MCP endpoint

Best for

developers building multi-tool MCP servers for Claude and other LLM clients

teams creating domain-specific tool suites (e.g., DevOps tools, data analysis tools)

organizations standardizing tool distribution across multiple LLM applications

Requires

Node.js 16+

Tool definitions with JSON schema input specifications

Resource files accessible via filesystem or HTTP

Limitations

Dependency resolution is static — does not support dynamic or conditional tool loading at runtime

No built-in versioning system for tools within a bundle — all tools share bundle version

Resource bundling is file-based — does not support streaming or large binary resources efficiently

What makes it unique

Provides declarative tool bundling with automatic dependency resolution specifically designed for MCP's tool discovery and invocation model, handling both stateless tools and stateful resources in a single package

vs alternatives

More specialized than generic package managers — understands MCP tool schemas and resource semantics, enabling smarter bundling decisions than npm or pip alone

mcp bundle type generation from typescript/javascript definitions

Medium confidence

Generates MCP-compliant bundle type definitions and JSON schemas from TypeScript interfaces or JavaScript JSDoc comments. Uses AST parsing to extract function signatures, parameter types, and return types, then automatically generates the input/output JSON schemas required by the MCP specification, reducing manual schema authoring.

Solves for

I have TypeScript tool functions and want to auto-generate their MCP input schemas without writing JSON by handI want to keep my tool definitions and their MCP schemas in sync as I refactor function signaturesI need to generate MCP bundle types for a large codebase with 50+ tools efficiently

Best for

TypeScript-first teams building MCP servers who want single-source-of-truth for tool definitions

developers migrating existing Node.js tool libraries to MCP without rewriting schemas

teams using code generation in their build pipeline who want MCP artifacts generated automatically

Requires

Node.js 16+

TypeScript 4.5+ or JavaScript with JSDoc type annotations

Source files with exported functions or class methods

Limitations

Requires TypeScript or JSDoc annotations — does not infer schemas from untyped JavaScript

Complex types (unions, generics, recursive types) may not translate perfectly to JSON schema

Does not generate descriptions or examples — requires manual JSDoc @description and @example tags

What makes it unique

Bidirectional type generation that keeps TypeScript source and MCP schemas synchronized through AST analysis, enabling developers to define tools once in code and derive MCP schemas automatically

vs alternatives

Eliminates manual JSON schema authoring for MCP tools, whereas competitors require hand-written schemas or only support runtime introspection without compile-time guarantees

bundle metadata and manifest generation

Medium confidence

Generates comprehensive bundle manifests that describe all tools, resources, capabilities, and metadata in a machine-readable format. Creates manifest files that include tool descriptions, input/output schemas, resource URIs, version information, and capability declarations, enabling clients to discover and understand bundle contents without executing code.

Solves for

I want to publish a bundle manifest so Claude and other clients can discover what tools are availableI need to document my bundle's capabilities, versions, and dependencies in a standard formatI want to generate a human-readable bundle documentation from the manifest automatically

Best for

MCP server developers publishing bundles to registries or marketplaces

teams maintaining multiple MCP bundles who need standardized documentation

developers building MCP client discovery systems that need to parse bundle metadata

Requires

Node.js 16+

Compiled MCP bundle artifact

@anthropic-ai/mcpb package

Limitations

Manifests are static snapshots — do not reflect runtime state or dynamic tool registration

No built-in versioning or changelog tracking — requires external version control

Limited to JSON/YAML formats — does not generate HTML or Markdown documentation automatically

What makes it unique

Generates MCP-compliant manifests that encode full tool semantics (schemas, descriptions, capabilities) in a format optimized for client discovery and validation, not just package metadata

vs alternatives

Purpose-built for MCP discovery semantics, whereas generic package manifests (package.json, setup.py) lack tool-level schema and capability information

bundle distribution and deployment packaging

Medium confidence

Packages validated and compiled MCP bundles into distributable artifacts (tarballs, Docker images, or standalone executables) with embedded runtime configuration. Handles bundle serialization, dependency vendoring, and environment variable injection, producing artifacts ready for deployment to MCP clients or cloud platforms.

Solves for

I want to package my MCP bundle as a Docker image for deployment to a cloud platformI need to create a standalone tarball that includes all dependencies and can be extracted on any machineI want to inject environment variables (API keys, config) into the bundle at deployment time

Best for

teams deploying MCP servers to production environments (cloud, on-prem, edge)

developers distributing MCP bundles to end users who need self-contained artifacts

organizations building MCP bundle registries or marketplaces

Requires

Node.js 16+

Compiled MCP bundle artifact

Docker (for Docker image packaging)

Limitations

Docker packaging requires Docker to be installed — not suitable for lightweight edge deployments

Standalone executables are platform-specific — requires separate builds for Windows, macOS, Linux

No built-in secret management — environment variables must be injected externally (e.g., via CI/CD)

What makes it unique

Produces MCP-aware deployment artifacts that preserve bundle semantics and manifest information through packaging, enabling clients to validate and discover bundles post-deployment

vs alternatives

Specialized for MCP bundle distribution with manifest preservation, whereas generic packaging tools (npm pack, Docker) lose MCP-specific metadata during packaging

bundle testing and validation framework

Medium confidence

Provides testing utilities to validate bundle behavior, tool invocation, and resource access before deployment. Includes mock MCP client implementations, tool execution simulators, and assertion helpers for verifying tool schemas, input validation, and output formats match MCP specifications.

Solves for

I want to write unit tests for my MCP tools to ensure they work correctly before deployingI need to validate that my tool schemas match the actual function signatures and behaviorI want to test error handling and edge cases in my tools without connecting to a real MCP client

Best for

MCP server developers building production-grade tool bundles with test coverage

teams implementing CI/CD pipelines for MCP bundles who need automated testing

developers debugging tool behavior and schema mismatches during development

Requires

Node.js 16+

Testing framework (Jest, Mocha, Vitest, or similar)

MCP bundle artifact

Limitations

Testing is limited to schema and invocation validation — does not test integration with external services

Mock client may not replicate all MCP client behaviors (e.g., streaming, cancellation)

No built-in performance testing or load testing utilities

What makes it unique

Provides MCP-specific test utilities that validate tool schemas against actual implementations and simulate MCP client behavior, going beyond generic unit testing to verify protocol compliance

vs alternatives

More specialized than generic testing frameworks — understands MCP tool semantics and can validate schema-to-implementation alignment automatically

bundle versioning and compatibility management

Medium confidence

Manages semantic versioning for MCP bundles and tracks compatibility with MCP protocol versions and client versions. Enables version constraints in bundle definitions, validates backward compatibility, and generates migration guides when breaking changes are introduced.

Solves for

I want to release a new version of my MCP bundle and ensure it's backward compatible with existing clientsI need to specify which MCP protocol versions my bundle supportsI want to deprecate old tools in my bundle and guide users to new versions

Best for

teams maintaining long-lived MCP bundles with multiple versions in production

developers publishing bundles to registries who need version management

organizations supporting multiple MCP client versions simultaneously

Requires

Node.js 16+

MCP bundle with version metadata

@anthropic-ai/mcpb package

Limitations

Compatibility checking is schema-based — does not detect behavioral changes or performance regressions

No automatic migration code generation — requires manual migration guides

Limited to semantic versioning — does not support other versioning schemes

What makes it unique

Tracks MCP protocol version compatibility alongside semantic versioning, enabling bundles to declare which MCP versions they support and detecting protocol-level breaking changes

vs alternatives

Understands MCP protocol evolution, whereas generic version managers (npm, pip) only track package versions without protocol-level compatibility awareness

interactive bundle configuration and scaffolding

Medium confidence

Provides CLI wizards and scaffolding templates to generate new MCP bundle projects with boilerplate code, configuration files, and example tools. Guides developers through bundle setup with interactive prompts for bundle name, tools, resources, and deployment targets, generating a ready-to-use project structure.

Solves for

I'm new to MCP and want to create my first bundle without understanding all the configuration detailsI want to quickly scaffold a new bundle project with example tools and testsI need to generate boilerplate code for a bundle with specific tools and resources

Best for

developers new to MCP who want to get started quickly

teams standardizing MCP bundle structure across projects

rapid prototyping of MCP bundles for proof-of-concept work

Requires

Node.js 16+

@anthropic-ai/mcpb package with CLI

Terminal or shell environment

Limitations

Scaffolding generates boilerplate that may require customization for complex use cases

Interactive prompts assume common patterns — advanced configurations require manual editing

Generated code may not follow all best practices — requires developer review

What makes it unique

MCP-aware scaffolding that generates not just boilerplate code but also MCP-compliant bundle configurations, schemas, and example tools tailored to the MCP protocol

vs alternatives

More specialized than generic project generators (Yeoman, Create React App) — understands MCP bundle structure and generates protocol-compliant examples

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Related Artifactssharing capabilities

Artifacts that share capabilities with @anthropic-ai/mcpb, ranked by overlap. Discovered automatically through the match graph.

MCP Server37

xmcp

The TypeScript MCP framework

typescript-first type system for mcp tools, prompts, and resourceswebpack-based compilation system with incremental builds

2 shared capabilities

MCP Server22

@gleanwork/mcp-server-utils

Shared utilities for MCP server packages

type-safe mcp tool definition buildermcp tool/resource schema validation and registration

2 shared capabilities

MCP Server34

mcpb

Desktop Extensions: One-click local MCP server installation in desktop apps

node.js programmatic api for bundle operations

1 shared capability

MCP Server22

@mseep/mcp-typescript-server-starter

ModelContextProtocol typescript server starter

mcp protocol type definitions and schema validation

1 shared capability

MCP Server42

mcp-use

The fullstack MCP framework to develop MCP Apps for ChatGPT / Claude & MCP Servers for AI Agents.

build cli for mcp server compilation and bundling

1 shared capability

MCP Server30

@mcp-use/cli

The mcp-use CLI is a tool for building and deploying MCP servers with support for ChatGPT Apps, Code Mode, OAuth, Notifications, Sampling, Observability and more.

mcp server build and bundling with esbuild

1 shared capability

Best For

✓MCP server developers building tool bundles for Claude and other LLM clients
✓teams standardizing MCP bundle packaging across multiple projects
✓developers integrating MCP into CI/CD pipelines who need automated validation
✓developers building multi-tool MCP servers for Claude and other LLM clients
✓teams creating domain-specific tool suites (e.g., DevOps tools, data analysis tools)
✓organizations standardizing tool distribution across multiple LLM applications
✓TypeScript-first teams building MCP servers who want single-source-of-truth for tool definitions
✓developers migrating existing Node.js tool libraries to MCP without rewriting schemas

Known Limitations

⚠Validation is schema-only — does not execute tool functions to verify runtime behavior
⚠Does not validate cross-references between tools and resources at compile time
⚠Limited to MCP specification version constraints — may require updates when protocol evolves
⚠Dependency resolution is static — does not support dynamic or conditional tool loading at runtime
⚠No built-in versioning system for tools within a bundle — all tools share bundle version
⚠Resource bundling is file-based — does not support streaming or large binary resources efficiently

Requirements

Node.js 16+Valid MCP bundle configuration file (JSON or YAML format)@anthropic-ai/mcpb package installedTool definitions with JSON schema input specificationsResource files accessible via filesystem or HTTP@anthropic-ai/mcpb packageTypeScript 4.5+ or JavaScript with JSDoc type annotationsSource files with exported functions or class methods

Input / Output

Accepts: JSON configuration, YAML configuration, JavaScript/TypeScript bundle objects, tool definition objects (name, description, inputSchema), resource definitions (URI, MIME type, content), dependency declarations (tool-to-tool references), TypeScript source files (.ts), JavaScript files with JSDoc comments (.js), TypeScript interface definitions, MCP bundle artifact, tool definitions, resource definitions, metadata configuration, compiled MCP bundle, dependency list, environment configuration, runtime configuration, test cases (tool invocations with inputs), expected outputs, bundle version string (semver), MCP protocol version constraints, previous bundle versions for comparison, interactive CLI prompts, configuration options (bundle name, tools, resources)

Produces: validated bundle artifact, validation error reports, compiled bundle metadata, bundled MCP artifact with tool registry, resource manifest, dependency graph metadata, JSON schema files for tool inputs, JSON schema files for tool outputs, MCP bundle type definitions, TypeScript type declaration files, JSON manifest file, YAML manifest file, manifest metadata object, tarball archive (.tar.gz), Docker image (OCI format), standalone executable, deployment manifest (Docker Compose, Kubernetes), test results (pass/fail), validation reports, coverage metrics, compatibility report, breaking change detection, migration guide template, project directory structure, configuration files (package.json, bundle.json), example tool implementations, test files, README documentation

UnfragileRank

Adoption59%(30% weight)

Quality17%(25% weight)

Ecosystem30%(25% weight)

Match Graph10%(15% weight)

Freshness75%(5% weight)

UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.

Type: MCP Server

8 capabilities

Visit @anthropic-ai/mcpb→

Package Details

npm

Registry

2.1.2

Version

44,322

Weekly Downloads

About

Tools for building MCP Bundles

Alternatives to @anthropic-ai/mcpb

IntelliCode50Extension

AI-assisted development

Compare →

GitHub Copilot Chat53Extension

AI chat features powered by Copilot

Compare →

GitHub Copilot52Extension

Your AI pair programmer

Compare →

Claude Code for VS Code52Extension

Claude Code for VS Code: Harness the power of Claude Code without leaving your IDE

Compare →

Are you the builder of @anthropic-ai/mcpb?

Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.

Claim this artifact →Verification via email

Get the weekly brief

New tools, rising stars, and what's actually worth your time. No spam.

Data Sources

mcp registry

Looking for something else?

Search →

Capabilities8 decomposed

mcp bundle schema validation and compilation

Medium confidence

Solves for

Best for

MCP server developers building tool bundles for Claude and other LLM clients

teams standardizing MCP bundle packaging across multiple projects

developers integrating MCP into CI/CD pipelines who need automated validation

Requires

Node.js 16+

Valid MCP bundle configuration file (JSON or YAML format)

@anthropic-ai/mcpb package installed

Limitations

Validation is schema-only — does not execute tool functions to verify runtime behavior

Does not validate cross-references between tools and resources at compile time

Limited to MCP specification version constraints — may require updates when protocol evolves

What makes it unique

Anthropic-native MCP bundle tooling that enforces the official Model Context Protocol specification schema directly, with tight integration to Anthropic's MCP ecosystem and Claude client requirements

vs alternatives

Purpose-built for MCP bundles by the protocol creators, whereas generic JSON schema validators lack MCP-specific constraints and context awareness

tool definition and resource bundling with dependency resolution

Medium confidence

Solves for

Best for

developers building multi-tool MCP servers for Claude and other LLM clients

teams creating domain-specific tool suites (e.g., DevOps tools, data analysis tools)

organizations standardizing tool distribution across multiple LLM applications

Requires

Node.js 16+

Tool definitions with JSON schema input specifications

Resource files accessible via filesystem or HTTP

Limitations

Dependency resolution is static — does not support dynamic or conditional tool loading at runtime

No built-in versioning system for tools within a bundle — all tools share bundle version

Resource bundling is file-based — does not support streaming or large binary resources efficiently

What makes it unique

vs alternatives

More specialized than generic package managers — understands MCP tool schemas and resource semantics, enabling smarter bundling decisions than npm or pip alone

mcp bundle type generation from typescript/javascript definitions

Medium confidence

Solves for

Best for

TypeScript-first teams building MCP servers who want single-source-of-truth for tool definitions

developers migrating existing Node.js tool libraries to MCP without rewriting schemas

teams using code generation in their build pipeline who want MCP artifacts generated automatically

Requires

Node.js 16+

TypeScript 4.5+ or JavaScript with JSDoc type annotations

Source files with exported functions or class methods

Limitations

Requires TypeScript or JSDoc annotations — does not infer schemas from untyped JavaScript

Complex types (unions, generics, recursive types) may not translate perfectly to JSON schema

Does not generate descriptions or examples — requires manual JSDoc @description and @example tags

What makes it unique

Bidirectional type generation that keeps TypeScript source and MCP schemas synchronized through AST analysis, enabling developers to define tools once in code and derive MCP schemas automatically

vs alternatives

Eliminates manual JSON schema authoring for MCP tools, whereas competitors require hand-written schemas or only support runtime introspection without compile-time guarantees

bundle metadata and manifest generation

Medium confidence

Solves for

Best for

MCP server developers publishing bundles to registries or marketplaces

teams maintaining multiple MCP bundles who need standardized documentation

developers building MCP client discovery systems that need to parse bundle metadata

Requires

Node.js 16+

Compiled MCP bundle artifact

@anthropic-ai/mcpb package

Limitations

Manifests are static snapshots — do not reflect runtime state or dynamic tool registration

No built-in versioning or changelog tracking — requires external version control

Limited to JSON/YAML formats — does not generate HTML or Markdown documentation automatically

What makes it unique

Generates MCP-compliant manifests that encode full tool semantics (schemas, descriptions, capabilities) in a format optimized for client discovery and validation, not just package metadata

vs alternatives

Purpose-built for MCP discovery semantics, whereas generic package manifests (package.json, setup.py) lack tool-level schema and capability information

bundle distribution and deployment packaging

Medium confidence

Solves for

Best for

teams deploying MCP servers to production environments (cloud, on-prem, edge)

developers distributing MCP bundles to end users who need self-contained artifacts

organizations building MCP bundle registries or marketplaces

Requires

Node.js 16+

Compiled MCP bundle artifact

Docker (for Docker image packaging)

Limitations

Docker packaging requires Docker to be installed — not suitable for lightweight edge deployments

Standalone executables are platform-specific — requires separate builds for Windows, macOS, Linux

No built-in secret management — environment variables must be injected externally (e.g., via CI/CD)

What makes it unique

Produces MCP-aware deployment artifacts that preserve bundle semantics and manifest information through packaging, enabling clients to validate and discover bundles post-deployment

vs alternatives

Specialized for MCP bundle distribution with manifest preservation, whereas generic packaging tools (npm pack, Docker) lose MCP-specific metadata during packaging

bundle testing and validation framework

Medium confidence

Solves for

Best for

MCP server developers building production-grade tool bundles with test coverage

teams implementing CI/CD pipelines for MCP bundles who need automated testing

developers debugging tool behavior and schema mismatches during development

Requires

Node.js 16+

Testing framework (Jest, Mocha, Vitest, or similar)

MCP bundle artifact

Limitations

Testing is limited to schema and invocation validation — does not test integration with external services

Mock client may not replicate all MCP client behaviors (e.g., streaming, cancellation)

No built-in performance testing or load testing utilities

What makes it unique

Provides MCP-specific test utilities that validate tool schemas against actual implementations and simulate MCP client behavior, going beyond generic unit testing to verify protocol compliance

vs alternatives

More specialized than generic testing frameworks — understands MCP tool semantics and can validate schema-to-implementation alignment automatically

bundle versioning and compatibility management

Medium confidence

Solves for

Best for

teams maintaining long-lived MCP bundles with multiple versions in production

developers publishing bundles to registries who need version management

organizations supporting multiple MCP client versions simultaneously

Requires

Node.js 16+

MCP bundle with version metadata

@anthropic-ai/mcpb package

Limitations

Compatibility checking is schema-based — does not detect behavioral changes or performance regressions

No automatic migration code generation — requires manual migration guides

Limited to semantic versioning — does not support other versioning schemes

What makes it unique

Tracks MCP protocol version compatibility alongside semantic versioning, enabling bundles to declare which MCP versions they support and detecting protocol-level breaking changes

vs alternatives

Understands MCP protocol evolution, whereas generic version managers (npm, pip) only track package versions without protocol-level compatibility awareness

interactive bundle configuration and scaffolding

Medium confidence

Solves for

Best for

developers new to MCP who want to get started quickly

teams standardizing MCP bundle structure across projects

rapid prototyping of MCP bundles for proof-of-concept work

Requires

Node.js 16+

@anthropic-ai/mcpb package with CLI

Terminal or shell environment

Limitations

Scaffolding generates boilerplate that may require customization for complex use cases

Interactive prompts assume common patterns — advanced configurations require manual editing

Generated code may not follow all best practices — requires developer review

What makes it unique

MCP-aware scaffolding that generates not just boilerplate code but also MCP-compliant bundle configurations, schemas, and example tools tailored to the MCP protocol

vs alternatives

More specialized than generic project generators (Yeoman, Create React App) — understands MCP bundle structure and generates protocol-compliant examples

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Alternatives to @anthropic-ai/mcpb

IntelliCode50Extension

AI-assisted development

Compare →

GitHub Copilot Chat53Extension

AI chat features powered by Copilot

Compare →

GitHub Copilot52Extension

Your AI pair programmer

Compare →

Claude Code for VS Code52Extension

Claude Code for VS Code: Harness the power of Claude Code without leaving your IDE

Compare →

@anthropic-ai/mcpb

Capabilities8 decomposed

mcp bundle schema validation and compilation

tool definition and resource bundling with dependency resolution

mcp bundle type generation from typescript/javascript definitions

bundle metadata and manifest generation

bundle distribution and deployment packaging

bundle testing and validation framework

bundle versioning and compatibility management

interactive bundle configuration and scaffolding

Related Artifactssharing capabilities

xmcp

@gleanwork/mcp-server-utils

mcpb

@mseep/mcp-typescript-server-starter

mcp-use

@mcp-use/cli

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

Package Details

About

Categories

Alternatives to @anthropic-ai/mcpb

Are you the builder of @anthropic-ai/mcpb?

Get the weekly brief

Data Sources

@anthropic-ai/mcpb

Capabilities8 decomposed

mcp bundle schema validation and compilation

tool definition and resource bundling with dependency resolution

mcp bundle type generation from typescript/javascript definitions

bundle metadata and manifest generation

bundle distribution and deployment packaging

bundle testing and validation framework

bundle versioning and compatibility management

interactive bundle configuration and scaffolding

Related Artifactssharing capabilities

xmcp

@gleanwork/mcp-server-utils

mcpb

@mseep/mcp-typescript-server-starter

mcp-use

@mcp-use/cli

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

Package Details

About

Categories

Alternatives to @anthropic-ai/mcpb

Are you the builder of @anthropic-ai/mcpb?

Get the weekly brief

Data Sources