Documentation
Properties, reports, the MCP server and billing — how the workspace fits together.
Getting started
Create an account, then connect one property. The onboarding flow asks for a Search Console site, connects it with your Google account and runs a first audit.
A property is active once Search Console is connected. GA4 is optional but unlocks the acquisition and conversion tools.
Connecting an MCP client
The MCP endpoint lives at /api/mcp and speaks streamable HTTP. It exposes 37 tools: 23 for Search Console, 12 for GA4 and 2 for PageSpeed.
It also advertises 8 prompt routines: seo-coach, seo-audit, keyword-research, competitor-analysis, content-brief, monthly-report, technical-audit, ai-visibility. Call prompts/list in your client and pick one; each routine asks its questions first, then runs the matching tools in order.
Create a token on the MCP page, then paste the config block into your client. A token is scoped to one workspace; revoking it stops every client that used it.
Every call is written to the activity log with its arguments and duration, so a surprising answer can be reproduced.
Scheduled reports
Each property can have one weekly or one monthly report. It is delivered as an email digest with a short plain-English summary.
Reports run from a background queue, so a slow Search Console response never blocks a page load.
Plans and refunds
Solo: ₹999/mo or ₹9,999/yr for 1 site.
Pro: ₹1,999/mo or ₹19,999/yr for 1 site.
Studio: ₹4,499/mo or ₹44,999/yr for 5 sites.
Growth: ₹9,999/mo or ₹99,999/yr for 12 sites.
Agency: ₹19,999/mo or ₹1,99,999/yr for 30 sites.
Refund windows
Monthly plans: 7 days. Half-yearly: 15 days. Yearly: 30 days.
A refund is issued to the original payment method through Razorpay. After the window closes, cancelling stops the next renewal and the plan runs to the end of the term.
Team seats
The Agency plan includes ten seats. Invite a teammate by email; they join the same workspace and see the same properties, tasks and reports.
Reports can carry white-label branding — your logo and colour replace ours in the PDF header.
Client setup
The same endpoint and bearer token, pasted into each client's config file. The token is created on the MCP page.
Claude Desktop
claude_desktop_config.json{
"mcpServers": {
"seokit24": {
"type": "http",
"url": "https://seokit24.com/api/mcp",
"headers": { "Authorization": "Bearer sk24_your_token" }
}
}
}Save the file, then restart Claude Desktop. The token is created on the MCP page.
Cursor
.cursor/mcp.json{
"mcpServers": {
"seokit24": {
"url": "https://seokit24.com/api/mcp",
"headers": { "Authorization": "Bearer sk24_your_token" }
}
}
}Reload the window after saving. Cursor lists the tools under Settings → MCP.
Codex CLI
~/.codex/config.toml[mcp_servers.seokit24] url = "https://seokit24.com/api/mcp" bearer_token_env_var = "SEOKIT24_MCP_TOKEN"
Export SEOKIT24_MCP_TOKEN in the shell that starts Codex.
ChatGPT
Settings → ConnectorsCreate a custom connector with the endpoint URL. Use the API-key/token field when your plan exposes it; otherwise connect from a client that can send the bearer header.
Setup reference
Environment variables the app reads.
- DATABASE_URL
- PostgreSQL connection string
- BETTER_AUTH_SECRET
- Session signing key
- GOOGLE_CLIENT_ID
- OAuth client (GSC + GA4 scopes)
- GOOGLE_CLIENT_SECRET
- OAuth client secret
- RAZORPAY_KEY_ID
- Checkout key
- RAZORPAY_KEY_SECRET
- Checkout secret
- RAZORPAY_WEBHOOK_SECRET
- Webhook signature
- PAGESPEED_API_KEY
- PageSpeed Insights
- PG_BOSS_ENABLED
- Set 0 to disable the report queue worker
- ADMIN_EMAILS
- Operators allowed into /app/admin
- ANTHROPIC_API_KEY
- Claude-written report narrative
- RESEND_API_KEY
- Email delivery for scheduled reports
- REPORT_FROM_EMAIL
- From address for report email
Missing values disable the matching feature instead of failing at runtime. The settings page shows which are present.