OmniSignal

ai.omnisignalPublished by omnisignal.aiOfficial publisherv1.0.0Updated Oct 24, 2026

Live market intelligence & AI content strategy: trends, competitor moves, content calendar.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

OmniSignal is a remote MCP server that gives an assistant live market intelligence, competitor analysis, and AI-generated social content calendars for a brand.

What you can do
It exposes 38 tools covering onboarding, brand profile and strategy reads, strategy generation, market signals, content calendar management, and raw social data pulls. The assistant can scan a niche for trends and competitor moves, produce sourced briefs and gap analyses, build and edit multi-week content calendars, create A/B hook variants, and export calendars as CSV, ICS, or JSON. Some tools run asynchronously and return a job id to poll.
When to use it
Worth adding when an assistant is used for ongoing social content planning, competitive research, or weekly market briefs for a specific brand, and you want fresh data rather than a model's stale training snapshot. Less useful for one-off questions or brands with no social presence to track.
Requirements
A remote streamable HTTP endpoint at reachable over the network. An OmniSignal account and an API key created in the dashboard, sent as the Authorization header in the form Bearer omni_sk_... . No local runtime or package install is needed; the Claude Code plugin reads the key from the OMNISIGNAL_API_KEY environment variable.
Before you install
The Authorization header carries a secret API key with read and generate scopes; keys are shown once and can be revoked. Paid tools consume credits metered to Stripe, so calls spend real money, and monthly packages auto-bill overage in round-up blocks. The server collects brand profile data and social handles, and data pulls query LinkedIn, Twitter, and Instagram content.

Installation

