seolyticize
Supports onboarding Next.js sites by generating the Seolyticize Analytics component with its CSP origins and an app/sitemap.ts file, alongside IndexNow and verification files.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
seolyticize
Every Seolyticize tool from a terminal or a script. Built on
@seolyticize/sdk; tools are discovered from the API at runtime, so a
tool added to the platform today is a command today, without a new CLI release.
Install
npm install -g @seolyticize/cli
seolyticize --helpRelated MCP server: mcp-oauth-proxy
Log in
# Piped, so the key never lands in shell history:
printf '%s' "$KEY" | seolyticize login
# Or interactively (the key is not echoed):
seolyticize login
# Another instance:
seolyticize login --base-url https://seolyticize.example.comThe key is checked against the API before it is stored, in
~/.config/seolyticize/config.json (or $XDG_CONFIG_HOME/seolyticize/config.json), with
permissions 0600 on the file and 0700 on its directory.
SEOLYTICIZE_API_KEY and SEOLYTICIZE_BASE_URL override the stored values, which is how CI
should provide them.
seolyticize whoami # role, reach (agency-wide or one client), tool count
seolyticize logoutUse
seolyticize tools # what this key may call
seolyticize describe get_top_searches # a tool's options
seolyticize call get_top_searches --market=uk --since=2026-09-01 --limit=20
seolyticize get_top_searches --market=uk --since=2026-09-01 # same, without "call"
# Input as JSON, inline, from a file, or from stdin; options apply on top:
seolyticize call get_keyword_gap --input '{"clientId":"c1","competitorDomains":["a.com"]}'
seolyticize call get_keyword_gap --file gap.json
cat gap.json | seolyticize call get_keyword_gap --file -Options are typed from the tool's schema: numbers and booleans are converted, arrays take
repeated options or commas (--domains=a.com,b.com), objects take JSON, null is null
where the schema allows it, and --client-id is accepted for clientId.
Shortcuts
seolyticize clients # list_clients
seolyticize rank <trackerId> --client <id> # get_rank_summary
seolyticize alerts --client <id> [--since 2026-10-01T00:00:00Z] # last 7 days by defaultOnboard a site from its repo
seolyticize init --domain example.com --framework nextjs [--dry-run] [--force] [--dir .] [--public public]Calls onboard_site and writes what it returns: the IndexNow and verification files under public/, the robots source, and for Next.js app/seolyticize.tsx (the <Analytics> component and its CSP origins) and app/sitemap.ts. Files already there are kept unless --force; --dry-run lists them.
seolyticize verify --site example.com # or --client <id>; exit 10 on a failed check, so CI can stopPrints one line per item not done, with its code, detail and next call.
Output
Human-readable tables by default. Scripts should pass --json, which prints the tool's
result exactly as the API returned it under data:
seolyticize clients --json | jq -r '.clients[].id'Exit codes
Stable, so scripts can branch on them:
Code | Meaning |
0 | success |
1 | unexpected error |
2 | usage error (bad command, option or JSON) |
3 | authentication failed (missing, unknown, revoked) |
4 | not permitted (role or client scope) |
5 | not found (no such tool for this key) |
6 | invalid input (did not match the tool's schema) |
7 | refused (a well-formed request the product declined) |
8 | rate limited (after the SDK's retries) |
9 | server error or network failure |
10 |
|
Errors go to stderr; results go to stdout.
MCP over stdio
For an MCP client that only launches a local command, seolyticize mcp relays the hosted server (https://seolyticize.com/api/mcp) over stdin and stdout with your key:
{ "mcpServers": { "seolyticize": { "command": "seolyticize", "args": ["mcp", "--group", "onboarding"], "env": { "SEOLYTICIZE_API_KEY": "sk_seo_…" } } } }--group (onboarding, weekly, technical, research, reporting) lists only that job's tools. Clients that speak HTTP can connect to the hosted URL directly instead.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Toolstile is a managed MCP gateway that connects remote MCP servers behind one endpoint, with per-agent permissions, shared accounts and activity logs. Connect at https://mcp.toolstile.com/mcp over Streamable HTTP with OAuth; sign in at https://toolstile.com, select a workspace and connect your upstream servers. Available tools, resources and prompts depend on that workspace and the agent's granted access.
Streamable HTTP MCP gateway for NV oOS fleets — one API key, namespaced tools, quotas and policy.
Governed MCP gateway: one endpoint for your tools, with credential custody and audit log.
Remote MCP server exposing SMI Aware tools, resources, and skills over Streamable HTTP.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables local MCP clients to access tools from a remote FastMCP server over stdio, handling OAuth authentication and Streamable HTTP communication.-
- AlicenseNot gradedqualityBmaintenanceEnables connecting multiple remote HTTP MCP servers through a single local stdio endpoint, handling OAuth authentication, token refresh, and namespace-scoped tools.16 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables any Streamable HTTP MCP client to reach every tool from many upstream MCP servers through a single URL and API key. Upstream stdio servers are spawned server-side with allowlisted environments and per-profile scoping, so clients install nothing and hold no upstream credentials.53 npm1Apache 2.0

Photon MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables MCP clients that only support stdio servers to access hosted-equivalent tools and operations through a local server using an Account Service Key, excluding key management, account security, SSO, and billing checkout.1Apache 2.0