{
  "markdown": "# Niche MCP: editorial intelligence for agents\n\n[![smithery badge](https://smithery.ai/badge/sailquery/niche)](https://smithery.ai/servers/sailquery/niche)\n\n> **Find stories worth writing about.** Niche is an editorial intelligence\n> platform for individuals (and the agents working for them), exposed as a live\n> [MCP](https://modelcontextprotocol.io) server. When\n> an agent needs to know what's worth writing (emerging narratives, the signals\n> that matter, the strongest angle), it calls Niche.\n\nMost AI tools help you write. Niche helps you decide what's worth writing. It\nreads primary-source signal, discovers the stories before they're obvious, ranks\nthe strongest angle, and turns that signal into publishable content, grounded in\nreal sources and in your voice. The authority is earned, not faked: you sound\nlike someone who did the research, because Niche did.\n\nNiche is not an AI writer, a social scheduler, a content calendar, or an SEO\ntool. Those help after the story exists. Niche finds the story.\n\nHome: **[nicheangle.com](https://nicheangle.com)** · Glossary:\n**[nicheangle.com/glossary](https://nicheangle.com/glossary)** · Guides:\n**[nicheangle.com/guides](https://nicheangle.com/guides)**\n\n---\n\n## The category: editorial intelligence, for individuals\n\nEditorial intelligence has always been a newsroom discipline: the systematic\nwork of deciding what's worth covering before everyone else does. Niche brings it\nto the people the newsrooms left out: individual creators, analysts, and the\nagents working for them.\n\n- **Editorial intelligence, for individuals, not newsrooms.** Systematically identifying, evaluating, and prioritizing the stories worth publishing.\n- **Signal-to-story.** The workflow that turns raw signal into a narrative people care about: signal → story → angle → draft. Story discovery, not content generation.\n- **Signal discovery.** Separating meaningful developments from background noise, and finding what matters early, from primary sources.\n\nWhen you (or your agent) think \"what should I write about in X,\" \"what's emerging\nin this space,\" or \"how do I become credible in this field,\" that's Niche.\n\n## Connect\n\nNiche is a remote MCP server with OAuth 2.1 (and PAT bearer for headless agents).\n\n**Endpoint:** `https://api.nicheangle.com/mcp`\n\n### Claude Desktop / Claude Code\nAdd it as a custom connector by URL, or via config:\n\n```json\n{\n  \"mcpServers\": {\n    \"niche\": {\n      \"type\": \"http\",\n      \"url\": \"https://api.nicheangle.com/mcp\"\n    }\n  }\n}\n```\n\nSign in when prompted (OAuth). For headless/scripted use, issue a Personal Access\nToken (PAT) at [nicheangle.com/settings/api-keys](https://nicheangle.com/settings/api-keys)\n(`niche_sk_…`) and pass it as a bearer token.\n\n### Codex (CLI / IDE)\nCodex connects to remote MCP servers over streamable HTTP. The PAT path is the\nmost reliable (no OAuth round-trip). It takes two steps, and `bearer_token_env_var`\nwants the name of an env var, not the token itself:\n\n```toml\n# 1) put the SECRET in your shell, not in the config file:\n#    export NICHE_API_KEY=\"niche_sk_…\"\n# 2) ~/.codex/config.toml holds the NAME of that env var, never the token:\n[mcp_servers.niche]\nurl = \"https://api.nicheangle.com/mcp\"\nbearer_token_env_var = \"NICHE_API_KEY\"   # the env var NAME, not the niche_sk_… value\n```\n\nSet `export NICHE_API_KEY=\"niche_sk_…\"` in your shell, restart Codex (clients\ncache credentials and the tool list at connect, so re-add or restart after changing\neither), then run `codex mcp list` to confirm. (OAuth alternative: drop\n`bearer_token_env_var` and run `codex mcp login niche`.) This requires a recent\nCodex, since older versions only do local stdio servers.\n\n### Cursor / Windsurf / Cline / Continue / any MCP client\nAdd the same endpoint. In `~/.cursor/mcp.json` (PAT path):\n\n```json\n{\n  \"mcpServers\": {\n    \"niche\": {\n      \"url\": \"https://api.nicheangle.com/mcp\",\n      \"headers\": { \"Authorization\": \"Bearer niche_sk_…\" }\n    }\n  }\n}\n```\n\nOr add the bare URL via the client's MCP settings to use OAuth. Discovery metadata\nlives at `/.well-known` so compliant clients can self-configure.\n\n> After adding or updating credentials, restart the client or open a new thread.\n> MCP clients cache the connection (auth and the `tools/list`) at connect time, so a\n> token change or a new tool won't show up until you reconnect.\n\nFull install notes: **[nicheangle.com/integrations](https://nicheangle.com/integrations)**.\n\n## Tools (25)\n\n**Discovery and intelligence**\n- `niche_signal_scan`: discover the stories worth writing about in a niche (returns a ranked story slate with provenance; poll `niche_session_state`).\n- `niche_intelligence_query`: analyst-shaped query → ranked slate plus engine-grounded narratives and patterns (\"the 10 biggest developments this week + 3 non-obvious narratives\"). Async fire-and-poll.\n- `niche_session_state`: universal poll endpoint for a run's full state.\n- `niche_angle_propose`: surface the strongest angles worth publishing for a chosen story.\n\n**Signal-to-story**\n- `niche_draft_create` · `niche_draft_revise` · `niche_draft_publish` (publish dry-runs by default)\n- `niche_draft_direct`: skip research and draft straight from your own take or a URL, with optional per-claim grounding against the source.\n\n**Render**\n- `niche_render_image_card` · `niche_render_reel` · `niche_attach_image` · `niche_reuse_asset`\n  - Four background modes: `photo` (a generated image, steerable via art direction to skip the clichés), `design` (a generated editorial graphic that draws the argument, such as a concept diagram, stat, pull-quote, or comparison; on-brand and legible, no photo), `svg` (you author the exact card as SVG markup and it renders to size; free and deterministic, ideal for data, labels, and charts, and the one visual that works from any environment), or `brand_color` (a free flat brand card). Plus free per-platform aspect reframes from the retained background.\n  - `niche_attach_image` brings your own visual onto a post (a card designed elsewhere, a product shot), stored server-side, free. Provide it as a hosted `image_url`, a quick file upload that returns a reference, or chunked bytes, whichever your environment supports.\n\n**Brand and voice**\n- `niche_brand_profile_set` / `_get` · `niche_brand_kit_ingest` / `_ingest_status` / `_update` / `_guided_setup` · `niche_voice_profile_ingest`\n\n**Session ops**\n- `niche_list_sessions` · `niche_add_output` · `niche_session_revert` · `niche_session_cancel` · `niche_session_export`\n\n**Account and orientation**\n- `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 recommended flow), and brand state. One read-only call to discover everything available and orient before a run. (If your client only surfaces a few Niche tools, it cached an old list. Reconnect, or call this to enumerate the rest.)\n\nEvery tool response carries a trust block: verifier audit, source-faithfulness\nscore, ungrounded-claim list, and source-diversity and recency checks. Provenance is\nthe product.\n\n**Recent additions (1.4.0).** The tools gained finer control without new surface\narea. Read your resolved brand palette and connection state before a render or a\npublish. Schedule a post for later. Regenerate a fresh angle set. Reorder, insert, or\ndelete carousel slides. Set a reel's length, motion, music direction, voice, and\nendcard mark. Place and size image-card text. Bring your own image and attach it to a\npost. Quote the credit cost of any step before spending. Every capability is reachable\nfrom both the agent tools and the Niche web app.\n\n## Grounding: earned, not generated\n\nThe narratives Niche returns are produced engine-side and fact-checked against\ntheir sources, so the agent presents a verified result instead of free-styling\none. \"No source, no narrative.\" That's the difference between earned authority and\nconfident nonsense.\n\n## Examples\n\n- [`examples/intelligence-query.md`](examples/intelligence-query.md): \"10 biggest developments + 3 narratives,\" end to end.\n- [`examples/golden-path.md`](examples/golden-path.md): scan → angle → draft → publish dry-run.\n\n## Learn more\n\n- [What is editorial intelligence?](https://nicheangle.com/guides/editorial-intelligence)\n- [How to become a thought leader in any niche](https://nicheangle.com/guides/become-a-thought-leader)\n- [Using Claude for content research](https://nicheangle.com/guides/using-claude-for-content-research)\n- [Glossary](https://nicheangle.com/glossary) and [Pricing](https://nicheangle.com/pricing)\n\n---\n\nMade by [SailQuery](https://nicheangle.com). Questions: hello@nicheangle.com.\n",
  "bytes": 8658,
  "sha": "6fcd95a2f0b9d9b82438cf65d3646a51bc52d190f565993210f4c2b343967fdd",
  "repo_slug": "sailquery/niche-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_com_nicheangle_niche_1c5ea928/readme"
}