Destinations

Destinations is where curated knowledge goes back out. It carries live delivery only, in three tabs.

Knowledge chat

A chat surface your team can open in a browser, answering from the knowledge base and citing what it used.

New knowledge chat asks for a destination name, a URL slug, the assistant title readers see, and a welcome message. Then pick the tools it may use for each answer: Search documents, Verified facts, and Approved answers. A chat scoped to search alone never serves an approved answer.

It starts as a Draft. Deploy takes it Live, and the destination URL is then readable on the card and openable from the page. Save a configuration change and deploy again to push it.

MCP servers

For an agent or an editor that speaks MCP. Create a server, choose the capabilities it exposes (search, facts, glossary, chat, lineage, and approved answers), and Mari issues a bearer token scoped to exactly those capabilities.

The token is shown once, with a connection snippet beside it to paste into the client. Copy it then, because it is not shown again.

Bots

Two push-into-Mari integrations, each with an honest status card. "Waiting for first event" is a real state and says so rather than claiming success.

Slack. Create a Slack app from the manifest the drawer hands you, then save the bot token, the app token, and the signing secret. Test connection calls Slack's own auth.test and reports what came back, so a bad token fails here rather than the first time somebody asks a question.

GitHub. In the repository's Settings, Webhooks, Add webhook, use the payload URL the drawer shows, choose Let me select individual events, and tick Pushes, Issue comments, and Pull requests. Generate a webhook secret and save it so Mari can verify deliveries.

That one webhook does two jobs. A push re-syncs the repository immediately. And it carries the fact-check bot: mention @mari in a pull request or an issue comment, or add the mari:factcheck label, and Mari checks the change against what it knows and replies in the thread.

Every surface here answers in the same voice, because the dock, a public knowledge chat, and the Slack bot all read one chat style guide. Slack gets mrkdwn rather than Markdown, which is the only difference that shows.

Not here

The documentation site you are reading is built from the mari-docs repo, not from the console. Destinations carries live delivery mechanisms only.