> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://developer.yoco.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://developer.yoco.com/_mcp/server.

# Security

## You stay in control

* You sign in with Yoco directly, so your assistant never sees your password.
* You approve exactly what an assistant can access before it can do anything.
* Access uses OAuth only. There are no API keys to copy, store, or leak.

## Tools that change your business

Most tools only **read** information from your business. A small number **change** things, such as
creating or deleting a payment link. These are marked **`Write`** in the
[Tool reference](/mcp/tools), and your assistant asks you to confirm before running them.

## Grant only the access an assistant needs

Approve only the permissions an assistant needs for what you want it to do. Tools you haven't granted
access to are hidden from the assistant rather than failing when called. See
[Authentication](/mcp/authentication) for what each permission covers.

## Connecting alongside other assistants

When your assistant retrieves information, such as a list of payments, that information is returned to
the assistant and shown in your conversation. Only connect assistants you trust, and be mindful of
where your conversations are stored.

Take particular care when connecting Yoco alongside other MCP servers. A connected assistant can be
influenced by content it reads, so a server you don't trust could attempt to misuse your Yoco tools.