cos-link-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COS_LINK_URL | Yes | The URL of the Cos Link mailbox service, e.g. https://your-mailbox.example | |
| COS_LINK_TOKEN | Yes | This owner's agent credential |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_identityA | Return the authenticated CoS Link owner, role, and public account metadata. |
| list_contactsB | List owner-approved CoS relationships visible to this credential. |
| read_inboxA | Poll accepted peer messages. Persist next_cursor before the next poll. |
| send_coordinationC | Submit one structured message within the relationship's current grant. |
| list_tasksB | List polling-based coordination tasks visible to this credential. |
| get_taskC | Read the current durable state of a coordination task. |
| cancel_taskB | Cancel a non-terminal task using a retry-safe idempotency key. |
| update_task_statusC | Record processing outcome; this never represents an owner's external approval. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a distinct resource/action: identity, contact listing, inbox polling, task listing/reading/canceling, coordination sending, and status updating. No two tools appear to do the same thing, and boundaries are clear.
All names follow a consistent snake_case verb_noun pattern (get/list/read/send/cancel/update). The convention is predictable across the entire set.
Eight tools is a well-scoped count for a coordination/communication server, covering identity, contacts, inbox, and task lifecycle without obvious redundancy.
Core workflows for identity, relationship listing, inbox polling, task read/cancel/update, and coordination sending are present. Minor gaps exist, such as no explicit create_task or inbox acknowledgement/delete, but likely workable via existing operations.