Oli by Thommidhi

com.thommidhiPublished by thommidhi.comOfficial publisherv1.0.0Updated Oct 24, 2026

Your terms for brand work, brand offers, deals and video plans from Thommidhi, in your AI assistant.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP server from Thommidhi that brings your brand work, brand offers, deals and video plans into an AI assistant.

What you can do
  • Access your Thommidhi brand work, brand offers, deals and video plans from inside the assistant.
  • No tool list is published, so the exact actions available are not documented; expect read-oriented access to your own brand and deal records.
  • The server is a hosted remote endpoint, so there is nothing to install locally.
When to use it
Worth considering if you already use Thommidhi for brand work, offers, deals or video planning and want an assistant to work with that material directly instead of copying it across.
Requirements
A remote MCP endpoint at thommidhi.com over streamable HTTP. OAuth sign-in is required; no environment variables or headers are declared. A Thommidhi account with access to the relevant brand data is implied.
Before you install
OAuth grants the server access to your Thommidhi account data, so review the scopes on the consent screen. Brand, offer, deal and video plan information is shared with the assistant and the model behind it. No tool list is published, so what it can read or change cannot be verified in advance.

Installation

In SourceWeft

  1. Open Oli by Thommidhi 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.thommidhi%2Foli/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": {
    "oli-by-thommidhi": {
      "type": "http",
      "url": "https://thommidhi.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.0LatestOct 15, 2026

Score

56% 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

    Publish an icon in the registry entry.

  • 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.