Skip to main content
Glama
refined-element

Ask Refined Element MCP Server

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ASK_RE_BASE_URLNoThe base URL of the Ask Refined Element API (`/api/ask/*`). The default is the production site, https://refinedelement.com. Point the server at a different host (e.g. http://localhost:23918) when running against a local Ask Refined Element API.https://refinedelement.com

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_refined_element_knowledgeA

Full-text search over the Ask Refined Element knowledge pack — blog articles, FAQs, case studies, services, checklists, and premium playbooks covering Xperience by Kentico upgrades, GEO (generative engine optimization), AI-driven development, Sentinel for Xperience by Kentico, and CMS architecture. Returns ranked matches, each with an answer-first summary you can cite directly or use to decide which item to fetch in full. FAQ, case study, and service matches carry no slug — their content comes back inline, so the match itself is the answer. Blog articles are read in full with get_article. Free checklists are fetched in full with get_checklist. Premium items return a summary and slug only — retrieve their full body with get_paid_playbook. Omit the query (or pass an empty one) to browse an index of everything in the pack, grouped by content type. Use this as the entry point whenever you need Refined Element's expertise on Kentico, GEO, or agent-ready CMS.

get_checklistA

Fetch one full free checklist from the Ask Refined Element pack by slug (e.g. geo-readiness-checklist-basic). Returns the checklist's title, summary, topic, audience, and complete ordered steps — each with its one-line action and an explanatory sentence — ready to follow, quote, or hand to a user. If the slug names a premium checklist the response explains it is paid and points you to get_paid_playbook. Unknown slugs return a not-found result. Get valid slugs from search_refined_element_knowledge.

get_paid_playbookA

Retrieve one premium item from the Ask Refined Element pack by slug. Premium items are L402-gated (typically 100 sats); discover them and their slugs with search_refined_element_knowledge — they are marked [PREMIUM]. Call this tool FIRST with only the slug: the endpoint answers HTTP 402 Payment Required with a Lightning invoice and a macaroon, which this tool returns as structured payment instructions. Pay the invoice (the free Lightning Enable MCP server can do this automatically — github.com/refined-element/lightning-enable-mcp), then call this tool AGAIN with the same slug plus the macaroon and the payment preimage to receive the full content.

list_articlesA

List the most recent posts from the Refined Element blog — each with its title, publish date, a one-line summary, and the slug to read it in full. Use this to see what Refined Element has published on Xperience by Kentico, GEO, AI-driven development, and agent commerce, then call get_article(slug) for the complete text. Returns newest-first, up to 50 (default 10).

get_articleA

Read one full Refined Element blog article by slug (get slugs from list_articles or search_refined_element_knowledge). Returns the title, publish date, summary, and the complete article body converted from HTML to readable text — headings, lists, and links preserved — plus the canonical URL. Unknown slugs return a not-found result.

request_consultationA

Send a consultation request straight to Mike Rahel at Refined Element — for Xperience by Kentico upgrades, AI-driven development, or agent-first (GEO) work. Submit your name, email, and message; Mike reads every one personally, so include enough context (what you're building, your Kentico version, timeline) for him to act on it. Set priority: true to flag the request as urgent so Mike sees the urgency — priority is free, no payment required.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.3/5.0

Scored across 6 tools

Disambiguation4/5

Each tool targets a distinct content type or action: search as entry point, list_articles for browsing, get_article/get_checklist/get_paid_playbook for fetching specific resource types, and request_consultation for contact. The three 'get_*' fetch tools share a shape but are separated by clear resource boundaries (free article vs free checklist vs premium playbook), so an agent can select reliably.

Naming Consistency5/5

All names follow a consistent verb_noun snake_case pattern (get_checklist, list_articles, get_article, get_paid_playbook, request_consultation, search_refined_element_knowledge). Only search_refined_element_knowledge is verbose, but the convention is uniform throughout.

Tool Count5/5

Six tools is well-scoped for a knowledge-pack/content server, with each tool earning its place across discovery, retrieval, and contact workflows. Nothing feels redundant or missing at the count level.

Completeness4/5

The surface covers discovery (search, list), retrieval by type (article, checklist, premium playbook), and a consultation path, with FAQ/case-study/service content returned inline via search. Minor gap: no dedicated browse/list for checklists or premium playbooks, though search partially compensates.

Maintenance

ActivityMaintained
ResponsivenessNo issues