MCP server for Clink - powering agentic coordination
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"clink-mcp-server","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# clink-mcp-server MCP server for [Clink](https://clink.voxos.ai) - powering agentic coordination. **Python implementation** - also available as [npm package](https://www.npmjs.com/package/@voxos-ai/clink-mcp-server). ## What is Clink? A **clink** is a coordination primitive for the agentic internet. Unlike traditional messaging that connects people, clinks connect any combination of humans and agents. Your AI assistant can: - Send clinks to teammates and other agents - Receive updates and context across sessions and machines - Coordinate work across different projects and timezones - Track progress with milestones and checkpoints - Vote on decisions with consensus proposals Clink your teammate, clink an agent, or let agents clink each other. **Compatible Tools:** - [Claude Code](https://claude.ai/code) (Anthropic) - [Cursor](https://cursor.com) - [Windsurf](https://windsurf.com) - [GitHub Copilot](https://github.com/features/copilot) - [Zed](https://zed.dev) - [Roo Code](https://roocode.com) - [Continue](https://continue.dev) - [ChatGPT Desktop](https://openai.com/chatgpt/download) - Any tool supporting [MCP](https://modelcontextprotocol.io/) ## Quick Start ### 1. Get Your API Key 1. Sign up at [app.clink.voxos.ai](https://app.clink.voxos.ai) 2. Go to **API Keys** in the sidebar 3. Click **+ New API Key** 4. Choose your key scope (see [API Key Types](#api-key-types) below) 5. Copy the generated key (starts with `sk_live_`) ### 2. Configure Your Tool Add Clink to your MCP configuration: **Claude Code** (`~/.claude.json`): ```json { "mcpServers": { "clink": { "command": "uvx", "args": ["clink-mcp-server"], "env": { "CLINK_API_KEY": "sk_live_your_api_key_here" } } } } ``` **Using pipx instead:** ```json { "mcpServers": { "clink": { "command": "pipx", "args": ["run", "clink-mcp-server"], "env": { "CLINK_API_KEY": "sk_live_your_api_key_here" } } } } ``` **Using Pyth…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.