MCP integration

Monetization for MCP tools.

Give agents a clean way to request sponsored suggestions when a user is choosing a product, service, API, or workflow.

Get API key Read MCP docs⏎

Offer call: Bounded; timeout and no-fill fallback
Disclosure: Required; every sponsored response
Auction: Quality-weighted; publisher-weighted ranking
Integration: 1 endpoint; REST, SDK, MCP, React

One server. One clear instruction.

Add Genesis to the client, then tell the agent to call it only at real decision moments.

MCP config

{
  "mcpServers": {
    "genesis": {
      "url": "https://mcp.thegenesis.com",
      "headers": {
        "Authorization": "Bearer gn_test_..."
      }
    }
  }
}

System instruction

Call `genesis.get_offers` only when the user is evaluating a product, vendor, service, API, tool, or workflow. Label every sponsored suggestion.

Tool schema

`genesis.get_offers` accepts placement, context, user, and controls. `genesis.record_signal` accepts privacy-safe feedback and hashed identifiers.

Fallback and trust

If Genesis returns no fill or cannot be reached, the agent simply continues without a sponsored suggestion.

Docs quickstart

Rewards boundary

MCP monetization is not Genesis Rewards.

MCP servers use Genesis tools for product-controlled sponsored suggestions. Genesis Rewards is the separate opt-in client for developer wait states.

MCP traffic is not automatically payable rewards traffic. Rewards require opt-in, privacy controls, duplicate-session controls, and review.

Genesis Rewards

Clear routing

Product placements stay in MCP. Personal coding wait-state placements stay in Genesis Rewards.