# Clazar MCP connector

The Clazar connector brings your cloud marketplace listings, private offers, contracts, buyers, opportunities and usage metering into Claude, ChatGPT and Cursor, so each person works with them inside their own Clazar access.

Source: https://elaichi.ai/connectors/clazar/

## Facts

| | |
| --- | --- |
| Application | Clazar |
| Category | CRM |
| AI tools | 29 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Clazar is connected

- Which private offers are still waiting on buyer acceptance this week?
- Summarize the open co-sell opportunities for the Acme buyer
- Show usage metering we submitted for the Acme contract in March

## Connect Clazar in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Clazar.
2. Optionally set Share with, then press Connect.
3. Paste a Clazar API key. One person generates a token in Clazar and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Clazar tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Clazar MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Clazar MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

## Clazar MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Connect Clazar to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Only Read is granted by default, which is not enough to call a Clazar tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with Clazar through Elaichi

### Catch an opportunity up after a call

Sales. Tell the agent what changed on a co-sell deal and it updates the Clazar opportunity, so the record matches the conversation before the next partner sync.

### Check where a private offer stands

Alliances. Ask which private offers are still waiting on buyer acceptance and get the answer from Clazar directly, without opening each one by hand.

### Report usage before the metering deadline

Finance. Submit usage metering for a marketplace contract in plain language, and look back at what was already reported so nothing is double counted.

### Activate a contract once the buyer accepts

Revenue operations. When a buyer signs off, activate the Clazar contract and confirm its terms in the same conversation, then note the change on the buyer record.

### Keep buyer contacts current

Customer success. Add a new champion, fix a wrong email or remove someone who left the buyer's team, all against the Clazar contact records for that account.

### Compare listings across cloud marketplaces

Marketplace operations. Pull every Clazar listing side by side and pair it with the analytics datasets available, so you can see which marketplace is pulling its weight.

## Frequently asked questions

### How do I connect Clazar to Claude?

Connect Clazar in Elaichi by pasting in the API key from your Clazar account, then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. There is no OAuth application to register and no client ID or secret to generate. Once Claude signs you in through Elaichi, Clazar is ready to use in your conversations.

### Does Clazar work with ChatGPT and Cursor as well as Claude?

Yes. Clazar connects to Elaichi once, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You do not connect Clazar again for each one.

### What can an AI agent actually do with my Clazar data?

With Clazar connected, an agent can look up buyers, contacts, contracts, listings, private offers and co-sell opportunities, update the ones you point it at, add or remove buyer contacts, activate a contract and submit usage metering. Short, concrete asks such as "show open private offers for Acme" work better than long paragraphs.

### Does connecting Clazar give the AI access to everything in my Clazar account?

No. Every call to Clazar runs as the person who signed in, so the agent only sees the buyers, contracts and offers that person can already see in Clazar. Elaichi can narrow that further with per-tool restrictions, and it can never widen it beyond what Clazar itself allows.

### Can my team share one Clazar connection?

Yes. One person connects Clazar in Elaichi and shares it with a team, and nobody else ever handles the Clazar API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every Clazar update.

### Can I stop an agent from deleting or changing things in Clazar?

Yes. Restrictions in Elaichi work per action, so you can allow reading Clazar contracts and opportunities while blocking updates, contact deletion or metering submissions. A restricted action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt can reach it.

### What happens to a Clazar connection when someone leaves?

Offboarding a person in Elaichi ends their Clazar access at once, across every client they used. A shared Clazar connection keeps working for everyone else on the team. If you want Clazar gone entirely, disconnecting it once in Elaichi removes it from every client.

### Does the Clazar MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Clazar is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

## All 29 Clazar tools

