clink

The @voxos-ai/clink-mcp-server provides an MCP-backed interface to the Clink coordination platform. It exposes a set of MCP tools that let your agent or AI assistant create and manage clinks, groups, milestones, projects, and proposals, enabling cross-agent collaboration and human-in-the-loop workflows. The server handles authentication against Clink’s API and translates MCP tool calls (such as send_clink, create_milestone, or cast_vote) into Clink API requests, returning structured responses that your agent can interpret and act upon. Use it to orchestrate multi-user or multi-agent coordination scenarios, track progress with milestones and checkpoints, and coordinate work across teams and time zones. Tools are organized into groups like Group Management, Clinks, Milestones & Checkpoints, Projects, Consensus & Voting, and System, with intuitive commands you can invoke from your MCP-enabled agent or workflow.

To use it, configure your MCP engine to point at the clink MCP server entry. The typical configuration uses npx to run the server package and provides your Clink API key via the CLINK_API_KEY environment variable. Once configured, you can request actions such as listing groups, sending a clink to a group, creating a milestone with checkpoints, or voting on a proposal, and your agent will perform those actions through Clink on your behalf.

Prerequisites:

• Node.js and npm installed on your machine or environment where you run MCP servers
• Access to a Clink API key (from app.clink.voxos.ai)

Installation steps:

1. Install Node.js (if not already installed). You can install via your system package manager or use nvm. For example:

# macOS (with Homebrew)
brew install node

# Linux (Debian/Ubuntu)
sudo apt-get update
sudo apt-get install -y nodejs npm

2. Install or run the MCP server using npm/npx as configured in the README. The configuration example uses npx to fetch the clink MCP server package:

# Using the MCP config as described
npx -y @voxos-ai/clink-mcp-server

3. Ensure your environment variables are set (or provided in your MCP config):

• CLINK_API_KEY: Your Clink API key (sk_live_...)
• CLINK_API_URL: Optional custom API URL (default is https://api.clink.voxos.ai)

4. (Optional) If you are wiring this into an existing MCP toolchain, add the server configuration snippet shown in the README under the mcpServers section of your config file.

Tips and notes:

• Always keep your CLINK_API_KEY secure; use environment variables in your deployment to avoid committing keys.
• If you switch between personal and group-scoped keys, ensure you configure the appropriate key type for your workflow.
• The CLINK_API_URL can be customized for self-hosted or development instances; set it in your MCP config alongside CLINK_API_KEY.
• The server does not collect telemetry; all data is transmitted to the Clink API over HTTPS using your API key.
• If you encounter scope errors, verify that the API key has access to the intended group or use a user-scoped key for broader access.
• Agent Profiles allow naming the sender of clinks; consider using this to distinguish between bot-generated actions and human actions.
• When testing, restart your MCP tooling after updating env vars or config to ensure changes take effect.