Splark

com.splarkPublished by splark.comOfficial publisherv1.0.2Updated Oct 24, 2026

The ask-and-answer video format: send a question, get a short one-take video answer, captioned.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Splark is a remote MCP server that turns a question into a short, captioned one-take video answer.

What you can do
  • Send a question and receive a short one-take video answer.
  • Get the answer captioned, in the ask-and-answer video format the service describes.
  • No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Useful when you want answers delivered as short captioned video clips rather than text, for example for social-style or presentation content generated from a question.
Requirements
Remote streamable HTTP endpoint at api.splark.com; no local package. Requires OAuth authentication with an Authorization header carrying a Bearer API key. A key is minted in the Splark dashboard, or a free account (20 shorts/month) can be created by posting an email to the signup endpoint.
Before you install
The Authorization header carries a live API key (sk_live_ prefix), so treat it as a secret and avoid exposing it in logs or shared configs. Usage is metered by a monthly quota on the free tier, and paid plans may be needed beyond it. Questions and account email are sent to a third-party service.

Installation

In SourceWeft

  1. Open Splark 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.splark%2Fsplark/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": {
    "splark": {
      "type": "http",
      "url": "https://api.splark.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.2LatestSep 16, 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.