Skip to main content
Glama
ia-cae-zurekin-mcp

ia-cae-zurekin-mcp

IA CAE Zurekin MCP Server

Node.js MCP server for authenticated querying of the internal CAEZ Urekin website.

What's included

  • search_pages: searches for content on the authenticated site

  • get_page: retrieves a specific page

  • extract_page_content: returns structured content

  • list_sections: lists navigable links from a root page

Related MCP server: wikijs-mcp

Requirements

  • Node.js 18+

  • A server or environment to run this project outside the editor

  • Adjust the login logic to the actual website if the form does not match the default values

Configuration

  1. Copy .env.example to .env

  2. Complete or adjust the environment variables

  3. Install dependencies:

    • npm install

  4. Start the server:

    • npm start

Main variables

  • CAEZ_BASE_URL: base URL of the internal site

  • CAEZ_USERNAME: access username

  • CAEZ_PASSWORD: access password

  • CAEZ_LOGIN_URL: exact login URL if different from the base

  • CAEZ_LOGIN_USER_FIELD: actual name of the username field in the form

  • CAEZ_LOGIN_PASSWORD_FIELD: actual name of the password field in the form

  • CAEZ_LOGIN_EXTRA_FIELDS: JSON with extra form fields, if any

  • CAEZ_SEARCH_PATH: internal search path if the site has a specific URL for searching

Preloaded configuration for your case

The example has already been adjusted with this base:

  • CAEZ_LOGIN_URL=https://interna.caezurekin.biz/caezurekin

  • CAEZ_LOGIN_USER_FIELD=username

  • CAEZ_LOGIN_PASSWORD_FIELD=password

Likely adjustments

It is very likely that you will still need to adapt:

  • the authentication flow if there are redirects, CSRF tokens, or SSO

  • the search logic if the site does not have a clear endpoint

  • any additional hidden form fields, if they exist

Usage with your custom MCP

When you deploy it, the MCP connection must point to this server, not directly to the internal website.

Available Tools

4 tools
extract_page_contentC

Extrae el contenido estructurado de una p�gina.

Inputs: url (required), include_tables, include_links.

get_pageC

Obtiene una p�gina concreta del sitio.

Inputs: url, path.

list_sectionsC

Lista secciones navegables del sitio.

Inputs: root_path.

search_pagesC

Busca contenido dentro de la web interna autenticada.

Inputs: query (required), limit, section.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct operation: extracting content from a page, retrieving a specific page, listing sections, and searching within the site. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., extract_page_content, get_page, list_sections, search_pages) using snake_case, making them predictable and easy to understand.

    Tool Count5/5

    The server has 4 tools, which is well-scoped for a website content retrieval and navigation purpose. Each tool serves a clear and necessary function without being redundant or excessive.

    Completeness4/5

    The tool set covers core operations: retrieving pages, extracting content, listing sections, and searching. It lacks features like listing pages within a section or getting page metadata, but these are minor gaps for the intended domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers