The official URPASS MCP Server exposes 10 high-performance operational tools via Anthropic's Model Context Protocol. Run locally with npx urpass-mcp over stdio, or connect your cloud agents to our remote JSON-RPC 2.0 HTTP endpoint.
₹29 introductory offer · 0% ticket commission · Cancel anytime
FEATURES
Run via local stdio for Claude Desktop and Cursor, or over remote JSON-RPC 2.0 HTTPS for cloud agents and webhooks.
No local builds or cloned repositories required. Run 'npx urpass-mcp' with your API key to immediately mount event tools.
Includes list_events, get_event_stats, list_attendees, approve_attendee, reject_attendee, verify_pass, and check_in_attendee.
All requests authenticate against scoped developer API keys with strict organizer isolation and database RLS.
Optimized PostgreSQL indexes and direct Supabase server connections keep agent tool invocations lightning fast.
Full input validation with Zod and standard JSON Schema definitions ensuring zero hallucinated tool arguments.
HOW IT WORKS
Navigate to your URPASS dashboard at /dashboard/developer and generate a production API key.
Add the urpass-mcp command and URPASS_API_KEY environment variable to your AI agent's configuration.
Client calls initialize; server responds with capabilities and the complete 10-tool operational schema.
Agent issues tools/call requests in response to user prompts, automating pass issuance and gate verification.
Changes reflect immediately across organizer web views, attendee digital passes, and mobile scanner interfaces.
STANDARDIZED AGENT PROTOCOL
Rather than writing one-off integrations for every AI assistant, the Model Context Protocol gives you a single, universally compatible interface. Any MCP-compliant client can instantly manage passes, check attendees in, and inspect gate capacity.
PASS SCANNED
Attendee check-in successful
For local desktop workflows like Anthropic Claude Desktop and Cursor IDE, stdio transport is ideal. The client spawns 'npx urpass-mcp' as a child process and communicates through standard input/output streams with zero network configuration.
For cloud microservices, Slack bots, and autonomous web agents, URPASS provides a remote JSON-RPC 2.0 endpoint at https://urpass.space/api/mcp. Cloud agents simply POST tool requests with an Authorization: Bearer <api_key> header.
Every tool exposed by URPASS MCP includes rigorous JSON Schema parameter definitions with explicit descriptions, required fields, and enum constraints.
If an LLM provides an invalid pass token or malformed attendee ID, the MCP server rejects the call with an informative client error, allowing the model to self-correct before touching production databases.
Discover how URPASS powers ticketing, digital credentials, and entrance management across different scenarios.
Get started for ₹29 · 0% ticket commission · Up and running in 5 minutes