> For the complete documentation index, see [llms.txt](https://docs.moderncollections.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.moderncollections.io/mcp-servers/tools.md).

# Tools

The Modern Collections MCP server (`mc-api-mcp` console script, stdio transport) exposes the creditor-scoped REST API as **8 implemented tools**. All tool names are `snake_case`.

The server is scoped to a single creditor via its API key and reads config from the environment only (never from tool arguments, so the key stays out of MCP client config that may be logged):

* `MC_API_ENV` — `demo` | `prod`, **or**
* `MC_API_BASE_URL` — explicit base URL (overrides `MC_API_ENV`)
* `MC_API_KEY` — creditor API key, format `ca_<prefix>_<secret>` (never logged or printed; there is no production default env)

Money amounts are **positive decimal strings** (e.g. `"7500.00"`). Tool errors carry the API's opaque `detail` and HTTP status — never the API key.

## Tools

| Tool                  | Purpose                                                                                      | Parameters                                                                                                                                                                                                                                                  |
| --------------------- | -------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `placement_create`    | Place an overdue commercial invoice for collection; returns the new placement id and status. | **Required:** `company_name` (debtor company), `invoice_amount` (positive decimal string). **Optional:** `primary_email`, `primary_phone`, `primary_domain`, `state`, `city`, `zip_code`, `invoice_number`, `due_date`, `posture`, `notes`, `callback_url`. |
| `placement_status`    | Retrieve a placement (status, debtor, amounts, outreach state) by id.                        | **Required:** `placement_id`.                                                                                                                                                                                                                               |
| `placement_list`      | List placements, paginated.                                                                  | **Optional:** `page` (default `1`), `page_size` (default `25`), `status` (comma-separated filter).                                                                                                                                                          |
| `payment_record`      | Record a payment received against a placement.                                               | **Required:** `placement_id`, `amount` (positive decimal string).                                                                                                                                                                                           |
| `dispute_get`         | Inspect the dispute (if any) filed by the debtor on a placement.                             | **Required:** `placement_id`.                                                                                                                                                                                                                               |
| `dispute_acknowledge` | Acknowledge a dispute filed by a debtor, optionally attaching a note.                        | **Required:** `placement_id`. **Optional:** `note`.                                                                                                                                                                                                         |
| `audit_query`         | Read a placement's append-only audit trail (keyset-paginated).                               | **Required:** `placement_id`. **Optional:** `event_type`, `cursor`, `limit`.                                                                                                                                                                                |
| `analytics_summary`   | Return headline per-creditor analytics (recovered totals, status counts, rates).             | *(none)*                                                                                                                                                                                                                                                    |

New tools ship from time to time and are announced in the [change log](https://changelog.moderncollections.io).

## See also

* [MCP overview](/mcp-servers/overview.md)
* [REST API overview](/rest-api/overview.md)
* [Authentication](/getting-started/authentication.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.moderncollections.io/mcp-servers/tools.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.