Claude Code Policy: Write Managed Settings Fast
Read More
Enterprise Connectors
LLMSE logo. LLMSE MCP server connector.

LLMSE MCP Server

Public MCP server for the LLM Search Engine

ToolsTools
10
Last updatedLast Updated
Jun 14, 2026
CategoryCategory
All
Enterprise-grade security
SSO & authentication ready
Full governance & audit logs

What is the LLMSE MCP Server?

The LLMSE MCP server gives AI agents structured, permission-aware access to LLMSE through the Model Context Protocol. With 10 pre-built actions, agents can read, create, and update LLMSE data on behalf of authorized users.

Willow ships the LLMSE MCP server as part of an enterprise control plane. Every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to a full audit trail, and integrates with Splunk and Loki for SIEM visibility. Connect from Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, or any custom agent. Install once, distribute org-wide, and see exactly how LLMSE is being used by every AI agent in your stack.

Tools

Tool

classify_url

Classify a website URL into category, subcategory, language, and sentiment. Fetches the URL content and uses AI for classification. Results are cached for fast subsequent lookups. Rate limited to 1 request per minute per domain. Args: url: The website URL to classify (e.g., "https://example.com"). Returns: Classification result with: - url: The normalized URL - category: Main category (e.g., "Sports", "Technology") - subcategory: Specific subcategory - language: Detected content language - sentiment: Content sentiment (Good/Neutral/Bad) - age: Target age group (if available) - gender: Target gender (if available) - cached: Whether result was from cache
Tool

select_advertiser

Select the best advertisers based on website demographics. Matches advertisers to website content based on classification demographics. Provide either a URL (classification will be fetched) or demographics directly. Rate limited to 1 request per minute per domain when using URL. Scoring weights: - Category match: +10 points - Age match: +5 points - Gender match: +3 points - Sentiment match: +2 points - Higher CPM bid as tiebreaker Args: url: URL to match advertisers for (fetches classification from cache). category: Target category (e.g., "Sports", "Automotive"). subcategory: Target subcategory. age: Target age group (e.g., "18-24", "25-34", "31-51"). gender: Target gender ("male", "female", or "all"). sentiment: Content sentiment ("Good", "Neutral", or "Bad"). limit: Number of advertisers to return (1-10, default 3). min_cpm: Minimum CPM cost filter (e.g., 5.0 for $5+ CPM). max_cpm: Maximum CPM cost filter (e.g., 10.0 for $10 or less CPM). Returns: Dictionary with: - matches: List of matched advertisers with scores - match_count: Number of matches found - classification: URL classification (if URL provided) - demographics: Provided demographics (if no URL)
Tool

analyze_seo

Analyze a website URL for SEO optimizations. Fetches the URL content and analyzes HTML for possible SEO improvements. Results are cached for fast subsequent lookups. Rate limited to 1 request per minute per domain. Args: url: The website URL to analyze (e.g., "https://example.com"). Returns: SEO analysis result with: - url: The analyzed URL - score: Overall SEO score (0-100) - grade: Letter grade (A-F) - issues: List of SEO issues found (critical, warnings, info) - meta: Extracted meta information (title, description, headings, etc.) - recommendations: Prioritized list of improvements - cached: Whether result was from cache
Tool

analyze_eeat

Analyze a website URL for E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness). Evaluates content quality signals based on Google's Search Quality Rater Guidelines and "Creating helpful content" documentation. Detects EEAT signals including: - Experience: First-person language, case studies, testimonials, years of experience - Expertise: Author credentials, certifications, professional memberships, topic depth - Authoritativeness: Organization schema, awards, trust badges, media mentions - Trustworthiness: HTTPS, contact info, privacy policy, source citations Also detects YMYL (Your Money or Your Life) content for health, financial, and legal topics. Results are cached for fast subsequent lookups. Rate limited to 1 request per minute per domain. Args: url: The website URL to analyze (e.g., "https://example.com"). Returns: EEAT analysis result with: - url: The analyzed URL - score: Overall EEAT score (0-100) - grade: Letter grade (A-F) - scores: Individual category scores (experience, expertise, authoritativeness, trustworthiness) - issues: Categorized issues (critical, warnings, info) - signals: Detected EEAT signals - meta: Extracted meta information - recommendations: Prioritized list of improvements - cached: Whether result was from cache
Tool

analyze_aeo

