---
title: "Profiles & TOON output | Mesher docs: MCP connectors for AI agents"
url: https://mesher.sh/docs/profiles
description: "Use Mesher profiles to keep work and personal accounts apart and limit what each MCP app sees, and switch results to TOON to spend fewer tokens."
---

# Profiles & TOON output

Keep accounts apart, expose only what each app needs, and return results in fewer tokens.

## Profiles

A **profile** is a named set of connectors, each signed in to one account. Use profiles to keep accounts apart, such as a work and a personal Gmail side by side, and to decide what each MCP app may reach.

- Every user has the profile `default`. It can't be deleted.
- Names are lowercase: a letter, then up to 15 letters, digits or `-`.
- Each profile **opts into** installed connectors. A newly installed connector joins `default` only.
- Only the credential is per profile. The OAuth client and declared inputs are shared, so you [register an OAuth app](https://mesher.sh/docs/calltool#oauth-clients) once and sign in once per account.

Name the profile after an `@`; without one, `default` is used.

```text title="callTool"
gmail@work.tools auth
gmail@personal.tools auth
gmail@work.tools listMessages -q maxResults=5
gmail@personal.tools auth status
```

```sh
$ mesher gmail tools auth --profile work
$ MESHER_PROFILE=personal mesher gmail tools listMessages
```

### Choosing what a profile exposes

By default a profile exposes every tool, resource and prompt of its connectors. Open a connector, then **Configuration › Profiles**, and untick what the apps let into that profile shouldn't see. Hidden items don't show up in search or listings, and calling one is refused.

### Bundles

A bundle is a named group of connectors, such as *Google* for Gmail, Calendar and Drive. On a profile's page, a bundle's switch turns all of them on or off in one go.

## TOON output

Results are JSON by default. A profile can choose [TOON](https://github.com/toon-format/toon) instead: the same data in fewer tokens, which suits models.

```json
{"users":[
  {"id":1,"name":"Ada"},
  {"id":2,"name":"Bob"}
]}
```

```toon
users[2]{id,name}:
  1,Ada
  2,Bob
```

Where the format comes from, strongest first:

1. The call: `"format": "toon"` next to `command` over MCP, or `--format toon` (or `MESHER_FORMAT`) on the CLI.
2. The profile: **Results as JSON | TOON** on its page, or `PUT /api/v1/profiles/<name>/format`.
3. The host default: **Profiles › Default output format** in the setup, or `MESHER_DEFAULT_FORMAT=toon`.

- Only text blocks and JSON resources that hold a JSON object or array are rewritten. Anything that doesn't convert stays as it is, so a format never fails a call.
- Images, audio and base64 files are never changed.
- With TOON the result carries no `structuredContent`, so no JSON shape is advertised.

Last updated November 21, 2026 · [This page as Markdown](https://mesher.sh/docs/profiles.md) · [Full reference on GitHub](https://github.com/agentrq/mesher/blob/main/README.md)