In SourceWeft

  1. Open OmniSignal 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/ai.omnisignal%2Fomnisignal/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": {
    "omnisignal": {
      "type": "http",
      "url": "https://mcp.omnisignal.ai/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

OmniSignal MCP Server

[omnisignal-mcp MCP server]

Live market intelligence and AI content strategy for your brand — straight into your AI assistant.

OmniSignal turns your brand profile into a data-driven social content operation: it collects fresh data from your niche (competitors, trends, audience), generates a multi-week content calendar, and surfaces daily signals (trends, competitor moves, opportunities). The entire backend is exposed as a remote MCP (Model Context Protocol) server — 38 tools your agent can call natively from Claude Code, Claude Desktop, Cursor, or any MCP-compatible client.

ChatGPT and Claude are trained on stale snapshots. Same model, same prompt — the only difference is whether your agent can see this week.

Server details

TransportStreamable HTTP (single endpoint, stateless)
Server URLhttps://mcp.omnisignal.ai/mcp
AuthAuthorization: Bearer omni_sk_... (API key from the dashboard)
Tools38 (onboarding, strategy, signals, calendar, data, credits)
DocsLive API docs · Markdown for agents
Websiteomnisignal.ai

Quickstart

1. Get an API key

Sign up at app.omnisignal.ai → Profile → MCP / API access → create a key (omni_sk_..., shown once). Keys carry read + generate scopes, up to 10 active keys, revocable anytime. New accounts get 50 free starter credits.

2. Connect your client

Claude Code (CLI):

bash
claude mcp add --transport http omnisignal \  https://mcp.omnisignal.ai/mcp \  --header "Authorization: Bearer omni_sk_YOUR_KEY_HERE"

Claude Code (plugin, from this repo):

/plugin marketplace add omnisignal-ai/omnisignal-mcp/plugin install omnisignal@omnisignal

Then set the OMNISIGNAL_API_KEY environment variable to your key — the plugin wires the header for you.

Claude Desktop (claude_desktop_config.json):

json
{  "mcpServers": {    "omnisignal": {      "type": "streamable-http",      "url": "https://mcp.omnisignal.ai/mcp",      "headers": { "Authorization": "Bearer omni_sk_YOUR_KEY_HERE" }    }  }}

Cursor (~/.cursor/mcp.json):

json
{  "mcpServers": {    "omnisignal": {      "type": "streamable-http",      "url": "https://mcp.omnisignal.ai/mcp",      "headers": { "Authorization": "Bearer omni_sk_YOUR_KEY_HERE" }    }  }}

Any MCP client: POST to the server URL with header Authorization: Bearer omni_sk_YOUR_KEY_HERE and Accept: application/json, text/event-stream.

3. Let the agent onboard you

Say: "Set up my OmniSignal workspace." The server ships with a built-in onboarding playbook — the agent checks readiness, collects your brand profile conversationally, analyzes your website, and kicks off your first strategy generation.

What you can do with it

  • Monday market brief — "What's moving in my market this week?" → fresh scan + a sourced brief of trends, competitor moves, and opportunities.
  • Battlecards / competitive response — sourced gap analysis of what a competitor covers that you don't, with immediate actions.
  • Weekly planning — walk this week's content calendar, playbooks included; A/B hook variants; mark posts published.
  • Export anywhere — the calendar as CSV / ICS / JSON into Notion, Google Calendar, or a scheduler.
  • Deep data pulls — fresh LinkedIn / Twitter / Instagram posts on any query when the agent needs raw material.

Tool overview (38 tools)

Free tools are always free; paid tools require the generate scope and credits. Agents are instructed (via the server's built-in instructions) to check credits_get_pricing / credits_get_balance before running paid calls.

GroupToolsPrice
Onboardingonboarding_get_readiness, onboarding_update_profile, onboarding_update_goals, onboarding_update_social_handles, onboarding_update_brand_voice, onboarding_update_content, onboarding_connect_platform, onboarding_analyze_websiteFree
Profile & strategy readsprofile_get, strategy_get_latest, strategy_list, strategy_get_status, strategy_get_swot, strategy_get_themesFree
Strategy generationstrategy_generate (async), strategy_analyze_post_idea, strategy_competitor_gap150 / 8 / 12 cr
Signalssignals_scan (async) + signals_scan_status (free), signals_list, signals_generate, signals_dismiss, signals_snooze, sources_list (free), sources_discover25 cr scan, 5 cr/list window, 10 cr generate/discover
Calendarcalendar_get_day, calendar_get_week, calendar_get_upcoming (free), calendar_get_post, calendar_search_posts, calendar_update_post (free), calendar_create_variants, calendar_export5 cr day / 15 cr week / 3 cr post / 3 cr search / 8 cr variants / 5 cr export
Datadata_summary (free), data_collect, data_points_list2–10 cr
Credits metacredits_get_balance, credits_get_pricingFree

Design notes: async jobs (strategy_generate, signals_scan) return a job id to poll and auto-refund on failure; responses are chunked for LLM context (signal windows of 10, calendar day-by-day with a week bulk discount); paid mutations are idempotent; per-user daily spend cap.

Pricing

1 credit = $0.15, metered to Stripe on every paid call.

PackagePrice/moCreditsEffective $/cr
Starter$25250$0.10
Creator$49550$0.089
Pro$991,200$0.083
Team$1992,600$0.077
PAYG—$0.15/cr, billed daily in arrears$0.15
  • 50 free starter credits on the free/PAYG tier.
  • Monthly packages never hard-stop: overage auto-bills in round-up blocks at the package rate.
  • Any MCP package also unlocks the full OmniSignal dashboard on the same account.

Links

  • Product site: omnisignal.ai
  • Dashboard: app.omnisignal.ai
  • Live MCP docs: /mcp/docs
  • This repo also contains server.json (Official MCP Registry manifest) and a Claude Code plugin marketplace manifest (.claude-plugin/marketplace.json).

License

MIT — see LICENSE. The hosted OmniSignal service itself is commercial; this repo contains listing metadata and documentation only.

Source: README.md at commit 729f1c6

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.0LatestSep 16, 2026

Score

85% 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
  • License10 pts