Powered by Zoomin Software. For more details please contactZoomin

MarkLogic MCP Server

Table of Contents

MarkLogic MCP Server environment variables

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
Print
  • Last Updated: September 9, 2026
  • 2 minute read
    • Documentation

MarkLogic MCP Server uses environment variables in .env for runtime overrides and optional feature switches.

Note: Core connection settings (such as MarkLogic REST app server URL and authentication method) and OAuth server metadata now reside in config.yaml. See the config.yaml Reference for core configuration settings.

Runtime and Container settings

These settings are optional.

Variable Default Used by Notes
MARKLOGIC_MCP_IMAGE marklogic/marklogic-mcp:local Docker Compose Specifies the Docker image tag for the MCP server container in docker-compose.yaml.
MCP_FORCE_HTTPS_METADATA true Hyperforge auth middleware Controls whether Hyperforge forces HTTPS in OAuth metadata URLs. Set to false for local http://localhost testing.
MRA_DEFINITION_CACHE_TTL_SECONDS 300 RetrieveDefinition tool How long, in seconds, a /v1/retrieve/definition response is cached before it is fetched again. Set to 0 to disable caching. Non-integer values fall back to the default.
MRA_DEFINITION_CACHE_MAX_ENTRIES 256 RetrieveDefinition tool Maximum number of cached definition responses retained. Entries are evicted least-recently-used once the limit is reached. The minimum effective value is 1; non-integer values fall back to the default.

Standalone bootstrap settings

These settings are optional.

Variable Used by Notes
load_modules Standalone startup

Default: [] (empty list)

JSON array of additional modules loaded after Hyperforge core registrations. The supplied docker-compose.yaml sets this to ["hyperforge_passthrough", "mra_agent"], which is required for the MarkLogic MCP tools to be registered.
standalone_application_class Standalone startup

Default: hyperforge.standalone.app.StandaloneApplication

Dotted Python path for the application class used by the standalone server. MarkLogic MCP Server uses the default.

Sample .env file

# Optional runtime overrides for Hyperforge standalone.
# Most server and OAuth/MarkLogic settings now live in config.yaml.

# Controls whether Hyperforge forces https in OAuth metadata URLs.
# Set false for local http://localhost MCP testing.
# MCP_FORCE_HTTPS_METADATA=true
Alert