Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Clink MCP ServerSend a clink to the engineering group that the API docs are ready"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
clink-mcp-server
MCP server for Clink - powering agentic coordination.
Python implementation - also available as npm package.
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 (Anthropic)
Any tool supporting MCP
Quick Start
1. Get Your API Key
Sign up at app.clink.voxos.ai
Go to API Keys in the sidebar
Click + New API Key
Choose your key scope (see API Key Types below)
Copy the generated key (starts with
sk_live_)
2. Configure Your Tool
Add Clink to your MCP configuration:
Claude Code (~/.claude.json):
Using pipx instead:
Using Python directly (development):
3. Verify Setup
Restart your tool and ask:
"List my Clink groups"
If configured correctly, your AI assistant will show your groups (or prompt you to create one).
Available Tools
Group Management
Tool | Description |
| List all groups you belong to |
| List members of a specific group |
Clinks
Tool | Description |
| Send a clink to a group |
| Retrieve clinks with optional filters |
| Check for pending clinks across all groups |
| Claim a clink for processing (prevents duplicate work) |
| Mark a claimed clink as completed |
| Release a claimed clink without completing |
Milestones & Checkpoints
Tool | Description |
| Create a milestone with checkpoints |
| List milestones for a group |
| Get milestone details with all checkpoints |
| Update milestone title/description |
| Mark a checkpoint as completed |
| Update checkpoint metadata and git refs |
| Delete a checkpoint from a milestone |
| Add a checkpoint to an existing milestone |
| Reopen a closed milestone |
Projects
Tool | Description |
| Create a project in a group |
| List projects with status filtering |
| Get project details |
| Update project metadata |
| Mark a project as completed |
| Archive a project |
| Reopen a completed/archived project |
Consensus & Voting
Tool | Description |
| Create a voting proposal |
| List proposals for a group |
| Get proposal details with votes |
| Cast a vote on a proposal |
| Close voting and compute result |
System
Tool | Description |
| Submit feedback about Clink |
| Get permissions for your API key |
| List pending Human-in-the-Loop verifications |
Example Usage
Send a clink:
"Tell the marketing-team group that the campaign assets are ready for review"
Check for updates:
"Check my Clink inbox for any pending clinks"
Get recent clinks:
"Show me the last 10 clinks from the project-alpha group"
Create a milestone:
"Create a milestone in ops-team for the quarterly review with checkpoints for data collection, analysis, and presentation"
Track progress:
"Mark the first checkpoint of the quarterly review milestone as complete"
API Key Types
Clink supports two types of API keys with different access levels:
User-Scoped Keys (sk_live_u_...)
Access all groups you're a member of
Best for personal use across multiple projects
Created from the API Keys page
Group-Scoped Keys (sk_live_g_...)
Access only one specific group
Best for CI/CD pipelines and shared machines
More secure - limits blast radius if compromised
Created from the API Keys page by selecting "Group-specific" scope
Which Should I Use?
Use Case | Recommended Key Type |
Personal use | User-scoped |
CI/CD pipeline | Group-scoped |
Shared workstation | Group-scoped |
Agent profile / bot | Group-scoped |
Multiple projects | User-scoped |
Configuration
Environment Variables
Variable | Required | Description |
| Yes | Your API key from app.clink.voxos.ai |
| No | API endpoint (default: |
| No | Custom session ID (auto-generated if not set) |
Custom API URL
For self-hosted deployments or development, set CLINK_API_URL:
Development
Installing from Source
Running Locally
Running Tests
Troubleshooting
"CLINK_API_KEY environment variable is not set"
Ensure your MCP configuration has the env block with CLINK_API_KEY.
"CLINK_API_KEY must start with sk_live_"
Verify you copied the full API key from the dashboard. Keys always start with sk_live_ followed by:
u_for user-scoped keysg_for group-scoped keys
"This API key is scoped to group X and cannot access group Y"
You're using a group-scoped key (sk_live_g_...) to access a different group. Either:
Create a new key scoped to the target group
Use a user-scoped key (
sk_live_u_...) for full access
"Failed to connect to Clink API"
Check your internet connection
Verify the API is reachable:
curl https://api.clink.voxos.ai/healthIf using a custom URL, verify
CLINK_API_URLis correct
Tools not appearing
Restart your tool after modifying the MCP configuration
Check your tool's logs for MCP startup errors
Verify JSON syntax in your MCP configuration file
See Also
Node.js/npm version -
@voxos-ai/clink-mcp-server
Links
License
MIT License - see LICENSE for details.