Copper CRM MCP Server and API by Cotlet

Log activity in Copper CRM

copper_crm_log_activity

Read-onlyIdempotent

Log activity in the user's own Copper CRM account from ChatGPT, Claude or any AI agent. Returns how to do it in Copper CRM step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Copper CRM Cloud Browser. Copper CRM's official API: Yes, Copper has a full REST Developer API, but no official MCP server (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": "copper_crm_log_activity"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false, and the description reinforces the key point that it 'opens nothing by itself'. That explicitly tells the agent no browser session or side effect is started by this call, which is the main behavioral risk an agent could misjudge. It adds no information about the size or format of the returned guidance.

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

Conciseness3/5

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

The core instruction is front-loaded, but 'from ChatGPT, Claude or any AI agent' is filler, and the trailing note about Copper's REST API and the absence of an official MCP server (with an oddly dated 'checked 20 Oct 2026') does not help an agent invoke this tool.

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 parameters, no output schema, and annotations covering the safety profile, the description supplies exactly what is missing: what the tool returns (step-by-step UI instructions) and what must happen next (browser tools). Nothing needed for correct invocation is absent.

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; baseline for a parameterless tool applies. The description correctly does not invent parameter guidance.

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

Purpose4/5

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

The description makes the real behavior explicit: the tool returns step-by-step instructions for logging activity in Copper CRM (screens, buttons, fields) and performs no action itself. This resolves the ambiguity in the name 'log_activity', which could otherwise be read as a write operation. It distinguishes itself from the cotlet_browser_* siblings by naming them as the actual execution path.

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 two-step workflow: call this first for guidance, then execute with cotlet_browser_* tools. It does not explicitly state when to skip this tool or how it relates to the other copper_crm_* siblings (e.g., create_task), so the exclusion side is only implicit.

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

All Copper CRM 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?