Analyze how well content is optimized for AI answer engines. Evaluates content for AI answer engines (ChatGPT, Perplexity, Gemini, Claude). Combines Q&A pattern detection, snippet extractability, and entity clarity analysis with a full Citation Readiness assessment. AEO Scoring Framework (100 points): - Answer Format Detection: 30 points (Q&A extractability patterns) - FAQ Schema Presence: 20 points (FAQPage schema markup) - HowTo Schema Presence: 15 points (HowTo schema markup) - Direct Answer Snippets: 20 points (short extractable blocks <50 words) - Entity Clarity Score: 15 points (clear entity definitions) Neutral Schema Scoring: If no FAQ/HowTo-style content detected, those schema metrics score full points rather than penalizing. Grade Scale: A (85-100), B (70-84), C (55-69), D (40-54), F (0-39) Results are cached for fast subsequent lookups. Rate limited to 1 request per minute per domain. Args: url: The website URL to analyze (e.g., "https://example.com"). Returns: AEO analysis with: - url: The analyzed URL - aeo_score: Overall AEO score (0-100) - aeo_grade: Letter grade (A-F) - aeo_metrics: Individual metric scores - citation: Full Citation Readiness analysis (score, grade, issues, signals) - issues: Problems detected (critical, warnings, info) - signals: Positive signals detected - recommendations: Prioritized improvements - cached: Whether result was from cache
Tool

analyze_wcag

Analyze a website URL for WCAG 2.1 Level A accessibility issues. Automated static HTML analysis covering approximately 30-40% of WCAG 2.1 Level A criteria. Checks include: image alt text, form labels, heading hierarchy, page title, html lang, empty links/buttons, ARIA labels, duplicate IDs, skip navigation, table headers, landmarks, viewport zoom, autoplay media, and tabindex ordering. Manual testing is required for full WCAG compliance assessment. Results are cached for fast subsequent lookups. Rate limited to 1 request per minute per domain. Args: url: The website URL to analyze (e.g., "https://example.com"). Returns: WCAG analysis with: - url: The analyzed URL - score: Accessibility score (0-100) - grade: Letter grade (A-F) - issues: Categorized issues (critical, warnings, info) - meta: Extracted accessibility metadata - recommendations: Prioritized improvements - coverage_note: Disclaimer about automated coverage - cached: Whether result was from cache
Tool

analyze_garm

Compute GARM brand safety score for a website or category. Based on the GARM (Global Alliance for Responsible Media) Brand Suitability Framework. Maps content categories to 11 GARM sensitive content categories with risk levels (Floor, High, Medium, Low). Can either: 1. Provide a URL - classification will be fetched and mapped to GARM 2. Provide category and sentiment directly for instant scoring Score interpretation: higher = safer for advertising. Floor categories (e.g., Adult) always score 0/F regardless of sentiment. Args: category: LLMSE category (e.g., "Adult", "Politics", "Sports"). sentiment: Content sentiment ("Bad", "Neutral", "Good"). url: Optional URL to analyze (fetches classification from cache). Returns: GARM brand safety analysis with: - score: Brand safety score (0-100, higher = safer) - grade: Letter grade (A-F) - garm_category: Matched GARM category name or None - risk_level: "floor"|"high"|"medium"|"low"|"none" - is_floor: True if not suitable for any advertising - issues: Categorized issues {critical, warnings, info} - recommendations: Improvement suggestions
Tool

analyze_readability

Analyze a website URL for content readability using Flesch Reading Ease. Extracts plain text from HTML and computes readability metrics including Flesch Reading Ease score, Flesch-Kincaid grade level, reading time, and word/sentence statistics. Grade Scale (web-optimized): - A (60-100): Easy, 6th-8th grade — ideal for web content - B (50-59): Fairly easy, some high school - C (30-49): Standard, college level - D (10-29): Difficult, graduate level - F (0-9): Very difficult, professional/academic Results are cached for fast subsequent lookups. Rate limited to 1 request per minute per domain. Args: url: The website URL to analyze (e.g., "https://example.com"). Returns: Readability analysis with: - url: The analyzed URL - score: Flesch Reading Ease score (0-100, higher = easier) - grade: Letter grade (A-F) - flesch_kincaid_grade_level: US school grade level equivalent - reading_time_minutes: Estimated reading time in minutes - word_count: Total word count - sentence_count: Total sentence count - difficult_words: Count of difficult/uncommon words - cached: Whether result was from cache
Tool

audit

