mcpField
O
OmniSignal

OmniSignal

Remote
omnisignal.aiBusiness & Marketing3Updated 12w ago

About OmniSignal

OmniSignal is a remote market-intelligence and content-planning service for brands, exposing research and publishing-planning workflows to AI agents. Its tools cover onboarding, strategy, market signals, content calendars, and data collection.

Key features

  1. 01Brand onboarding and profile management
  2. 02Market and competitor signal scans
  3. 03Content strategy and post-idea analysis
  4. 04Content calendar management and export
  5. 05Social data collection

Use cases

  1. 01Preparing a sourced weekly market brief
  2. 02Comparing competitor coverage and planning responses
  3. 03Reviewing and updating a weekly content calendar
  4. 04Exporting a calendar as CSV, ICS, or JSON

MCP support

Exposes 38 tools through a remote MCP server using Streamable HTTP. MCP clients can use them for onboarding, strategy generation, signals, calendar operations, data collection, and credit information.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://mcp.omnisignal.ai/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

All endpoints
Streamable HTTPhttps://mcp.omnisignal.ai/mcpAuth required

Tools

Details

From the project 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):

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):

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

Cursor (~/.cursor/mcp.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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.