Oviond

com.oviondPublished by oviond.comOfficial publisherv1.0.0Updated Oct 24, 2026

Build branded agency client reports from 100+ marketing datasources.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Oviond is a remote MCP server that lets an assistant build branded client reports for agencies from more than 100 marketing data sources.

What you can do
Connect an assistant to Oviond's reporting platform for agencies, which draws on over 100 marketing data sources. From the description, the assistant can work with that data to assemble client reports carrying the agency's own branding. No individual tools are listed, so the exact actions available are not documented here.
When to use it
Worth considering for marketing agencies or similar teams that regularly produce branded client reports and want an assistant to help assemble them from many marketing data sources.
Requirements
A remote MCP connection to the Oviond endpoint, with OAuth sign-in required. An Oviond account and access to the relevant marketing data sources are implied by the service. No environment variables or headers are declared.
Before you install
Access is granted through OAuth, so the assistant acts within the connected Oviond account and its marketing data. Reports may contain client data from third-party marketing sources; check what is shared and who can see generated reports before connecting.

Installation

In SourceWeft

  1. Open Oviond in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.oviond%2Foviond/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "oviond": {
      "type": "http",
      "url": "https://api.oviond.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 18, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.