← usefulapi.io

INDIVIDUAL MCP TOOL

humanitix_create_event

Create a base event (name, description, timezone, one or more date ranges, location, keywords, classification).

usefulapi.ionone authenticationAvailability not checked

LIVE ENDPOINT

https://humanitix.usefulapi.io/mcp

No auth detected

Connect to this endpoint to inspect the live schema for humanitix_create_event and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Potential side effects detected · medium confidence · heuristic, not a guarantee.

  • A tool name or description contains a write-action term.

Parent server

usefulapi.io

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.humanitix-mcp]
url = "https://humanitix.usefulapi.io/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "humanitix-mcp": {
      "type": "http",
      "url": "https://humanitix.usefulapi.io/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: humanitix-mcp
Remote MCP URL: https://humanitix.usefulapi.io/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "humanitix-mcp": {
      "url": "https://humanitix.usefulapi.io/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "humanitix-mcp": {
      "type": "http",
      "url": "https://humanitix.usefulapi.io/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "humanitix-mcp",
  "transport": "streamable-http",
  "url": "https://humanitix.usefulapi.io/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

  • humanitix_list_events — List your events, newest first, with dates, ticket types, pricing and capacity.
  • humanitix_get_event — Fetch one event: name, description, URL, dates (each date's _id is the event_date_id other tools take), ticket types, packaged tickets, pricing, location, capacity and publish state.
  • humanitix_get_check_in_count — How many attendees have checked in for one date of an event, in total and per ticket type (ticket types with sales only, most check-ins first).
  • humanitix_list_orders — List the orders for an event (optionally one date of it): buyer name/email, financial status, totals, discounts, payment type and sales channel.
  • humanitix_get_order — Fetch one order of an event, with its totals breakdown, answers to checkout questions and buyer details.
  • humanitix_list_tickets — List the tickets (attendees) for an event, optionally one date of it and complete or cancelled only: attendee name, ticket type, price, check-in state and seating.
  • humanitix_get_ticket — Fetch one ticket of an event, including its check-in history and any swap history.
  • humanitix_list_tags — List the tags you use to group events (events carry them in tagIds).