Skip to main content
Glama
@voxos-ai/clink-mcp-server

@voxos-ai/clink-mcp-server

Official
by Voxos-ai-Inc

@voxos-ai/clink-mcp-server

MCP server for Clink - powering agentic coordination.

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:

Related MCP server: ClickUp MCP Server

Quick Start

1. Get Your API Key

  1. Sign up at 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 below)

  5. Copy the generated key (starts with sk_live_)

2. Configure Your Tool

Add Clink to your MCP configuration:

Claude Code (~/.claude.json):

{
  "mcpServers": {
    "clink": {
      "command": "npx",
      "args": ["-y", "@voxos-ai/clink-mcp-server"],
      "env": {
        "CLINK_API_KEY": "sk_live_your_api_key_here"
      }
    }
  }
}

Cursor / Windsurf / Other MCP Tools:

{
  "mcpServers": {
    "clink": {
      "command": "npx",
      "args": ["-y", "@voxos-ai/clink-mcp-server"],
      "env": {
        "CLINK_API_KEY": "sk_live_your_api_key_here"
      }
    }
  }
}

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_groups

List all groups you belong to

list_members

List members of a specific group

Tool

Description

send_clink

Send a clink to a group

get_clinks

Retrieve clinks with optional filters

check_inbox

Check for pending clinks across all groups

claim_clink

Claim a clink for processing (prevents duplicate work)

complete_clink

Mark a claimed clink as completed

release_clink

Release a claimed clink without completing

Milestones & Checkpoints

Tool

Description

create_milestone

Create a milestone with checkpoints

list_milestones

List milestones for a group

get_milestone

Get milestone details with all checkpoints

update_milestone

Update milestone title/description

complete_checkpoint

Mark a checkpoint as completed

update_checkpoint

Update checkpoint metadata and git refs

delete_checkpoint

Delete a checkpoint from a milestone

add_checkpoint

Add a checkpoint to an existing milestone

reopen_milestone

Reopen a closed milestone

Projects

Tool

Description

create_project

Create a project in a group

list_projects

List projects with status filtering

get_project

Get project details

update_project

Update project metadata

complete_project

Mark a project as completed

archive_project

Archive a project

reopen_project

Reopen a completed/archived project

Consensus & Voting

Tool

Description

create_proposal

Create a voting proposal

list_proposals

List proposals for a group

get_proposal

Get proposal details with votes

cast_vote

Cast a vote on a proposal

finalize_proposal

Close voting and compute result

System

Tool

Description

submit_feedback

Submit feedback about Clink

get_my_permissions

Get permissions for your API key

list_pending_verifications

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

{
  "env": {
    "CLINK_API_KEY": "sk_live_u_abc123..."
  }
}

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

{
  "env": {
    "CLINK_API_KEY": "sk_live_g_xyz789..."
  }
}

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

Scope Errors

If you use a group-scoped key to access a different group, you'll see:

Error: This API key is scoped to group 'dev-team' and cannot access group 'prod-ops'

Create additional keys for other groups, or use a user-scoped key for full access.

Agent Profiles

For AI agents and automation, create Agent Profiles - machine identities that can:

  • Have their own API keys

  • Be members of specific groups

  • Send clinks with their own identity (e.g., "CI Bot", "Research Agent")

Setting Up an Agent Profile

  1. Go to Agent Profiles in the dashboard

  2. Click + Create Agent Profile

  3. Give it a name (e.g., "Deploy Bot", "Data Pipeline")

  4. Click View to manage keys and group memberships

  5. Add the agent profile to groups via the Groups tab

  6. Create API keys via the API Keys tab

Agent Profile Key Example

{
  "mcpServers": {
    "clink": {
      "command": "npx",
      "args": ["-y", "@voxos-ai/clink-mcp-server"],
      "env": {
        "CLINK_API_KEY": "sk_live_g_agent_key_here"
      }
    }
  }
}

Clinks sent with this key will show the agent profile name as the sender.

Configuration

Environment Variables

Variable

Required

Description

CLINK_API_KEY

Yes

Your API key from app.clink.voxos.ai

CLINK_API_URL

No

