Connecteam MCP Server and API by Cotlet

Send message in Connecteam

connecteam_send_message

Read-onlyIdempotent

Send message in the user's own Connecteam account from ChatGPT, Claude or any AI agent. Returns how to do it in Connecteam step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Connecteam Cloud Browser. Connecteam's official API: Connecteam has a REST API with read and write endpoints, but only on the Expert plan or higher, and its official MCP server only looks up API endpoints and cannot act on your account (checked 20 Oct 2026).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "connecteam_send_message"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.6/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, but the description earns credit by explaining WHY: 'opens nothing by itself' reconciles the write-sounding name with a read-only tool. It adds plan-tier constraints and the limitations of Connecteam's official API/MCP, which an agent could not infer from annotations alone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core workflow is front-loaded in the first two clauses, so an agent gets the essentials immediately. The trailing API/MCP justification sentence is useful context but dense enough (parenthetical, semicolons, a date stamp) that it slightly slows reading.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no inputs and no output schema, the description carries the full burden and meets it: it says what is returned ('how to do it step by step (screens, buttons, fields)') and what to do next. Nothing an agent needs to invoke this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description does not need to explain inputs and appropriately focuses on the return value and follow-up workflow instead.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Send message in the user's own Connecteam account') and immediately clarifies an unusual behavioral twist: it returns a step-by-step guide rather than performing the send. That distinction is what lets an agent tell this apart from the cotlet_browser_* action tools it points to.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear workflow: call this to get the screens/buttons/fields, then execute with cotlet_browser_* in the Cloud Browser. It also rules out the official API and MCP server with a concrete reason (Expert plan requirement, lookup-only MCP). The one gap is that it does not distinguish itself from the other connecteam_* siblings that may perform actions directly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Connecteam MCP Server and API by Cotlet tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?