Integrations

Works with your tools and your AI assistant

Glimana reads the data, ranks the tasks and measures the result. You do the fixing wherever you like: Claude, ChatGPT, Cursor, your own code or WordPress.

AI assistants (MCP)

Glimana is an MCP server. Your assistant reads your sites, ranked tasks, open issues, measured impact and Search Console queries directly. The connection uses OAuth 2.1, so there is no key to copy. Every tool is read-only: the assistant cannot change, delete or publish anything.

Read-onlyOAuth 2.1

Claude

claude.ai and Claude Desktop

  1. Settings → Connectors → Add custom connector
  2. https://glimana.com/api/mcp
  3. Sign in with Google or email, pick the workspace, click Allow.
Read-onlyCLI

Claude Code

One command, then authenticate with /mcp.

claude mcp add --scope user --transport http glimana https://glimana.com/api/mcp
Read-onlyOAuth 2.1

ChatGPT

  1. Enable developer mode
  2. Create → https://glimana.com/api/mcp
  3. Authentication: OAuth
Read-onlymcp.json

Cursor

Add it to ~/.cursor/mcp.json or the project’s .cursor/mcp.json and restart Cursor.

{"mcpServers":{"glimana":{"url":"https://glimana.com/api/mcp"}}}

Tools: list_sites · get_site_summary · get_priority_tasks · get_open_issues · get_impact_results · get_top_queries · get_ai_bot_access

Clients without OAuth can use the key method from the MCP tab in the panel (Authorization: Bearer). Full setup guide →

Hand the task to your assistant, let Glimana measure the result

Every task has a “For your AI assistant” button. One click copies the reason, the fix, the affected pages, the evidence and the done-criteria as Markdown. Paste it into Claude Code or Cursor; the assistant makes the change and verifies it by asking Glimana over MCP. You mark the task done; Glimana measures the impact against a control group for 28 days.

One task

Tasks › the ✦ icon on a row, or the button on the task page. Copy, paste.

FIX-PLAN.md

All open tasks of a site in priority order in one file, with the MCP command at the top. The assistant works top to bottom.

Closed loop

Fix → Glimana verifies (re-crawl) → impact is measured (28 days, control group) → PDF report.

REST API

The same data as JSON. Create a key under Account settings › API; it is shown once and stored only as a one-way hash. Pro plans and up; rate limit 60–300 requests/min by plan.

curl -H "Authorization: Bearer glm_…" https://glimana.com/api/v1/sites GET /api/v1/sites/{site}/summary · tasks · issues · impacts · queries · ai-access

Endpoints and fields →

WordPress publisher plugin

Receives articles written in Glimana as drafts or scheduled posts on your WordPress site. Every request is HMAC-signed; the plugin exposes nothing else. Setup: download the plugin, upload it under WordPress › Plugins, then enter your site address and key in the Glimana publishing connection.

Download the plugin (.zip)

Google Search Console and GA4

Connect once with your Google account; Glimana asks for read access only. Search Console is pulled with 16 months of history, GA4 adds sessions and conversions. Nothing is written to your site or Search Console; tokens are stored encrypted.

Reports and sharing

PDF reports from the dashboard (you pick the sections), a monthly report by email on the 1st, and signed share links valid for 30 days. Show results to a client or your team without creating accounts.

For agents

A short file that describes the site and the MCP to an agent: glimana.com/llms.txt. Suggested flow: list_sites → get_priority_tasks → fix → verify with get_open_issues → mark the task done in Glimana.

Start free →