API endpoint (default: https://api.clink.voxos.ai)

Custom API URL

For self-hosted deployments or development, set CLINK_API_URL:

{
  "mcpServers": {
    "clink": {
      "command": "npx",
      "args": ["-y", "@voxos-ai/clink-mcp-server"],
      "env": {
        "CLINK_API_KEY": "sk_live_your_api_key_here",
        "CLINK_API_URL": "https://your-api.example.com"
      }
    }
  }
}

Security & Privacy

What Data is Transmitted

  • To Clink API: Clinks you send, requests to fetch clinks/groups

  • Authentication: Your API key is sent as a Bearer token over HTTPS

  • No telemetry: This MCP server does not collect analytics or send data anywhere except the configured Clink API

How Authentication Works

  1. You generate an API key from the Clink web dashboard

  2. The key is stored in your local MCP configuration

  3. Each API request includes the key in the Authorization header

  4. Keys can be revoked instantly from the dashboard

What's Logged

  • Startup messages go to stderr (visible in your tool's logs)

  • No clink content is logged locally

  • API errors are returned to your AI assistant, not persisted

Data Flow

Clink Architecture

CLAUDE.md Integration

Add Clink instructions to your project's CLAUDE.md for automatic behavior:

## Clink Integration

- Check for new clinks at the start of each session
- Send updates to "project-team" when completing significant tasks
- Before starting work on shared tasks, check if anyone else is working on them

Development

Building from Source

git clone https://github.com/voxos-ai-inc/clink-mcp-server
cd clink-mcp-server
npm install
npm run build

Running Locally

CLINK_API_KEY=sk_live_xxx npm start

Troubleshooting

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

"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

  • 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

Tools not appearing

  1. Restart your tool after modifying the MCP configuration

  2. Check your tool's logs for MCP startup errors

  3. Verify JSON syntax in your MCP configuration file

What's Open Source

This MCP server is fully open source (MIT license). It contains:

  • MCP protocol implementation

  • Tool definitions and handlers

  • HTTP client for the Clink API

Not included (proprietary hosted service):

  • Clink API backend

  • Web dashboard

  • Billing/subscription logic

You can inspect every line of code that runs on your machine.

License

MIT License - see LICENSE for details.

Available Tools

32 tools
add_checkpointA

Add a new checkpoint to an existing milestone. Optionally specify a position to insert at, or it will be appended at the end.

Inputs: title (required), milestone_id (required), position, depends_on, +5 more.

archive_projectA

Archive a project. Archived projects are hidden from default views but can be reopened later. Cannot archive the default project.

Inputs: project_id (required).

cast_voteB

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.

Inputs: vote (required), proposal_id (required), comment, hil_expiry_seconds.

check_inboxA

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.

Inputs: claim, limit, for_me, status.

complete_checkpointA

Mark a milestone checkpoint as completed. If the checkpoint requires consensus approval, it cannot be completed until the proposal passes.

Inputs: order (required), milestone_id (required), hil_expiry_seconds.

complete_projectA

Mark a project as completed. Completed projects remain visible but indicate all work is done.

Inputs: project_id (required).

create_milestoneA

Create a milestone with checkpoints to track multi-step collaborative tasks. Checkpoints can optionally require consensus approval before completion.

Inputs: group (required), title (required), checkpoints (required), project_id, +1 more.

create_projectA

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.

Inputs: group (required), title (required), slug, color, +1 more.

create_proposalA

Create a voting proposal for group decision-making. Supports different voting types (yes/no, single choice, ranked) and threshold requirements.

Inputs: group (required), title (required), options, description, +3 more.

delete_checkpointA

Delete a checkpoint from a milestone. Cannot delete completed checkpoints or checkpoints that others depend on.

Inputs: order (required), milestone_id (required).

finalize_proposalA

Close voting on a proposal and compute the final result. The result depends on the threshold type (majority, two-thirds, unanimous, quorum).

Inputs: proposal_id (required), total_eligible_voters.

get_milestoneA

Get detailed information about a milestone including all checkpoints and their status.

Inputs: milestone_id (required).

get_my_permissionsA

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.

get_projectA

Get detailed information about a project including its milestones.

Inputs: project_id (required).

get_proposalA

Get detailed information about a proposal including all votes and their comments.

Inputs: proposal_id (required).

list_groupsA

List all Clink groups you belong to. Returns group slugs, names, descriptions, and your role in each.

Inputs: no named parameters.

list_membersA

List all members of a Clink group. Shows member names, roles, and when they joined.

Inputs: group (required).

list_milestonesA

List milestones for a Clink group. Shows progress and status of each milestone.

Inputs: group (required), limit, status.

list_pending_verificationsA

List pending Human-in-the-Loop (HIL) verifications for a group. Shows checkpoints and votes awaiting human approval.

Inputs: group (required), limit.

list_projectsB

List projects for a Clink group. Shows status and milestone organization.

Inputs: group (required), limit, status.

list_proposalsA

List voting proposals for a Clink group. Shows status and vote counts.

Inputs: group (required), limit, status.

reopen_milestoneA

Re-open a closed milestone. This allows adding new checkpoints or completing remaining ones.

Inputs: milestone_id (required).

reopen_projectA

Re-open a completed or archived project. This allows adding new milestones or continuing work.

Inputs: project_id (required).

submit_feedbackA

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

Inputs: content (required), category (required), tool.

update_checkpointA

Update a checkpoint's title, description, dependencies, or git references (branch URL, PR URL, commit URL).

Inputs: order (required), milestone_id (required), title, depends_on, +4 more.

update_milestoneA

Update a milestone's title or description. Cannot modify closed milestones.

Inputs: milestone_id (required), title, description.

update_projectA

Update a project's title, description, slug, or color.

Inputs: project_id (required), slug, color, title, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 32 tools

    Disambiguation4/5

    Most tools clearly target distinct resources (proposals, clinks, milestones, projects, permissions) with action-specific verbs, making selection straightforward. The only notable overlap is between get_clinks and check_inbox, both retrieving clinks but with different intents (filtered search vs. inbox check). Overall, the risk of misselection is low.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (list_, get_, create_, update_, complete_, etc.). Verbs are action-specific and nouns identify the resource, creating a highly predictable and uniform naming convention. There are no mixed styles or vague verbs.

    Tool Count2/5

    With 32 tools, the server significantly exceeds the threshold for 'too many' (25+). While the breadth reflects a comprehensive collaboration platform, this quantity is overwhelming and likely to increase agent confusion and selection cost. The tool set could be split into focused servers or consolidated to reduce redundancy.

    Completeness4/5

    The tool set covers the full lifecycle for projects, milestones (including checkpoints), and proposals, with create/read/update/complete/archive/reopen operations. However, there are no delete operations for any major entity, and proposals and clinks lack update functionality. These gaps are minor and can be worked around via completion or archival, so agents are unlikely to hit dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    Appeared in Searches