UnClick MCP Server

Search the UnClick tool marketplace by keyword or description. Use this to discover which tools are available for a task. Example: 'I need to resize an image' → returns the image tool with its endpoints.

Browse all available UnClick tools, optionally filtered by category. Returns a list of tools with their slugs and descriptions.

Get detailed information about a specific UnClick tool including all its endpoints, required parameters, and response shapes. Use this after unclick_search to understand exactly how to call a tool.

Call any UnClick tool endpoint. Specify the endpoint ID and parameters. Use unclick_search or unclick_tool_info to discover endpoint IDs and required params. Example: endpoint_id='image.resize', params={image: '', width: 800, height: 600}

Load persistent UnClick Memory at session start. Returns business context (standing rules), recent session summaries, and hot facts. Call this FIRST in every new session to understand the user's ongoing projects, preferences, and open loops. Works zero-config locally, or with Supabase for cross-machine sync.

Write a session summary at the end of a session. Critical for cross-session continuity. Call this BEFORE the session ends (when the user says goodbye, or context is running low). Include key decisions, open loops, and topics discussed.

Add a new atomic fact to UnClick Memory. One fact = one statement. Use when the user states a preference, makes a decision, or shares important info. Good: 'Team prefers Tailwind over CSS modules'. Bad: 'We talked about styling'.

Full-text search across UnClick Memory conversation logs. Use when you need to recall something specific from a previous session.

Add or update a standing rule in UnClick Memory (Layer 1). Business context is ALWAYS loaded at session start. Use for standing rules, client info, and preferences that are always relevant.