optivise
Server Configuration
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 |
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
| Capability | Details |
|---|---|
| tools | {} |
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 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Several tools have overlapping purposes: implementation_guide and project_helper both provide development guidance, while code_analyzer and debug_helper both analyze code for issues. Descriptions clarify some boundaries but ambiguity remains, especially for agents relying on tool names alone.
All tools follow a consistent optidev_<topic>_<role> pattern (analyzer, guide, helper) and use snake_case throughout. The convention is uniform and predictable, even though it uses nouns rather than verbs.
With exactly 5 tools, the server is well-scoped for a development assistance purpose. Each tool covers a distinct area without unnecessary duplication, making the set manageable and purposeful.
The toolset covers key development assistance needs: context analysis, implementation guidance, debugging, code analysis, and project setup. Minor gaps exist (e.g., testing or deployment guidance), but core workflows are well represented.