Every tool below is callable through https://api.elaichi.ai/mcp once Clazar is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Create a Clazar authenticate** (Create). Create an access token in Clazar by exchanging client credentials. Returns the access_token used as the Bearer credential for subsequent Clazar API requests. Requires client_id and client_secret.
- **List all Clazar analytics datasets** (List). List records from a Clazar analytics dataset. Returns a paginated collection of dataset rows in results; the row fields are specific to the dataset selected. Required: dataset_name (e.g. aws_cosell_opportunities, aws_marketplace_revenue, gcp_marketplace_monthly_insights). Supports ordering and search; page and page_size are handled automatically.
- **Get single Clazar buyer by ID** (Get). Get a Clazar buyer by id. Returns the buyer record including id, cloud, cloud_identifiers, status, and custom_properties. Required: id.
- **List all Clazar buyers** (List). List Clazar buyers for your cloud marketplace agreements. Returns buyer records including id, cloud, cloud_identifiers, status, and custom_properties.
- **Update a Clazar buyer by ID** (Update). Update a Clazar buyer by id (partial update) — set the buyer's custom_properties or external_object_associations. Returns the updated buyer record including id, custom_properties, and external_object_associations. Required: id.
- **Create a Clazar contact** (Create). Create a contact in Clazar. Returns the created contact record including its uuid, email, full_name, and phone_number.
- **Delete a Clazar contact by ID** (Delete). Delete a contact in Clazar by id (contact UUID). Returns an empty 204 response on success. Required: id.
- **Get single Clazar contact by ID** (Get). Get a single contact in Clazar by id (contact UUID). Returns the contact record including its uuid, email, full_name, and phone_number. Required: id.
- **List all Clazar contacts** (List). List contacts in Clazar. Returns: uuid, email, full_name, phone_number.
- **Update a Clazar contact by ID** (Update). Partially update a contact in Clazar by id (contact UUID). Returns the updated contact record including its uuid, email, full_name, and phone_number. Required: id.
- **Clazar contracts activate** (Activate). Activate a contract in Clazar by its id. Returns an empty response body on success. Required: contract_id.
- **Get single Clazar contract by ID** (Get). Get a single Clazar contract by id. Returns the contract record including id, cloud, cloud_id, status, buyer_id, listing_id, accepted_at, start_at, end_at, and custom_properties. Required: id.
- **List all Clazar contracts** (List). List Clazar marketplace contracts with filters for cloud (aws, azure, gcp), status (active, inactive, pending), buyer_id, listing_id, date ranges, and cloud-specific identifiers. Returns contract records including id, cloud, cloud_id, status, accepted_at, start_at, and end_at.
- **Update a Clazar contract by ID** (Update). Update a Clazar contract by id, setting custom_properties (custom property API names and values in key-value format) and external_object_associations (Salesforce, Hubspot, Orb, etc.). Returns the updated contract record including id, cloud, cloud_id, status, and custom_properties. Required: id.
- **Get single Clazar listing by ID** (Get). Get a single Clazar marketplace listing by id. Returns the listing record including its id, cloud, cloud_id, status, and last_modified_at. Required: id.
- **List all Clazar listings** (List). List Clazar marketplace listings. Returns each listing with id, cloud, cloud_id, status, and last_modified_at. Filter by cloud, cloud_id, status, or last_modified_at_before/after; use ordering to sort results.
- **Create a Clazar metering** (Create). Create metering records in Clazar in bulk. Returns the created metering record including its id, cloud, contract_id, dimension, and status. Required: request (array of metering record objects).
- **Get single Clazar metering by ID** (Get). Get a single Clazar metering record by id. Returns: id, cloud, contract_id, dimension, status, custom_properties, created_at, updated_at. Required: id.
- **List all Clazar metering** (List). List Clazar metering records. Returns: id, cloud, contract_id, dimension, status, custom_properties, created_at, updated_at. Filter by cloud, contract_id, dimension, or status; sort with ordering.
- **Update a Clazar metering by ID** (Update). Update a Clazar metering record by id. Returns the updated record including its id, cloud, contract_id, dimension, and custom_properties. Required: id.
- **Get single Clazar opportunity by ID** (Get). Get a single Clazar opportunity by its UUID id. Returns: id, cloud, cloud_id, stage, status, accept_by, target_close_date, created_at, last_modified_at, metadata. Required: id.
- **List all Clazar opportunities** (List). List Clazar opportunities, filterable by cloud, cloud_id, stage, status, and created/last-modified/target-close/accept-by date ranges. Returns: id, cloud, cloud_id, stage, status, accept_by, target_close_date, created_at, last_modified_at, metadata.
- **Update a Clazar opportunity by ID** (Update). Update a Clazar opportunity by id, e.g. its custom_properties or external_object_associations with external systems like Salesforce, Hubspot, or Orb. Returns: id, cloud, cloud_id, stage, status, accept_by, target_close_date, created_at, last_modified_at, metadata. Required: id.
- **Get single Clazar private offer by ID** (Get). Get a Clazar Private Offer by id. Returns the Private Offer record including id, cloud, cloud_id, status, accepted_at, and expiration_at. Required: id (UUID of the Private Offer).
- **List all Clazar private offers** (List). List Clazar Private Offers, filterable by cloud, cloud_id, status, and accepted_at/published_at/expiration_at date ranges. Returns Private Offer records including id, cloud, cloud_id, status, and accepted_at.
- **Update a Clazar private offer by ID** (Update). Update a Clazar Private Offer by id, setting its custom properties and associations with external systems (Salesforce, Hubspot, Orb, etc.). Returns the updated Private Offer record including id, cloud, cloud_id, status, and accepted_at. Required: id.
- **Get single Clazar reseller offer by ID** (Get). Get a single Clazar reseller offer by id. Returns the reseller offer including its id, cloud, cloud_id, status, custom_properties, and external_object_associations. Required: id.
- **List all Clazar reseller offers** (List). List Clazar reseller offers, filterable by accepted, published, and expiration date ranges, cloud, cloud_id, and status. Returns reseller offer records including id, cloud, cloud_id, status, and custom_properties.
- **Update a Clazar reseller offer by ID** (Update). Update a Clazar reseller offer by id, setting its custom_properties and/or external_object_associations. Returns the updated reseller offer including id, cloud, cloud_id, status, and custom_properties. Required: id.