MCP Integration (Model Context Protocol)

What is MCP? The Model Context Protocol lets AI assistants like Claude, Cursor, and others connect directly to Cajari. Once configured, you can ask your AI assistant questions about your Seller Central data in natural language.

Overview

Cajari provides an MCP server that AI assistants can connect to. This gives the assistant the ability to check your execution status, view reports, list your merchant marketplaces, and even trigger new executions — all through natural conversation.

The MCP server uses the same API key as the REST API, and all data is scoped to your account.

Setup

To connect your AI assistant to Cajari, add the following to your MCP client configuration. Your API key can be found on the Account Settings page.

Claude Code

Add to .mcp.json in your project root:

{
  "mcpServers": {
    "cajari": {
      "type": "http",
      "url": "https://api.cajari.com/mcp/",
      "headers": {
        "Authorization": "Bearer <your_api_key_here>"
      }
    }
  }
}

Or add it via the command line:

claude mcp add --transport http cajari https://api.cajari.com/mcp/ \
    --header "Authorization: Bearer <your_api_key_here>"

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "cajari": {
      "type": "streamable-http",
      "url": "https://api.cajari.com/mcp/",
      "headers": {
        "Authorization": "Bearer <your_api_key_here>"
      }
    }
  }
}

Other MCP-compatible clients (Cursor, Windsurf, etc.) will have similar configuration options. The endpoint and authentication are the same for all clients.

Note: The type value varies by client. Claude Code uses "http", while Claude Desktop and the MCP specification use "streamable-http".

Available Tools

Once connected, your AI assistant will have access to the following tools. You don't need to call these directly — just ask your assistant what you want to know and it will use the appropriate tool automatically.

Tool	Description
`whoami`	Get information about the authenticated account
`list_available_skills`	List all available skills that can be enabled for merchant marketplaces
`list_seller_central_accounts`	List your Seller Central accounts with login status and last execution info
`trigger_discovery`	Trigger discovery for a Seller Central account to find all available merchant + marketplace combinations
`list_merchant_marketplaces`	List active merchant + marketplace combinations (use `include_disabled` to show all)
`get_merchant_marketplace`	Get details for a single merchant marketplace including all skills with enabled/disabled state
`enable_merchant_marketplace`	Enable a merchant marketplace (set status to active)
`disable_merchant_marketplace`	Disable a merchant marketplace so it won't be included in scheduled executions
`update_merchant_marketplace`	Update a merchant marketplace's status (active/disabled) and/or customer reference fields (customer_id / customer_name)
`set_merchant_marketplace_skills`	Set which skills are enabled for a merchant marketplace
`trigger_execution`	Queue a new execution for a specific merchant marketplace
`get_todays_executions`	Get today's execution status — which completed, failed, or are still in progress
`list_executions`	Browse recent executions, filterable by merchant marketplace or time range
`get_execution_detail`	Get details of a specific execution including skill results
`list_results`	List skill results, filterable by skill type, merchant marketplace, or time range
`get_report`	Download the actual report data (JSON/CSV) for a specific result; oversized reports return a truncated preview plus a download link for the full raw file
`get_api_info`	Get REST API documentation for building integrations

Example Prompts

Here are some things you can ask your AI assistant once Cajari is connected:

What you ask	What happens
"How did today's executions go?"	Uses `get_todays_executions` to show a summary of successes, failures, and in-progress runs
"Show me the latest chargebacks for my US marketplace"	Uses `list_results` filtered by skill and merchant, then `get_report` to fetch the data
"Are any Seller Central accounts having login problems?"	Uses `list_seller_central_accounts` and checks for login failures
"What failed in the last 3 days?"	Uses `list_executions` with a 3-day lookback to find failures
"Run an execution for merchant marketplace ABC123"	Uses `trigger_execution` to queue it
"Why did the latest execution for Demo Merchant fail?"	Uses `list_executions` to find it, then `get_execution_detail` to read the logs

Authentication

The MCP server uses the same API key as the REST API. The key is sent as a Bearer token in the Authorization header. All data returned is scoped to your account — you can only see and interact with your own Seller Central accounts, merchant marketplaces, executions, and results.

Your API key can be found on the Account Settings page.

Technical Details

Endpoint	`https://api.cajari.com/mcp/`
Transport	Streamable HTTP (JSON-RPC 2.0 over HTTP POST)
Authentication	Bearer token (`Authorization: Bearer <api_key>`)
Protocol Version	2024-11-05