any-chat-completions-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AI_CHAT_KEY | Yes | API key for the AI chat provider (e.g., OPENAI_KEY, PYROPROMPTS_KEY, PERPLEXITY_KEY) | |
| AI_CHAT_NAME | Yes | Name of the AI chat provider (e.g., OpenAI, PyroPrompts, Perplexity) | |
| AI_CHAT_MODEL | Yes | Model to use for the AI chat (e.g., gpt-4o, ash, llama-3.1-sonar-small-128k-online) | |
| AI_CHAT_BASE_URL | Yes | Base URL for the AI chat provider API (e.g., https://api.openai.com/v1, https://api.pyroprompts.com/openaiv1, https://api.perplexity.ai) |
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| chat-with-openaiC | Text chat with OpenAI |
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 1 tool
Only one tool exists, so there is no possibility of confusion between tools.
With a single tool, naming inconsistency is not applicable; it follows a clear verb_noun pattern ('chat' + 'with-openai').
A chat completions server should typically offer multiple tools (e.g., streaming, model listing, conversation history). A single tool feels overly minimal for the domain.
The single tool only covers basic text chat, missing obvious needs like streaming, parameter customization, or model availability queries, making the surface severely incomplete.