PushPress MCP Server and API by Cotlet

Check in member in PushPress

pushpress_check_in_member

Read-onlyIdempotent

Check in member in the user's own PushPress account from ChatGPT, Claude or any AI agent. Returns how to do it in PushPress step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's PushPress Cloud Browser. PushPress's official API: PushPress has a Platform API and an SDK that doubles as a local MCP server, both using an API key from Settings > Security & Access, but they are mostly read-only beyond creating customers and invitations (checked 11 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": "pushpress_check_in_member"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses that no action is opened automatically, that the return value is procedural guidance with screens, buttons, and fields, and that the actual write must be done through the browser tools. It also adds useful context about the official API's limited scope.

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 description is front-loaded with the purpose and the critical no-side-effect clarification. The final sentence about the official API is relevant but somewhat verbose, and the opening 'from ChatGPT, Claude or any AI agent' is boilerplate.

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?

For a zero-parameter, read-only guidance tool with no output schema, the description supplies the key operational facts: what it returns, that it does not act, and which tools to use next. An agent should be able to use it correctly without additional schema detail.

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 has zero input parameters, so there is no schema parameter semantics to supplement; the description appropriately does not invent parameters. The baseline for a zero-parameter tool is 4.

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 provides a specific verb and resource (check in member in PushPress) and immediately clarifies that the tool returns step-by-step instructions rather than performing the action. That distinction separates it from the cotlet_browser_* action tools, though the name and title still carry some risk of being read as a direct check-in action.

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 explicitly instructs the agent to get the procedure here and then execute it with cotlet_browser_* tools in the user's PushPress Cloud Browser, and it rules out relying on the official PushPress API because it is mostly read-only. It does not name a precise browser tool sequence, but the guidance is actionable.

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

All PushPress 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?