thenichegap-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| THENICHEGAP_API_KEY | Yes | Your TheNicheGap API key. Generate it in the TheNicheGap Dashboard under the Developer section. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_niche_gapB | Analyze an SEO keyword to find search intent, industry must-haves, and content gaps using real SERP data from TheNicheGap. Use this to help craft highly differentiated articles. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
There is only one tool, so there is no overlap or misselection risk between tools. Its purpose is explicit and distinct.
The single tool follows a clear snake_case verb_noun naming pattern. With no other tools, there are no inconsistent conventions present.
One tool is borderline thin for a server surface, though it may be acceptable for a tightly scoped niche-analysis endpoint. The scale treats 1-2 tools as borderline.
The tool covers the core described operation of analyzing an SEO keyword for intent and content gaps. Minor gaps remain, such as batch analysis or adjacent keyword-discovery operations, but the primary use case is covered.