Back

Tools

Connect anything. Custom APIs and MCP, in minutes

Pleep can call any API you have. Or any tool that supports MCP. Define a custom tool once, the agent uses it forever

Try in 3 minutes

Custom tools

Define a tool. The agent uses it.

Hand the agent a function. Pleep calls it when context demands. No prompt engineering, no tool selection logic, no retry plumbing

Order status lookup

Agent gets an order ID from the lead, hits your DB, replies with shipping status and ETA

Loyalty tier check

Agent verifies a returning customer's tier in your CRM, applies the right pricing without asking

Booking system

Agent reads availability from your calendar API, books the slot, sends the confirmation

MCP support

Plug any MCP server in one click.

Pleep speaks Model Context Protocol natively. If a tool exposes an MCP server, the agent can use it. No custom code on your side

  • Native MCP server registration
  • Auto-discover tools, resources, prompts
  • Per-agent scoping: which tools each agent can use
  • Audit log of every tool call, every argument

Trust & safety

The agent only uses tools you approve.

Each tool is scoped to the agents that can call it. Every invocation is logged with arguments and result. Tools that mutate state require explicit approval rules — like a maximum refund amount or an allowed customer tier

  • Per-tool, per-agent allowlist
  • Approval rules for state-mutating calls
  • Full audit trail of every invocation
  • Rollback on failed tool calls
FAQ

Frequently Asked Questions

A custom tool is a function you wire up directly to Pleep — usually a single API endpoint. An MCP server can expose dozens of tools, resources, and prompts at once and is the standard way modern tooling is shared. Pleep supports both.

Tool invocation adds a few hundred milliseconds round trip plus your endpoint's latency. The agent decides whether to call a tool based on conversation context — if your endpoint replies fast, the customer doesn't notice.

Only if you explicitly grant that scope. Tools are read-only by default. Mutating tools (like 'apply refund' or 'cancel booking') require an approval rule with conditions: max amount, customer tier, time of day. The agent can't bypass these.

For an MCP server, no — most popular tools have an MCP integration you can plug in. For a fully custom tool, you'll need to expose an HTTP endpoint and define the schema. Templates are provided for common patterns.