MySampark

io.github.utsav12322Published by GitHub account utsav12322v1.0.1Updated Oct 24, 2026

Manage MySampark products and social media campaigns across Facebook, Instagram, and more.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

MySampark is a remote MCP server that lets an assistant manage MySampark products and social media campaigns across Facebook, Instagram and other channels.

What you can do
Manage MySampark products and social media campaigns across Facebook, Instagram and other channels, as described in the registry entry. No individual tools are listed in the manifest, so the exact actions available are not documented here. Access is through a remote endpoint with a bearer token tied to a MySampark account.
When to use it
Worth considering if you already use MySampark and want an AI assistant to work with your products and social media campaigns from within a conversation.
Requirements
A remote MCP endpoint at mcp.mysampark.com over streamable HTTP. A MySampark account and a bearer token, generated by logging in and calling the token API, supplied in the Authorization header.
Before you install
The server requires a bearer token in the Authorization header; treat it as a secret and do not share it. It is described as managing products and campaigns, which likely includes changing or publishing content on connected social channels, so review actions before they run.

Installation

In SourceWeft

  1. Open MySampark in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/io.github.utsav12322%2Fmysampark-mcp/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.

{
  "mcpServers": {
    "mysampark": {
      "type": "http",
      "url": "https://mcp.mysampark.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.