MCP Connector

Unify 500+ App Integrations for AI Assistants

Manage and execute tools across 500+ connected providers from one authenticated MCP Hub endpoint - no per-server configuration.

Works with githubslacknotiongoogle drivesalesforce

91
Spark score
out of 100
Updated 3 months ago
Version uk-public-services-h
Models
universal

Add to Favorites

Why it matters

Empower AI assistants to seamlessly interact with over 500 services, including GitHub, Slack, and Salesforce, through a single, unified access point.

Outcomes

What it gets done

01

Access and manage tools across diverse applications like Notion, Google Drive, and Stripe.

02

Automate tasks by executing provider-specific functions via a central hub.

03

Discover and list available tools and providers for enhanced AI capabilities.

04

Manage credentials and bundles for streamlined integration.

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/vb-mcp-bundles-hub | bash

Capabilities

Tools your agent gets

mcpbundles_hub_list_bundles

Get a list of all your bundles

mcpbundles_hub_get_bundle

Get details of a specific bundle

mcpbundles_hub_create_bundle

Create a new bundle

mcpbundles_hub_update_bundle

Update a bundle configuration

mcpbundles_hub_delete_bundle

Delete a bundle

mcpbundles_hub_list_credentials

Get a list of your provider credentials

mcpbundles_hub_add_credential

Add new provider credentials

mcpbundles_hub_update_credential

Update existing credentials

+6 tools

Overview

MCP Bundles Hub MCP Server

MCP Bundles Hub is the account-management MCP server for MCPBundles, letting you create tool bundles, connect provider credentials, and discover tools across 500+ integrations from one authenticated endpoint. Executing bundle tools happens through a separate per-bundle MCP URL once configured via the Hub. Use it to centrally manage bundles and provider credentials for an AI assistant connected to many SaaS tools. Not applicable if you need direct control of a single provider outside the MCPBundles account model.

What it does

MCP Bundles Hub is the account-management MCP server for MCPBundles, a service that groups tools from 500+ providers (GitHub, Slack, Notion, Google Drive, Salesforce, Stripe, and more) into user-defined "bundles." Instead of configuring an individual MCP server per provider, the Hub server gives an authenticated single endpoint for creating bundles, connecting provider credentials, discovering tools, and executing them.

When to use - and when NOT to

Use it when you want to give an AI assistant (Claude Desktop, Cursor, or another MCP-compatible client) access to many third-party tools without hand-configuring a separate MCP server for each provider, and you're comfortable authenticating those providers through an MCPBundles account (OAuth or API key). Do not use it if you need direct, self-hosted control over a single provider's credentials without routing through a third-party hub, or if your provider isn't among the 500+ MCPBundles integrations.

Capabilities

The Hub server exposes tools prefixed mcpbundles_hub_, grouped as:

  • Bundle operations: mcpbundles_hub_list_bundles, mcpbundles_hub_get_bundle, mcpbundles_hub_create_bundle, mcpbundles_hub_update_bundle, mcpbundles_hub_delete_bundle.
  • Credential management: mcpbundles_hub_list_credentials, mcpbundles_hub_add_credential, mcpbundles_hub_update_credential, mcpbundles_hub_remove_credential.
  • Provider discovery: mcpbundles_hub_search_providers, mcpbundles_hub_get_provider_info, mcpbundles_hub_list_provider_tools.
  • Account management: mcpbundles_hub_get_account_info, mcpbundles_hub_get_usage_stats.

