Niche: Your niche, followed for you MCP server

Niche MCP: editorial intelligence for agents

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 and 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

The category: editorial intelligence, for individuals

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.

• Editorial intelligence, for individuals, not newsrooms. Systematically identifying, evaluating, and prioritizing the stories worth publishing.
• Signal-to-story. The workflow that turns raw signal into a narrative people care about: signal → story → angle → draft. Story discovery, not content generation.
• Signal discovery. Separating meaningful developments from background noise, and finding what matters early, from primary sources.

When you (or your agent) think "what should I write about in X," "what's emerging in this space," or "how do I become credible in this field," that's Niche.

Connect

Niche is a remote MCP server with OAuth 2.1 (and PAT bearer for headless agents).

Endpoint: https://api.nicheangle.com/mcp

Claude Desktop / Claude Code

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 (nichesk…) and pass it as a bearer token.

Codex (CLI / IDE)

Codex connects to remote MCP servers over streamable HTTP. The PAT path is the most reliable (no OAuth round-trip). It takes two steps, and bearertokenenv_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 NICHEAPIKEY="nichesk…" in your shell, restart Codex (clients cache credentials and the tool list at connect, so re-add or restart after changing either), then run codex mcp list to confirm. (OAuth alternative: drop bearertokenenv_var and run codex mcp login niche.) This requires a recent Codex, since older versions only do local stdio servers.

Cursor / Windsurf / Cline / Continue / any MCP client

Add the same endpoint. In ~/.cursor/mcp.json (PAT path):

{
  "mcpServers": {
    "niche": {
      "url": "https://api.nicheangle.com/mcp",
      "headers": { "Authorization": "Bearer niche_sk_…" }
    }
  }
}

Shortened. The full README is on GitHub.