"Tesla Sales Data" matching MCP connectors:
GET /v1/connectors – MCP directory API referenceMatching Connector Tools:
btlabs Core MCP endpoint: site content and brand data for AI agents. OAuth or API key.
PerfectPost is a LinkedIn content management platform. This MCP server gives AI assistants read and write access to a user's PerfectPost account: published posts with their engagement analytics, drafts lifecycle (create / edit / schedule), and LinkedIn profile data.
**Can AI actually read your page?** ChatGPT, Perplexity, Claude and Google's AI Overviews fetch pages very differently from your browser — no JavaScript, tight timeouts, and a robots.txt rulebook of their own. Lekta fetches a URL exactly the way they do and grades what survives, **A+ to F**. This is the technical half of **AEO** (answer engine optimization) and **GEO** (generative engine optimization): before a model can cite you, it has to be able to fetch you, parse you, and find one sentence worth quoting. **The loop this server was built for:** `Audit https://mysite.com/pricing with Lekta, apply the fixes it lists, audit it again, and show me the difference.` Your agent gets a graded verdict, a ranked fix plan with the exact markup to paste, and a diff that proves the change landed. Repeat until A+. **Four layers, 100 points:** **Access** 25 — do the ~17 AI crawler tokens get past robots.txt? **Indexability** 25 — how much content survives without JavaScript? **Answerability** 30 — is there a single quotable sentence an engine can lift? **Recency** 20 — can a model tell when this page was last true? **What this is not:** a rank tracker. Lekta will not tell you how often ChatGPT mentions your brand. It tells you whether your page can be read and quoted when it does — the part you can actually fix. **No black box.** Every finding cites its basis — an RFC, a vendor doc, or a dated measurement we ran. The engine is versioned with a public changelog: a score never moves without a published shift table. **Tools:** `lekta_audit` (fresh fetch) · `lekta_report` (cached read) · `lekta_fix_plan` (ranked, paste-ready) · `lekta_diff` (before/after) · `lekta_my_sites` Listing tools is open. Tool calls need a free key from lekta.dev/en/panel/api — send `Authorization: Bearer lekta_…` or `x-api-key`. Cached reads, fix plans and diffs cost nothing; only fresh fetches count against the daily limit. **Topics:** AEO · GEO · AI SEO · LLM SEO · answer engine optimization · generative engine optimization · AI crawler access (GPTBot, ClaudeBot, PerplexityBot, Google-Extended) · JavaScript-free indexability · structured data · content freshness
Maintain your CV with your agent. Review changes, then share one record as web, PDF and open data.
Turn Search Console data into SEO actions, content, publishing, indexing, and AI insights.
- ME-QROAuthcom.me-qr.mcp
ME-QR MCP Server brings the full power of the ME-QR platform to your AI agents via the Model Context Protocol (MCP). It allows LLMs to autonomously create, design, and manage QR codes for any type of data without leaving the chat interface.
- SoloFireOAuthcom.solofire
Med device and life science sales enablement: search content, share tracked Spaces, see engagement.
Let your AI assistant build pages and courses, manage contacts, and run email campaigns in AXL.
Create, publish and track sales funnels and Sites with custom domains from any MCP agent.
Turns SEO insight into page changes: keyword research, SERP and rank data, rewrites you approve.
SEO, competitor and AI-search data, plus blog management — draft, schedule and publish posts.
8 AI services via MCP: content, code, image, docs, data extraction, translation, SEO, email.
