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