Perform comprehensive audit of a website URL. Fetches the URL content ONCE and provides a combined report with: - Classification: category, subcategory, language, sentiment, demographics - SEO Analysis: score, grade, issues, recommendations - EEAT Analysis: experience, expertise, authoritativeness, trustworthiness scores - AEO Analysis: AI answer engine optimization score, metrics, issues, signals (includes full Citation Readiness analysis in the nested 'citation' key) - Advertiser Matching: best-fit advertising networks with scores - Similar Sites: competitor/related sites from the same category This is more efficient than calling classify_url, analyze_seo, analyze_eeat, analyze_aeo, select_advertiser, and find_similar_sites separately as it only fetches the page once. Args: url: The website URL to audit (e.g., "https://example.com"). Returns: Comprehensive audit report with: - url: The analyzed URL - classification: Category, subcategory, language, sentiment, demographics - seo: Score, grade, issues, recommendations - eeat: EEAT score, grade, category scores, issues, signals - aeo: AEO score, grade, metrics, issues, signals (includes citation results) - advertisers: Matched advertising networks with scores - similar_sites: Related sites from the same category (up to 10) - cached: Whether result was from cache
Tool

find_similar_sites

Find similar or competitor websites based on classification. Takes a URL, classifies it (or uses cached classification), and returns other websites from the same category and subcategory. Useful for competitive analysis and discovering related content. Rate limited to 1 request per minute per domain. Args: url: The website URL to find similar sites for. limit: Maximum number of similar sites to return (1-50, default 10). Returns: Dictionary with: - url: The input URL (normalized) - classification: The URL's category and subcategory - similar_sites: List of similar URLs from the same category - total_in_category: Total sites in this category/subcategory - cached: Whether the classification was from cache
Customize tools

Customize Tools

Edit descriptions, modify arguments, select tools, or add new ones

ReviewEdit descriptions
ConfigureChange arguments
ApproveSelect tools
Create NewAdd tool

Set Up Your LLMSE MCP Server in Minutes

Add the following configuration to your MCP client. Authentication is handled via OAuth. Compatible with Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, and any MCP-compatible agent.

Claude Desktop

claude_desktop_config.json
{
  "mcpServers": {
    "willow-llmse": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/llmse"
    }
  }
}

Cursor

.cursor/mcp.json
{
  "mcpServers": {
    "willow-llmse": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/llmse"
    }
  }
}

Claude Code

CLI
claude mcp add willow-llmse --transport http https://<org>.mcp-s.com/mcp/mcp/llmse

n8n

HTTP Request Node
{
  "url": "https://<org>.mcp-s.com/mcp/mcp/llmse",
  "method": "POST"
}

Or click "Install with Willow" above to set up automatically with SSO and RBAC preconfigured.

Enterprise Governance for LLMSE

Willow adds the layer LLMSE and every other SaaS doesn't ship out of the box: every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to full audit logs, and detects shadow AI usage across your stack. One MCP gateway. Any agent. Every tool.

LLMSE MCP Server FAQ

What is the LLMSE MCP server?

The LLMSE MCP server is a Model Context Protocol implementation that lets AI agents like Claude, Cursor, and ChatGPT read and write LLMSE data through a standardized interface. Willow hosts and governs this server so enterprises can roll it out without a security review backlog.

How is Willow's LLMSE MCP server different from the official one?

The official LLMSE MCP server is scoped to a single user's account and does not include enterprise governance. Willow's version adds SSO, RBAC, audit logging, shadow AI detection, and centralized control over which actions agents can take across the entire org.

Which AI clients work with the LLMSE MCP server?

Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code with MCP support, n8n, and any custom agent built with OpenAI Agents SDK, LangChain, Vercel AI SDK, or Anthropic SDK.

Is the LLMSE MCP server secure? How does Willow handle authentication?

Every call runs behind your existing SSO (Okta, Azure AD). Per-user OAuth scopes the agent to exactly what that user can do in LLMSE, nothing more. No credentials reach the LLM. Every action writes to an audit trail.

Can I limit which LLMSE actions agents can take?

Yes. Willow lets you scope agents to specific actions, specific projects, or specific environments. Toggle actions on or off in the dashboard, or enforce policy via infrastructure-as-code through GitHub.

How do I detect shadow LLMSE MCP servers in my org?

Willow's browser extension and discovery service surface unmanaged MCP servers, skills, and AI agents across the org. If a developer installed an unapproved LLMSE MCP locally, you'll see it.

What does the LLMSE MCP server cost?

Pricing depends on org size and deployment model (SaaS, dedicated cloud, self-host). See withwillow.ai/pricing or contact sales for a quote.

How do I install the LLMSE MCP server with Willow?

Install via the Willow Connect Panel in one click, or paste the JSON snippet above into your Claude Desktop, Cursor, or Claude Code config. SSO and RBAC inherit from your existing Willow setup.

Compare Willow MCP Gateway

See how Willow stacks up against other MCP platforms on governance, security, and enterprise readiness.

Your agents are already in the wild.

Give them a Basecamp. Go from AI chaos to AI work, in minutes.

LLMSE MCP Server | Willow