Skip to main content
Glama
README.md
# UnClick MCP server

**The app store for AI agents.** [unclick.world](https://unclick.world)

450+ callable endpoints across 178+ tools, available to any MCP-compatible AI client. New tools ship to the API continuously. Your agent picks them up automatically; no package update is needed.
<!-- Update counts from src/config/site-stats.ts -->

## Install

**Using the latest GitHub release (no npm account required):**
```json
{
  "mcpServers": {
    "unclick": {
      "command": "npx",
      "args": ["-y", "https://github.com/malamutemayhem/unclick/releases/latest/download/unclick.tgz"]
    }
  }
}
```

Add this to your `claude_desktop_config.json` (or equivalent for Cursor, Windsurf, etc).

**Or install globally from GitHub:**
```bash
npm install -g https://github.com/malamutemayhem/unclick/releases/latest/download/unclick.tgz
```

## Operational Notes

This repo follows the AGENTS.md fence rules for agent work.

## Run

For local web development:

```bash
npm run dev
```

For the API workspace:

```bash
npm run dev:api
```

## Test

Run the main test suite:

```bash
npm test
```

Run the production build check:

```bash
npm run build
```

## License

UnClick uses a split license. The platform (website, API, and hosted backend
and memory services) is **AGPL-3.0** (see [LICENSE](./LICENSE)). The npm client
package `@unclick/mcp-server` stays **MIT**, and the standalone connector
packages stay **Apache-2.0**. Full breakdown and reasoning in
[LICENSING.md](./LICENSING.md).

## What it does

Gives your agent access to a growing catalog of tools across developer utilities, social media, e-commerce, finance, messaging, media, security, and more. You don't need to install separate packages for each integration. One server provides access to everything in the catalog.

## Tool Surface

UnClick exposes a small direct surface for daily agent workflows, plus hidden internal discovery tools for the full catalog.

| Tool group | Tools |
|------------|-------|
| Memory session protocol | `load_memory`, `save_fact`, `search_memory`, `save_identity`, `save_session` |
| Signals and Boardroom coordination | `check_signals`, `read_messages`, `post_message`, `create_todo`, `list_todos`, `update_todo`, `complete_todo`, `create_idea`, `list_ideas`, `vote_on_idea`, `promote_idea_to_todo` |
| Hidden internal catalog tools | `unclick_search`, `unclick_browse`, `unclick_tool_info`, `unclick_call` |

The agent starts with memory, uses direct Boardroom tools for coordination, and can still call the hidden catalog tools by name when it needs dynamic endpoint discovery.

### Compatibility and advanced memory operations

- Legacy memory names still work as aliases: `get_startup_context` -> `load_memory`, `write_session_summary` -> `save_session`, `add_fact` -> `save_fact`, `set_business_context` -> `save_identity`.
- The remaining memory operations are intentionally not listed in `ListTools` and are called through `unclick_call` with `endpoint_id: "memory.<op>"` (for example `memory.manage_decay`, `memory.store_code`, `memory.log_conversation`, `memory.supersede_fact`, `memory.upsert_library_doc`).

## Requirements

- Node.js 18+
- An API key from [unclick.world](https://unclick.world)

Set your key as an environment variable:
```bash
UNCLICK_API_KEY=your_key_here
```

Or pass it via the MCP config:
```json
{
  "mcpServers": {
    "unclick": {
      "command": "npx",
      "args": ["-y", "https://github.com/malamutemayhem/unclick/releases/latest/download/unclick.tgz"],
      "env": {
        "UNCLICK_API_KEY": "your_key_here"
      }
    }
  }
}
```

## More

Full catalog, docs, and API keys at [unclick.world](https://unclick.world).

TDQS

D1.8/5.0

Scored across 813 tools

Disambiguation1/5

The server aggregates an enormous and unrelated collection of tools from dozens of distinct domains, many with overlapping purposes (e.g., crypto_price vs cmc_quotes vs stock_quote, weather_forecast vs tomorrow_forecast vs willyweather_forecast, multiple search/search variants). Multiple generic 'action' tools (notion_action, github_action, etc.) abstract many sub-actions, creating ambiguity about which tool to call. Almost no tool has a unique, non-overlapping role across the set.

Naming Consistency1/5

Naming uses no consistent pattern: some tools use verb_noun (sendle_get_quote, list_calendly_event_types), some use noun_verb (mc_quotes, weather_forecast), many use bare domain prefixes (amber_sites, esports_matches), and several are generic 'action' tools (slack_action, github_action). Conventions are wildly mixed with no discernible consistent style.

Tool Count1/5

With 813 tools, this is a massive aggregate of almost every possible MCP integration, far beyond any single-purpose server. The count is extreme and unwieldy, making it nearly impossible for an agent to efficiently select the right tool. Many tools cover overlapping functionality across different providers.

Completeness1/5

The server attempts to cover an impossibly broad domain (global APIs, productivity, finance, gaming, media, etc.), but individual areas are often incomplete: many CRUD operations are missing (e.g., no update for many resources), several providers only expose partial endpoints, and no coherent lifecycle is covered for any single domain. The enormous breadth makes meaningful completeness assessment impossible, but obvious gaps exist (e.g., serious lack of write operations in many integrations).

Maintenance

ActivityActive
ResponsivenessSyncing