BizGigz MCP Servers

What BizGigz MCP Servers MCP server does

The BizGigz MCP Servers MCP server connects AI agents to two distinct areas of the BizGigz platform. The Agent Marketplace server is focused on agent-level operations: identifying an agent, checking its health, and discovering available capabilities. It exposes three tools at https://agents.bizgigz.com/mcp.

The Talent Ecosystem server covers a broader business workflow. Its 53 tools support recruiting, hiring, onboarding, learning, and collaboration through https://bizgigz.com/mcp. Use this endpoint when an agent needs to interact with the broader BizGigz talent platform, rather than only manage or inspect an agent identity.

These endpoints are presented as separate MCP servers, so a client can configure either one independently or both together.

How it works

Both services use the Streamable HTTP MCP transport. An MCP-compatible client sends requests to the relevant HTTPS endpoint, with authentication supplied in the request headers. The required header uses the Bearer scheme and contains the API key issued by BizGigz.

The Agent Marketplace and Talent Ecosystem endpoints serve different tool sets, but they follow the same authentication model. A client configuration can therefore define two entries, each with its own endpoint URL and the same API key when that key has access to both services.

The BizGigz MCP Servers MCP server does not describe a local process, package installation, or standard-input transport in the supplied documentation. Connectivity is configured against the hosted endpoints.

Setup and configuration

First, sign in at agents.bizgigz.com, register an agent, and copy the API key generated for it. Add the desired BizGigz endpoint to an MCP client configuration using the streamable-http type. Set the URL to either the Agent Marketplace endpoint or the Talent Ecosystem endpoint, then include an Authorization header with this structure:

Authorization: Bearer YOUR_API_KEY

Configure both endpoint entries if the agent needs marketplace and talent capabilities. Replace the placeholder with the real key and keep it out of source control and shared configuration files. The supplied material does not specify environment variable names, client-specific setup steps, scopes, or separate credentials for the two endpoints.

Tools and capabilities

The available capabilities are divided by endpoint:

• Agent Marketplace: three tools for agent identity, health checks, and capability discovery.
• Talent Ecosystem: 53 tools covering recruiting, hiring, onboarding, learning, and collaboration.
• Authentication: API-key access through a Bearer token in the Authorization header.
• Transport: Streamable HTTP for both hosted MCP services.

The documentation does not provide individual tool names, argument schemas, response formats, permission details, or examples of specific recruiting or collaboration operations. Consult the linked service or registry documentation before building workflows that depend on a particular tool contract.

Limitations and notes

The two endpoints are not interchangeable: the marketplace server exposes three agent-oriented tools, while the talent server exposes the larger recruiting and workforce workflow surface. Access to either endpoint depends on a valid API key.

The supplied project states that the code and documentation are copyright 2026 BizGigz and all rights reserved; it does not identify an open-source license. The documentation also does not list supported MCP clients, rate limits, availability guarantees, API-key permissions, or a local deployment option. Treat those areas as requiring confirmation from BizGigz before production use.