A
licenseA
qualityB
maintenanceExposes an OpenAI-compatible inference endpoint to MCP hosts, enabling them to list available models and run non-streaming chat completions as tools.
2
MIT
agent-as-model
Related Servers
Alternatives to agent-as-model
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible clients to manage and run local or cloud LLMs, generate completions and embeddings, and perform web search/fetch through exposed tools.897 npmAGPL 3.0
- AlicenseNot gradedqualityCmaintenanceExposes local LM Studio language models as MCP tools, enabling chat completions and model listing through a local OpenAI-compatible API without requiring API keys.MIT
- FlicenseNot gradedqualityDmaintenanceLocal MCP server that exposes fixed tools for GPT, Claude, and Gemini while routing to any OpenAI-compatible chat completions backend with independent configuration per target.1-
- AlicenseNot gradedqualityDmaintenanceExposes internal tools from agent harnesses (Claude Code, Codex, etc.) as a standard MCP server by intercepting LLM API calls.1MIT
- AlicenseAqualityDmaintenanceMCP server that exposes 300+ AI agents as tools via a single API key. Supports listing agents, invoking any agent with chat-completion style messages, checking agent health, and retrieving platform statistics.54MIT
TDQS
A3.9/5.0
Scored across 5 tools
Disambiguation3/5
chat_complete, messages_create, and responses_create perform essentially the same operation—sampling the host model—and differ only in request/response schema. The long descriptions explain the shapes, but an agent must know which external API format is intended, so boundaries are inferable yet easy to confuse.
Naming Consistency3/5
All names use snake_case, but ordering is mixed: list_models and generate are verb-first, while chat_complete, messages_create, and responses_create are noun-first. 'generate' is also vaguer than the other completion tools, so the pattern is readable but not predictable.
Tool Count4/5
Five tools is a healthy, well-scoped count for a model-proxy server. The only slight issue is that three of the five are near-duplicate completion endpoints that could arguably be consolidated.
Completeness4/5
The surface covers the main completion shapes (chat, messages, responses, raw text) plus model discovery, which is solid for a model-sampling proxy. It lacks embeddings, streaming controls, and other peripheral model operations, but core completion workflows are covered.
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues