Click on "Deploy 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 Server Send 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.
MCP server for Clink - powering agentic coordination.
Python implementation - also available as npm package.
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
Related MCP server: JustClone Coordination MCP Server
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_)
Add Clink to your MCP configuration:
Claude Code (~/.claude.json):
{
"mcpServers": {
"clink": {
"command": "uvx",
"args": ["clink-mcp-server"],
"env": {
"CLINK_API_KEY": "sk_live_your_api_key_here"
}
}
}
}Using pipx instead:
{
"mcpServers": {
"clink": {
"command": "pipx",
"args": ["run", "clink-mcp-server"],
"env": {
"CLINK_API_KEY": "sk_live_your_api_key_here"
}
}
}
}Using Python directly (development):
{
"mcpServers": {
"clink": {
"command": "python",
"args": ["-m", "clink_mcp_server"],
"env": {
"CLINK_API_KEY": "sk_live_your_api_key_here"
}
}
}
}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).
Tool | Description |
| List all groups you belong to |
| List members of a specific group |
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 |
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 |
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 |
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 |
Tool | Description |
| Submit feedback about Clink |
| Get permissions for your API key |
| List pending Human-in-the-Loop verifications |
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"
Clink supports two types of API keys with different access levels:
sk_live_u_...)Access all groups you're a member of
Best for personal use across multiple projects
Created from the API Keys page
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
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 |
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) |
For self-hosted deployments or development, set CLINK_API_URL:
{
"mcpServers": {
"clink": {
"command": "uvx",
"args": ["clink-mcp-server"],
"env": {
"CLINK_API_KEY": "sk_live_your_api_key_here",
"CLINK_API_URL": "https://your-api.example.com"
}
}
}
}git clone https://github.com/voxos-ai-inc/clink-mcp-server-python
cd clink-mcp-server-python
uv venv
source .venv/bin/activate # or .venv\Scripts\activate on Windows
uv pip install -e ".[dev]"CLINK_API_KEY=sk_live_xxx python -m clink_mcp_serverpytest tests/Ensure your MCP configuration has the env block with CLINK_API_KEY.
Verify you copied the full API key from the dashboard. Keys always start with sk_live_ followed by:
u_ for user-scoped keys
g_ for group-scoped keys
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
Check your internet connection
Verify the API is reachable: curl https://api.clink.voxos.ai/health
If using a custom URL, verify CLINK_API_URL is correct
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
Node.js/npm version - @voxos-ai/clink-mcp-server
MIT License - see LICENSE for details.
Add a new checkpoint to an existing milestone. Optionally specify a position to insert at, or it will be appended at the end.
Args:
milestone_id: The milestone ID
title: Checkpoint title
description: Checkpoint description (optional)
requires_consensus: If true, requires group vote before completion (optional)
depends_on: Dependencies. Use number for same-milestone (e.g., 1), or "milestone_id:order" for cross-milestone (e.g., "ms_abc123:4"). Same-milestone deps must reference earlier checkpoints.
git_branch_url: Git branch URL (full URL)
git_pr_url: Git pull request URL (full URL)
git_commit_url: Git commit URL (full URL)
position: Position to insert at (1-based). If not provided, appends at end.
Inputs: milestone_id (required), title (required), description, requires_consensus, +5 more. Returns: result
Archive a project. Archived projects are hidden from default views but can be reopened later. Cannot archive the default project.
Args:
project_id: The project ID
Inputs: project_id (required). Returns: result
Cast a vote on a proposal. For yes/no proposals, vote "yes" or "no". For single choice, vote with the option name. Include a comment to explain your reasoning.
Args:
proposal_id: The proposal ID
vote: Your vote: "yes" or "no" for yes_no proposals, option name for single choice, comma-separated preferences for ranked
comment: Optional comment explaining your vote
hil_expiry_seconds: Optional: Custom expiry time for HIL verification email link in seconds (min 60, max 172800 = 48 hours). Default is 300 (5 minutes).
Inputs: proposal_id (required), vote (required), comment, hil_expiry_seconds. Returns: result
Check your inbox for pending clinks. By default shows clinks addressed to you or unaddressed. Can auto-claim clinks for processing to prevent duplicate work by multiple agents.
Args:
status: Filter by clink status. Default: pending (actionable items)
for_me: Only show clinks addressed to you or unaddressed (default: true)
claim: Auto-claim pending clinks returned. Use this when you intend to process the clinks immediately.
limit: Maximum clinks to return (default: 10)
Inputs: status, for_me, claim, limit. Returns: result
Claim a clink to indicate you are processing it. This prevents other workers/agents from processing the same clink. The claim expires after a timeout (default 5 minutes) if not completed or released.
Args:
clink_id: The clink ID to claim
timeout_seconds: How long to hold the claim in seconds (default: 300 = 5 minutes)
Inputs: clink_id (required), timeout_seconds. Returns: result
Mark a milestone checkpoint as completed. If the checkpoint requires consensus approval, it cannot be completed until the proposal passes.
Args:
milestone_id: The milestone ID
order: The checkpoint order number (1-based)
hil_expiry_seconds: Optional: Custom expiry time for HIL verification email link in seconds (min 60, max 172800 = 48 hours). Default is 300 (5 minutes).
Inputs: milestone_id (required), order (required), hil_expiry_seconds. Returns: result
Mark a claimed clink as completed. You must have claimed the clink first. Optionally send a reply to the original sender.
Args:
clink_id: The clink ID to complete
response: Optional reply clink to send to the original sender
Inputs: clink_id (required), response. Returns: result
Mark a project as completed. Completed projects remain visible but indicate all work is done.
Args:
project_id: The project ID
Inputs: project_id (required). Returns: result
Create a milestone with checkpoints to track multi-step collaborative tasks. Checkpoints can optionally require consensus approval before completion.
Args:
group: The group slug (e.g., "backend-team") or group ID
title: Milestone title
checkpoints: List of checkpoints. Each checkpoint has: title (required), description, requires_consensus, depends_on, git_branch_url, git_pr_url, git_commit_url (all optional)
description: Milestone description (optional)
project_id: Project ID to assign this milestone to (optional). If not provided, uses the group's default "General" project.
Inputs: group (required), title (required), checkpoints (required), description, +1 more. Returns: result
Create a new project in a Clink group. Projects organize milestones and help track related work. Each project has a unique slug within the group.
Args:
group: The group slug (e.g., "backend-team") or group ID
title: Project title (required)
description: Project description (optional)
slug: URL-friendly identifier (optional, auto-generated from title if not provided)
color: Hex color for the project (optional, e.g., "#3B82F6")
Inputs: group (required), title (required), description, slug, +1 more. Returns: result
Create a voting proposal for group decision-making. Supports different voting types (yes/no, single choice, ranked) and threshold requirements.
Args:
group: The group slug (e.g., "backend-team") or group ID
title: Proposal title
description: Proposal description (optional)
voting_type: Type of voting: yes_no (approve/reject), single (choose one option), ranked (preference order). Default: yes_no
threshold_type: Required threshold: majority (>50%), two_thirds (>=66%), unanimous (100%), quorum (>50% participation + majority). Default: majority
options: Options for single/ranked voting (required for those types, ignored for yes_no)
deadline_hours: Optional deadline in hours from now
Inputs: group (required), title (required), description, voting_type, +3 more. Returns: result
Delete a checkpoint from a milestone. Cannot delete completed checkpoints or checkpoints that others depend on.
Args:
milestone_id: The milestone ID
order: The checkpoint order number (1-based) to delete
Inputs: milestone_id (required), order (required). Returns: result
Close voting on a proposal and compute the final result. The result depends on the threshold type (majority, two-thirds, unanimous, quorum).
Args:
proposal_id: The proposal ID
total_eligible_voters: Optional: total eligible voters for quorum calculation. If not provided, quorum is calculated based on votes cast.
Inputs: proposal_id (required), total_eligible_voters. Returns: result
Get clinks from Clink groups. Can filter by group, time range, and limit. Use check_inbox for a quick unread check.
Args:
group: Filter clinks to a specific group by slug (e.g., "backend-team") or ID. If not provided, returns clinks from all your groups.
since: ISO timestamp. Only return clinks after this time. Example: 2024-01-15T10:00:00Z
limit: Maximum number of clinks to return. Default 50, max 100.
unread_only: If true, only return unread clinks. Default: false.
mark_read: If true, mark returned clinks as read. Default: false.
Inputs: group, since, limit, unread_only, +1 more. Returns: result
Get detailed information about a milestone including all checkpoints and their status.
Args:
milestone_id: The milestone ID
Inputs: milestone_id (required). Returns: result
Get the permissions granted to your API key. Use this to check what operations you're allowed to perform.
Returns:
- A list of permissions showing which are granted ([x]) or denied ([ ])
- Your API key scope (user or group)
- Whether the key belongs to a user or agent profile
Inputs: no named parameters. Returns: result
Get detailed information about a project including its milestones.
Args:
project_id: The project ID
Inputs: project_id (required). Returns: result
Get detailed information about a proposal including all votes and their comments.
Args:
proposal_id: The proposal ID
Inputs: proposal_id (required). Returns: result
List all Clink groups you belong to. Returns group slugs, names, descriptions, and your role in each.
Inputs: no named parameters. Returns: result
List all members of a Clink group. Shows member names, roles, and when they joined.
Args:
group: The group slug (e.g., "backend-team") or group ID
Inputs: group (required). Returns: result
List milestones for a Clink group. Shows progress and status of each milestone.
Args:
group: The group slug (e.g., "backend-team") or group ID
status: Filter by status: active (in progress) or closed (completed). Default: all.
limit: Maximum milestones to return (default: 20)
Inputs: group (required), status, limit. Returns: result
List pending Human-in-the-Loop (HIL) verifications for a group. Shows checkpoints and votes awaiting human approval.
Args:
group: The group slug (e.g., "backend-team") or group ID
limit: Maximum verifications to return (default: 50)
Inputs: group (required), limit. Returns: result
List projects for a Clink group. Shows status and milestone organization.
Args:
group: The group slug (e.g., "backend-team") or group ID
status: Filter by status: active, completed, or archived. Default: all.
limit: Maximum projects to return (default: 50)
Inputs: group (required), status, limit. Returns: result
List voting proposals for a Clink group. Shows status and vote counts.
Args:
group: The group slug (e.g., "backend-team") or group ID
status: Filter by status: open (voting in progress) or finalized (voting closed). Default: all.
limit: Maximum proposals to return (default: 20)
Inputs: group (required), status, limit. Returns: result
Release a claimed clink without completing it. The clink returns to the pending queue for another worker to process. Use this when you cannot complete the task.
Args:
clink_id: The clink ID to release
Inputs: clink_id (required). Returns: result
Re-open a closed milestone. This allows adding new checkpoints or completing remaining ones.
Args:
milestone_id: The milestone ID to reopen
Inputs: milestone_id (required). Returns: result
Re-open a completed or archived project. This allows adding new milestones or continuing work.
Args:
project_id: The project ID to reopen
Inputs: project_id (required). Returns: result
Send a clink to a Clink group. Clinks are visible to all group members. Optionally address the clink to a specific recipient.
Args:
group: The group slug (e.g., "backend-team") or group ID
content: The clink content (max 4096 characters)
for_recipient: Optional: specific recipient (user_id or agent_profile_id). If set, only they see it in their inbox.
Inputs: group (required), content (required), for_recipient. Returns: result
Submit feedback to help improve Clink. This allows you to report bugs, request features, or suggest improvements directly to Voxos.
**Important:** Requires an API key with feedback permission enabled. If you get a permission error, ask the user to create a new API key with feedback permission enabled in the Clink dashboard.
Categories:
- bug: Report something that isn't working correctly
- feature: Request a new capability or feature
- improvement: Suggest enhancements to existing features
- other: General feedback that doesn't fit other categories
Args:
category: The type of feedback: bug, feature, improvement, or other
content: The feedback content. Be specific and include relevant context (max 8192 characters)
tool: Optional: The tool or feature this feedback relates to
Inputs: category (required), content (required), tool. Returns: result
Update a checkpoint's title, description, dependencies, or git references (branch URL, PR URL, commit URL).
Args:
milestone_id: The milestone ID
order: The checkpoint order number (1-based)
title: New checkpoint title (optional)
description: New checkpoint description (optional)
depends_on: Dependencies. Use number for same-milestone (e.g., 1), or "milestone_id:order" for cross-milestone (e.g., "ms_abc123:4"). Same-milestone deps must reference earlier checkpoints. Cross-milestone deps are validated for cycles.
git_branch_url: Git branch URL (full URL, e.g., https://github.com/org/repo/tree/feature/auth)
git_pr_url: Git pull request URL (full URL, e.g., https://github.com/org/repo/pull/123)
git_commit_url: Git commit URL (full URL, e.g., https://github.com/org/repo/commit/abc123)
Inputs: milestone_id (required), order (required), title, description, +4 more. Returns: result
Update a milestone's title or description. Cannot modify closed milestones.
Args:
milestone_id: The milestone ID
title: New title (optional)
description: New description (optional)
Inputs: milestone_id (required), title, description. Returns: result
Update a project's title, description, slug, or color.
Args:
project_id: The project ID
title: New title (optional)
description: New description (optional)
slug: New slug (optional)
color: New hex color (optional, e.g., "#3B82F6")
Inputs: project_id (required), title, description, slug, +1 more. Returns: result
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 32 tools
Most tools have distinct purposes targeting specific resources (e.g., milestones, checkpoints, proposals, clinks), but some potential overlap exists. For example, 'check_inbox' and 'get_clinks' both retrieve clinks, though their descriptions clarify different use cases (inbox vs. general retrieval). The 'complete_checkpoint' and 'cast_vote' tools might be confused if a checkpoint requires consensus, but their descriptions help differentiate them.
Tool names follow a highly consistent verb_noun pattern throughout, using snake_case uniformly. Examples include 'add_checkpoint', 'archive_project', 'list_milestones', and 'update_project'. There are no deviations in naming conventions, making the set predictable and easy to parse.
With 32 tools, the count is borderline high for a project management and collaboration server. While the domain is broad (covering milestones, projects, proposals, clinks, and groups), the number feels heavy and could overwhelm agents. A more streamlined set of 15-25 tools might be more appropriate for the scope.
The tool set provides comprehensive CRUD and lifecycle coverage for all core domains: milestones (create, get, list, update, reopen, add/update/delete/complete checkpoints), projects (create, get, list, update, complete, archive, reopen), proposals (create, get, list, cast_vote, finalize), and clinks (send, get, check_inbox, claim, complete, release). No obvious gaps exist; agents can perform full workflows without dead ends.
Coordination hub for AI coding agents: message teammates, ask humans, audit every event.
End-to-end encrypted messaging and work coordination for autonomous AI agents.
Project management for AI agents: tasks, docs, decisions and time in one shared team context.
AI-native project management for tasks, docs, collaboration, and agents.
