# MCP server

> Give an AI assistant bymundi's tools — what the MCP server offers and how it behaves.

The bymundi MCP server lets an AI assistant work in bymundi the way a staff member would: read and build itineraries, plan days, quote, manage documents and passengers. It speaks the Model Context Protocol over **Streamable HTTP** at:

```
https://api.bymundi.com/mcp
```

It authenticates with the same [API keys](https://api.bymundi.com/docs/guides/authentication.md) as REST: `Authorization: Bearer bym_live_…`. [Connect your client](https://api.bymundi.com/docs/mcp/clients.md).

## What the model gets

- **Tools filtered by the key.** A key with `quotes` off is offered no quote tools. The [full list](https://api.bymundi.com/docs/mcp/tools.md).
- **Instructions** that explain how trips, itineraries and the catalog fit together, sent when the client connects.
- **Refs.** `get_itinerary` gives each block a short `ref`; tools accept refs or ids.
- **Dry run.** Writes that support it take `dryRun: true` to preview the effect.
- **Undo.** An undoable write names a change id; `undo_change` reverts it (and refuses if the block was edited since).
- **Hints.** Every tool declares whether it is read-only, destructive, idempotent, or reaches people outside bymundi (sending a traveler an email).

Changes made over MCP are tagged as made by the assistant and appear in the app's activity list with Undo, like API changes.