Skip to main content
Glama
code-wgl

MCP Server with OpenAI Integration

by code-wgl

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MCP_PORTNoReserved for future transports7337
LOG_LEVELNoLog level: fatal → traceinfo
UI_DEMO_PORTNoOptional port for the browser UI demo4399
OPENAI_API_KEYYesAPI key for OpenAI
MCP_SERVER_NAMENoName advertised to MCP clients
OPENAI_BASE_URLNoOverride base URL for Azure/OpenAI proxies
MCP_TOOL_MODULESNoComma-separated absolute paths to extra tool modules
OPENAI_TIMEOUT_MSNoTimeout (ms) applied to OpenAI API calls20000

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
knowledge_searchC

Searches curated knowledge base snippets stored as markdown files.

text_summarizerC

Summarizes long text into concise bullet points using the configured LLM.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: knowledge_search retrieves information from a knowledge base, while text_summarizer condenses provided text. There is no overlap in functionality, and an agent would easily differentiate between them.

Naming Consistency4/5

Both tools use snake_case naming, which is consistent. However, knowledge_search follows a noun_verb pattern (knowledge_search), while text_summarizer uses a noun_verb pattern with a suffix (text_summarizer), showing a minor deviation in naming style.

Tool Count2/5

With only 2 tools, the server feels thin for an 'OpenAI Integration' purpose, which typically implies broader capabilities like text generation, translation, or analysis. This limited set may not adequately cover the expected scope.

Completeness2/5

Given the server's name suggests OpenAI integration, there are significant gaps: no tools for text generation, translation, sentiment analysis, or other common LLM tasks. The surface is incomplete, likely causing agent failures for broader use cases.

Maintenance

ActivityInactive
ResponsivenessNo issues