Schema | optivise

optivise

Describes the environment variables required to run the server.

Name	Required	Description	Default
`LOG_LEVEL`	No	Log level: error\|warn\|info\|debug (default: info)	info
`AUDIT_API_KEY`	No	API key to enable protected GET /audit endpoint (requires OPTIVISE_AUDIT=true)
`OPTIVISE_MODE`	No	Operation mode: mcp\|server (default: mcp)	mcp
`OPENAI_API_KEY`	No	Optional API key to enable AI-powered features
`OPTIVISE_AUDIT`	No	Set to 'true' to enable in-memory audit trail (requires AUDIT_API_KEY)
`MAX_BLOCK_CHARS`	No	Maximum characters per context block (default: 5000)	5000
`MAX_TOTAL_TOKENS`	No	Hard safety ceiling for context tokens (default: 4000)	4000
`CORS_ALLOW_ORIGINS`	No	Comma-separated allowed origins for HTTP server (default: *)	*
`REQUEST_TIMEOUT_MS`	No	Per-request timeout for /analyze (default: 15000)	15000

Features and capabilities supported by this server

Capability	Details
`tools`	{}

Functions exposed to the LLM to take actions

Name	Description
optidev_context_analyzerC	Enhanced context analysis with AI-powered relevance scoring and vector search
optidev_implementation_guideB	Analyzes Jira tickets and provides complete implementation guidance
optidev_debug_helperC	Provides intelligent debugging assistance for Optimizely-related issues
optidev_code_analyzerC	Real-time code analysis for performance, security, and best practices
optidev_project_helperC	Project setup, migration assistance, and development guidance

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/biswajitpanday/Optivise'

If you have feedback or need assistance with the MCP directory API, please join our Discord server