Once a bundle is created and configured through the Hub, each bundle gets its own dedicated MCP server URL (https://mcp.mcpbundles.com/bundle/<name>) for actually executing its tools - the Hub itself is for managing bundles, providers, and credentials, not for running bundle tools directly.

How to install

The typical workflow is to use the Hub MCP to create a bundle, add provider credentials to it, and enable specific tools, then switch to that bundle's own dedicated MCP server URL to actually call those tools. In Cursor, add the server via Settings -> Features -> MCP -> Add Server, using the hub.mcpb release URL, then authenticate with OAuth. Alternatively, download and double-click the hub.mcpb file for Claude Desktop to auto-install, or configure manually:

{
  "mcpServers": {
    "mcpbundles-hub": {
      "command": "npx",
      "args": ["-y", "mcp-remote@latest", "https://mcp.mcpbundles.com/hub/", "--header", "Authorization:Bearer ${ACCESS_TOKEN}"],
      "env": { "ACCESS_TOKEN": "your_access_token_here" }
    }
  }
}

An MCPBundles account (free) and an access token from the dashboard are required; OAuth is recommended for Cursor (browser-based, automatic token refresh, revocable from the dashboard) while API keys suit Claude Desktop (manual bearer token, no expiration until revoked). Credentials are encrypted in transit, never exposed to the AI model itself, stored securely in the user's MCPBundles account, and revocable at any time.

Who it's for

AI power users and teams who connect many SaaS tools (GitHub, Slack, Notion, Salesforce, Stripe, etc.) to an AI assistant and want centralized bundle and credential management instead of maintaining dozens of separate MCP server configs. The Hub server itself is MIT-licensed.

Source README

MCP Bundles Hub MCP Server

MCP Bundles Logo

MCP Compatible 500+ Providers Download .mcpb Documentation

Execute tools from your enabled bundles directly from Claude, Cursor, and other MCP-compatible AI assistants using the Model Context Protocol.

Download

Download the MCPBundles Hub .mcpb file directly:

Download hub.mcpb

This .mcpb package contains a pre-configured MCP server proxy that connects to the MCPBundles Hub endpoint. Once installed, your AI assistant can discover and execute tools from all your enabled bundles.

Note: This repository hosts .mcpb files for hundreds of bundles. The link above is specifically for the Hub server. See all releases to download individual bundle packages.

What is MCP Bundles?

MCP Bundles is the simplest way to connect AI assistants to real-world tools. Instead of configuring hundreds of individual MCP servers, you:

  1. Create bundles of tools you need (e.g., "Marketing Tools", "Developer Workflow")
  2. Connect providers with secure OAuth or API keys once
  3. Use one MCP URL per bundle - all your tools instantly available

With 500+ provider integrations including GitHub, Slack, Notion, Google Drive, Salesforce, Stripe, and more, MCP Bundles eliminates the complexity of MCP server management while giving your AI assistant powerful, authenticated access to the services you use every day.

What is the Hub MCP Server?

The MCP Bundles Hub MCP Server provides direct access to tools from all your enabled bundles through a single MCP endpoint. Instead of configuring each bundle separately, you can:

  • Execute Tools: Run any tool from your enabled bundles through one interface
  • List Available Tools: Discover what tools are available across all your bundles
  • Search Tools: Find tools by name, provider, or capability
  • Check Readiness: Verify bundle configuration and credential status
  • Get Tool Details: View parameters, descriptions, and usage for specific tools

This server is authenticated and tied to your MCPBundles account. It aggregates all your bundle tools into one convenient MCP server endpoint.

Features

  • OAuth & API Key Authentication: Secure access via OAuth login or Bearer token
  • Unified Access: Execute tools from multiple bundles through one endpoint
  • Tool Discovery: Search and list all tools you have access to
  • Bundle-Aware Execution: Tools automatically use the correct credentials for each bundle
  • Readiness Checks: Verify configuration status before executing tools

Documentation

For comprehensive setup guides and usage instructions:

Quick Start

Prerequisites

  • An MCPBundles account (free at mcpbundles.com)
  • MCP-compatible client (Claude Desktop, Cursor, etc.)
  • Authentication method:
    • OAuth (recommended): One-click authentication in Cursor
    • API Key: Get from your dashboard for Claude Desktop

Setup Methods

Method 1: One-Click Install in Cursor (Recommended)

Cursor supports direct MCP server installation via URL:

  1. Open Cursor Settings → Features → MCP
  2. Click "Add Server"
  3. Paste this URL: https://github.com/thinkchainai/mcpbundles/releases/download/hub-v1.0.0%2Bbuild.8da55d55/hub.mcpb
  4. Authenticate with OAuth when prompted
Method 2: Download & Install .mcpb File
  1. Download hub.mcpb
  2. Double-click the .mcpb file (Claude Desktop will auto-install)
  3. Restart Claude Desktop
  4. Configure authentication (see Manual Configuration below for API key setup)
Method 3: Manual Configuration
Cursor Setup

Add to your Cursor MCP settings:

{
  "mcpServers": {
    "mcpbundles-hub": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://mcp.mcpbundles.com/hub/",
        "--header",
        "Authorization:Bearer ${ACCESS_TOKEN}"
      ],
      "env": {
        "ACCESS_TOKEN": "your_access_token_here"
      }
    }
  }
}
Claude Desktop Setup

