MCP Server with OpenAI-Compatible Model Support
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAI_MODEL | No | Model identifier for generate_text tool. | gpt-4o-mini |
| MCP_HTTP_HOST | No | Host for HTTP transport. | 127.0.0.1 |
| MCP_HTTP_PORT | No | Port for HTTP transport. | 3000 |
| MCP_TRANSPORT | No | Transport mode: stdio, http, or both. | stdio |
| OPENAI_API_KEY | No | API key for OpenAI-compatible provider (required for generate_text tool). | |
| OPENAI_BASE_URL | No | Base URL for OpenAI-compatible API. | https://api.openai.com/v1 |
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 | {
"listChanged": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| server_healthC | Checks whether the MCP server and provider configuration are ready. |
| generate_textC | Generate text using the configured OpenAI-compatible model. |
| list_modelsB | Returns the currently configured model metadata for the MCP server. |
| echoA | Returns the provided message back. Useful for testing the connection. |
| list_directoryB | Lists the files and folders at a path on the machine running this server. |
| read_fileB | Reads and returns the text contents of a file on the machine running this server. |
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 6 tools
All six tools have clearly distinct purposes: echo is for testing, generate_text for model generation, list_directory and read_file for file operations, list_models for model metadata, and server_health for checking configuration. There is no overlap or ambiguity.
Most tools follow a verb_noun pattern (generate_text, list_directory, list_models, read_file), but echo is a single verb and server_health is a noun phrase, breaking consistency. The pattern is still readable but not uniform.
With six tools, the count is reasonable for an MCP server. However, the server's stated focus on OpenAI-compatible model support is somewhat diluted by the inclusion of file system tools (list_directory, read_file), which slightly reduces the sense of a well-scoped set.
For a server claiming OpenAI-compatible model support, the tool surface is notably sparse: only a single generate_text tool and a list_models tool. Missing capabilities like context management, streaming, or role-based chat severely limit model interaction. File access is also one-sided (read only).