Server data from the Official MCP Registry
Find the stories worth writing about: discover emerging stories, rank the angle, draft from sources.
Find the stories worth writing about: discover emerging stories, rank the angle, draft from sources.
Remote endpoints: streamable-http: https://api.nicheangle.com/mcp
Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.
Endpoint verified · Requires authentication · 1 issue found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Remote Plugin
No local installation needed. Your AI client connects to the remote endpoint directly.
Add this to your MCP configuration to connect:
{
"mcpServers": {
"com-nicheangle-niche": {
"url": "https://api.nicheangle.com/mcp"
}
}
}From the project's GitHub README.
Find stories worth writing about. Niche is an editorial intelligence platform for individuals (and the agents working for them), exposed as a live MCP server. When an agent needs to know what's worth writing — emerging narratives, the signals that matter, the strongest angle — it calls Niche.
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, in your voice. The authority is earned, not faked: you sound like someone who did the research, because Niche did.
Niche is not an AI writer, a social scheduler, a content calendar, or an SEO tool. Those help after the story exists. Niche finds the story.
Home: nicheangle.com · Glossary: nicheangle.com/glossary · Guides: nicheangle.com/guides
Editorial intelligence has always been a newsroom discipline — the systematic work of deciding what's worth covering before everyone else does. Niche brings it to the people the newsrooms left out: individual creators, analysts, and the agents working for them.
When you (or your agent) think "what should I write about in X," "what's emerging in this space," "how do I become credible in this field" — that's Niche.
Niche is a remote MCP server with OAuth 2.1 (and PAT bearer for headless agents).
Endpoint: https://api.nicheangle.com/mcp
Add it as a custom connector by URL, or via config:
{
"mcpServers": {
"niche": {
"type": "http",
"url": "https://api.nicheangle.com/mcp"
}
}
}
Sign in when prompted (OAuth). For headless/scripted use, issue a Personal Access
Token (PAT) at nicheangle.com/settings/api-keys
(niche_sk_…) and pass it as a bearer token.
Codex connects to remote MCP servers over streamable HTTP. The PAT path is the
most reliable (no OAuth round-trip). Two steps — and bearer_token_env_var wants
the name of an env var, NOT the token itself:
# 1) put the SECRET in your shell — not in the config file:
# export NICHE_API_KEY="niche_sk_…"
# 2) ~/.codex/config.toml holds the NAME of that env var, never the token:
[mcp_servers.niche]
url = "https://api.nicheangle.com/mcp"
bearer_token_env_var = "NICHE_API_KEY" # the env var NAME — not the niche_sk_… value
Set export NICHE_API_KEY="niche_sk_…" in your shell, restart Codex (clients
cache credentials + the tool list at connect — re-add or restart after changing
either), then codex mcp list to confirm. (OAuth alternative: drop
bearer_token_env_var and run codex mcp login niche.) Requires a recent Codex —
older versions only do local stdio servers.
Add the same endpoint. In ~/.cursor/mcp.json (PAT path):
{
"mcpServers": {
"niche": {
"url": "https://api.nicheangle.com/mcp",
"headers": { "Authorization": "Bearer niche_sk_…" }
}
}
}
Or add the bare URL via the client's MCP settings to use OAuth. Discovery metadata
lives at /.well-known so compliant clients can self-configure.
After adding or updating credentials, restart the client / open a new thread. MCP clients cache the connection (auth + the
tools/list) at connect time, so a token change or a new tool won't show up until you reconnect.
Full install notes: nicheangle.com/integrations.
Discovery + intelligence
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/patterns ("the 10 biggest developments this week + 3 non-obvious narratives"). Async fire-and-poll.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.Signal-to-story
niche_draft_create · niche_draft_revise · niche_draft_publish (publish dry-runs by default)niche_draft_direct — skip research and draft straight from your own take or a URL.Render
niche_render_image_card · niche_render_reel · niche_attach_image · niche_reuse_assetBrand + voice
niche_brand_profile_set / _get · niche_brand_kit_ingest / _ingest_status / _update / _guided_setup · niche_voice_profile_ingestSession ops
niche_list_sessions · niche_add_output · niche_session_revert · niche_session_cancel · niche_session_exportAccount + orientation
niche_whoami — account + plan + credit balance, the server's live tool count, the capability map (tools grouped by band + the recommended flow), and the brand state — one read-only call to orient before a run.Every tool response carries a trust block — verifier audit, source-faithfulness score, ungrounded-claim list, source-diversity + recency checks. Provenance is the product.
The narratives Niche returns are produced engine-side and fact-checked against their sources — the agent presents a verified result instead of free-styling one. "No source, no narrative." That's the difference between earned authority and confident nonsense.
examples/intelligence-query.md — "10 biggest developments + 3 narratives," end to end.examples/golden-path.md — scan → angle → draft → publish dry-run.Made by SailQuery. Questions: hello@nicheangle.com.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.