Content Tools

bizzabo.com

An MCP server that lets you search, browse, fetch, and inventory Bizzabo marketing content across published content types.

1 endpoint7 known toolsFirst detected October 21, 2026Last detected October 21, 2026

ENDPOINT 1

https://www.bizzabo.com/wp-json/bizzabo-mcp/v1/mcp

No auth detected

MCP server metadata

Name: bizzabo-content
Version: 1.0

Capabilities

tools

Server instructions

Read-only access to Bizzabo's published marketing content at https://www.bizzabo.com — blog posts, podcast episodes, case studies, and the resource library. Typical flow: search_content to find relevant pieces, then get_content for the full markdown of one. Use content_inventory to audit how much has been published on a topic before writing something new, and get_company_overview for grounded product and positioning facts. Everything here is public and published. Nothing in this server can write to the site.

Known tools 7

search_content

Search Bizzabo marketing content across all content types at once and return ranked results with a relevant snippet from each.

Inferred read-only

get_content

Fetch a single Bizzabo page and return its body as clean markdown with an outline.

Inferred read-only

list_content

Browse a content type newest-first without fetching bodies.

Inferred read-only

content_inventory

Show how much Bizzabo has published on a topic, broken down by content type, with the newest and oldest pieces and a staleness read.

Inferred read-only

list_content_types

List the Bizzabo content types this server exposes, with how many items each holds and whether full body text is available.

Inferred read-only

list_categories

List category ids and names, for use with the category_id filter on list_content.

Inferred read-only

get_company_overview

Get Bizzabo's own summary of what it does, its products, key pages and solutions, from the site llms.txt.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.bizzabo-content]
url = "https://www.bizzabo.com/wp-json/bizzabo-mcp/v1/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "bizzabo-content": {
      "type": "http",
      "url": "https://www.bizzabo.com/wp-json/bizzabo-mcp/v1/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: bizzabo-content
Remote MCP URL: https://www.bizzabo.com/wp-json/bizzabo-mcp/v1/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "bizzabo-content": {
      "url": "https://www.bizzabo.com/wp-json/bizzabo-mcp/v1/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "bizzabo-content": {
      "type": "http",
      "url": "https://www.bizzabo.com/wp-json/bizzabo-mcp/v1/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "bizzabo-content",
  "transport": "streamable-http",
  "url": "https://www.bizzabo.com/wp-json/bizzabo-mcp/v1/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.