Carbon

What Carbon MCP server does

The Carbon MCP server connects AI assistants to a company’s carbon.talent hiring account. It covers the workflow from finding potential data professionals to managing roles and applicants. Hiring teams can search the talent catalog using skills, experience, location, or keywords; inspect a profile returned by search; create a role draft; publish a role; and review applicants associated with company roles.

Applicant workflow support includes listing applicants, reading an applicant summary, and moving an applicant between Applied, Screened, Interview, and Offer. The connector does not move applicants to Hired. Profile and applicant-summary responses intentionally omit contact information, CVs, rates, and scores.

How it works

The Carbon MCP server uses a Streamable HTTP endpoint at https://mcp.carbondatasolutions.com/mcp. An MCP host connects to that URL, then the user signs in through OAuth with a carbon.talent company account. Access is limited to company-scoped data, and the connection can be disconnected from Carbon or the host.

Runtime tool definitions are supplied by the live connector through MCP’s tools/list method. The available operations separate read actions from writes. Read tools retrieve account, role, applicant, or talent information. Creating a role draft, publishing a role, and changing an applicant’s stage are write actions that request confirmation before proceeding.

Setup and configuration

Add the Streamable HTTP endpoint to an MCP host that accepts custom server URLs. For Cursor or an Open Plugins-compatible configuration, the connection can be represented as:

{
  "mcpServers": {
    "carbon": {
      "type": "streamable-http",
      "url": "https://mcp.carbondatasolutions.com/mcp"
    }
  }
}

After connecting, authenticate with OAuth to a carbon.talent company account. No environment variables are specified for this setup. The repository also provides server.json and server-card.json with static name and description data for directory indexing, while live tool schemas come from the connector.

Tools and capabilities

The Carbon MCP server exposes these operations:

• whoami: Shows the connected hiring account, including name, email, company, and verification status.
• list_roles: Lists company roles with status, location, and applicant counts.
• get_role: Retrieves a role and its applicants organized by stage.
• create_role_draft: Creates a private company role draft after confirmation.
• post_role: Submits a draft for publication after confirmation.
• list_applicants: Lists applicants for a selected role with stage and application time.
• get_applicant_summary: Returns a restricted summary without contact details, CVs, rates, or scores.
• move_applicant_stage: Advances an applicant to Applied, Screened, Interview, or Offer after confirmation.
• search_talent: Searches the catalog by skills, experience, location, or keywords, returning a first name and last initial.
• get_talent_profile: Retrieves a catalog profile using an ID returned by search.

Limitations and notes

The connector is intended for company hiring workflows and uses company-scoped account access. It does not expose full applicant or talent records: contact details, CVs, rates, and scores are excluded from the relevant responses. Applicant stage movement stops at Offer; Hired is not available through the connector.

A role can be posted without a fee, and Carbon states that the one-time fee is waived for a first hire. Skills tests are listed from approximately $110, or about €95. The README describes the endpoint as live and suitable for hosts that allow custom MCP connectors; it does not establish that Carbon appears in every named assistant’s official directory.