Edit your Claude Desktop config file (Claude menu → Settings → Developer → Edit Config):

{
  "mcpServers": {
    "mcpbundles-hub": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://mcp.mcpbundles.com/hub/",
        "--header",
        "Authorization:Bearer ${ACCESS_TOKEN}"
      ],
      "env": {
        "ACCESS_TOKEN": "your_access_token_here"
      }
    }
  }
}

Note: Replace your_access_token_here with your actual MCPBundles access token from your dashboard.

Example Usage

Once configured, you can ask your AI assistant:

Execute Tools

  • "Use the GitHub create_issue tool from my dev-tools bundle"
  • "Execute the slack_send_message tool to post an update"
  • "Run the notion_create_page tool with title 'Meeting Notes'"

Discover Tools

  • "What tools are available in my marketing bundle?"
  • "List all GitHub tools I have access to"
  • "Search for tools related to 'email'"

Check Status

  • "Check if my dev-tools bundle is ready to use"
  • "Show me the parameters for the github_create_issue tool"
  • "What bundles do I have enabled?"

Available Tools

The Hub MCP server provides tools with the mcpbundles_hub_ prefix:

Bundle Operations

  • mcpbundles_hub_list_bundles - List all your bundles
  • mcpbundles_hub_get_bundle - Get details about a specific bundle
  • mcpbundles_hub_create_bundle - Create a new bundle
  • mcpbundles_hub_update_bundle - Update bundle configuration
  • mcpbundles_hub_delete_bundle - Delete a bundle

Credential Management

  • mcpbundles_hub_list_credentials - List your provider credentials
  • mcpbundles_hub_add_credential - Add a new provider credential
  • mcpbundles_hub_update_credential - Update an existing credential
  • mcpbundles_hub_remove_credential - Remove a credential

Provider Discovery

  • mcpbundles_hub_search_providers - Search available providers
  • mcpbundles_hub_get_provider_info - Get detailed provider information
  • mcpbundles_hub_list_provider_tools - List tools for a specific provider

Account Management

  • mcpbundles_hub_get_account_info - View your account details
  • mcpbundles_hub_get_usage_stats - Check API usage statistics

Security

The Hub MCP server supports two authentication methods:

  1. OAuth (Recommended): Secure browser-based authentication

    • Automatic token refresh
    • Revocable from your dashboard
    • Works seamlessly in Cursor
  2. API Keys: Manual Bearer token authentication

    • Generate from your dashboard
    • Ideal for Claude Desktop
    • No expiration (until revoked)

Your credentials are:

  • Encrypted in transit (HTTPS/TLS)
  • Never exposed to the AI model
  • Stored securely in your MCPBundles account
  • Revocable at any time from your dashboard

Never share your API keys or include them in public repositories.

How It Works with Your Bundles

The Hub MCP server is for managing your account. Once you create bundles, each bundle gets its own MCP server URL:

https://mcp.mcpbundles.com/bundle/your-bundle-name

Typical Workflow:

  1. Use Hub MCP to create a bundle: "Create a bundle called 'dev-tools'"
  2. Use Hub MCP to add providers: "Add GitHub and Slack credentials"
  3. Use Hub MCP to configure tools: "Enable all GitHub repo tools"
  4. Use the Bundle MCP (/bundle/dev-tools) to actually use the tools: "Create a new GitHub issue"

Troubleshooting

"401 Unauthorized" Error

  • Check that your access token is valid
  • Verify the token in your dashboard at mcpbundles.com/dashboard
  • Make sure you're using the correct environment variable name

Tools Not Appearing

  • Restart your AI client after adding the MCP server
  • Check that "App-Level Tools" is enabled in your dashboard
  • Verify the MCP server URL is correct: https://mcp.mcpbundles.com/hub/

Connection Timeout

  • Ensure you have internet connectivity
  • Check if mcpbundles.com is accessible
  • Try refreshing your access token

Related Resources

Official Repositories

MCP Resources

FAQ

Common questions

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.