Niche — Editorial Intelligence MCP Server

Find the stories worth writing about: discover emerging stories, rank the angle, draft from sources. The niche — editorial intelligence mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 6 defined tools rather than through you.

What it actually does

Most AI tools help you write. Niche helps you decide what's worth writing. It reads primary-source signal, discovers the stories before they're obvious, ranks the strongest angle, and turns that signal into publishable content, grounded in real sources and in your voice. The authority is earned, not faked: you sound like someone who did the research, because Niche did.

Its toolset

Everything the assistant can do here goes through one of these:

• niche_signal_scan — discover the stories worth writing about in a niche (returns a ranked story slate with provenance; poll niche_session_state)
• niche_intelligence_query — analyst-shaped query → ranked slate plus engine-grounded narratives and patterns ("the 10 biggest developments this week + 3 non-obvious
• niche_session_state — universal poll endpoint for a run's full state
• niche_angle_propose — surface the strongest angles worth publishing for a chosen story
• niche_draft_direct — skip research and draft straight from your own take or a URL, with optional per-claim grounding against the source
• niche_whoami — the full tool catalog (every tool name and the live count) plus account, plan, credit balance, the capability map (tools grouped by band and the

Configuration

You will need one environment variable: NICHE_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Niche — Editorial Intelligence's toolset — niche_signal_scan, niche_intelligence_query, niche_session_state and 3 more — is a fair guide to whether it matches your workflow. It is maintained by com.nicheangle; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the niche — editorial intelligence mcp server does with a few real requests.