SEO Intellect MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Host/IP to bind for HTTP mode. | 0.0.0.0 |
| PORT | No | Port to bind for HTTP mode. | 3000 |
| MCP_TRANSPORT | No | Transport to use. stdio for local, http for remote Streamable HTTP. | stdio |
| MCP_ACCESS_TOKEN | No | Private access token required for static HTTP mode. | |
| MCP_ALLOWED_HOSTS | No | Comma-separated list of allowed hostnames for HTTP mode (e.g., mcp.example.com). | |
| MCP_HTTP_AUTH_MODE | No | Authentication mode for HTTP: byok (each caller supplies their own token) or static (one upstream token with a private access token). | |
| SEOINTELLECT_API_TOKEN | No | Your SEO Intellect API token. Required for local stdio mode and for static HTTP mode. |
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 |
|---|---|
| lsiB | Collect LSI unigrams and bigrams from search results. Upstream API tool: lsi. This operation may consume SEO Intellect account limits. |
| seo_textB | Measure competitor text sizes and collect page text from the SERP. Upstream API tool: seo-text. This operation may consume SEO Intellect account limits. |
| site_ageB | Find the first known indexing date for URLs. Upstream API tool: site-age. This operation may consume SEO Intellect account limits. |
| top_10B | Export search results for the supplied keywords. Upstream API tool: top-10. This operation may consume SEO Intellect account limits. |
| page_indexB | Check whether URLs are indexed in Yandex and Google. Upstream API tool: pageindex. This operation may consume SEO Intellect account limits. |
| clusteringA | Cluster a semantic core using search-result overlap. Upstream API tool: clustering. This operation may consume SEO Intellect account limits. |
| lemmaA | Lemmatize text and optionally build n-grams. Upstream API tool: lemma. This operation may consume SEO Intellect account limits. |
| positions_multiA | Check keyword positions for several sites or pages. Upstream API tool: positions-multi. This operation may consume SEO Intellect account limits. |
| headersB | Collect page headings from SERP competitors. Upstream API tool: headers. This operation may consume SEO Intellect account limits. |
| competitorsB | Find organic-search competitors for a keyword set. Upstream API tool: competitors. This operation may consume SEO Intellect account limits. |
| suggestB | Collect Yandex or Google search suggestions. Upstream API tool: suggest. This operation may consume SEO Intellect account limits. |
| sqiC | Fetch Yandex site quality index and related public site signals. Upstream API tool: sqi. This operation may consume SEO Intellect account limits. |
| keywords_checkerB | Check strict, lemmatized, and additional keyword occurrences in text. Upstream API tool: keywords-checker. This operation may consume SEO Intellect account limits. |
| overoptimization_filterB | Estimate possible Yandex text-filter or overoptimization risk. Upstream API tool: filter. This operation may consume SEO Intellect account limits. |
| positionsB | Check a site's positions and optional Wordstat/SERP signals. Upstream API tool: positions. This operation may consume SEO Intellect account limits. |
| link_checkerA | Check donor pages for links to acceptor URLs and optional indexation. Upstream API tool: linkchecker. This operation may consume SEO Intellect account limits. |
| relevant_pagesB | Find the most relevant site page for each keyword. Upstream API tool: relevant. This operation may consume SEO Intellect account limits. |
| wordstatB | Collect supported Wordstat frequencies for keywords. Upstream API tool: wordstat. This operation may consume SEO Intellect account limits. |
| semanticB | Analyze a domain's visible keyword semantics. Upstream API tool: semantic. This operation may consume SEO Intellect account limits. |
| site_scannerA | Crawl a website and return technical SEO findings. Upstream API tool: site-scanner. This operation may consume SEO Intellect account limits. |
| copywriter_briefB | Build a content brief from SERP competitors and keyword signals. Upstream API tool: copyrighters. This operation may consume SEO Intellect account limits. |
| text_analyzeC | Analyze text or competitor pages against a keyword set. Upstream API tool: text-analyze. This operation may consume SEO Intellect account limits. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/arseniigruzdev/engine-seointellect-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server