Skip to main content
The Oviond MCP server exposes 179 tools across 29 groups. Most map to a single REST operation; a few chain several. Tool names are verb-first — create_client, list_projects, add_data_widget — so an agent can guess the right one from the action.

Tool catalog

Account

Activity

API keys

Archive

Assets

Automations

Billing

Branding

Calculated metrics

Clients

Company

Custom data

Datasources

Domains

Email

Exports

Folders

Goals

Media

Notifications

Pages

PDF

Projects

Templates

Themes

Users

Widgets

Workflows

🔒 = flagged destructive, so a client can prompt before running it.

Conventions

  • Identifiers — calls return IDs the agent chains into later calls. It is instructed to refer to records by name in chat, never by ID.
  • Multi-tenancy — every call is scoped to the authenticated account. You never pass an account_id.
  • Discovery firstdatasources, then describe_datasource, before configuring a data widget: the second returns that datasource’s data views, metrics, dimensions and required settings.
  • Metrics and dimensions are objects — pass [{ "value": "clicks" }], not ["clicks"]. Only value is required; Oviond fills in the rest from the catalog. The same shape is used by the widget, goal and calculated-metric tools.
  • Data is fetched server-side after a widget is written. refresh_widgets or refresh_project force it.

Reference

Each tool wraps an Oviond REST operation. For exact parameters and response shapes, see the API Reference.