A
licenseA
qualityA
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 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
- FlicenseAqualityFmaintenanceMCP 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.54-
- AlicenseNot gradedqualityCmaintenanceExposes remote, agent-facing MCP endpoints over Streamable HTTP for web search, webpage parsing, local knowledge-base retrieval and document creation, and delegation of tasks to configurable LLM providers. Also bundles an admin console with onboarding, provider/model configuration, API-key management, and call logging.MIT
TDQS
A3.8/5.0
Scored across 3 tools
Disambiguation4/5
chat_complete and messages_create serve genuinely distinct request shapes (OpenAI vs Anthropic schemas), and the descriptions make this clear. However, both do essentially the same thing — run a completion through the host agent — so an agent without a strong schema preference could still hesitate between them.
Naming Consistency2/5
Naming mixes conventions: 'chat_complete' is noun_verb while 'messages_create' is plural_noun_verb and 'list_models' is verb_noun. The verb position flips between first and last, and no single pattern dominates.
Tool Count4/5
Three tools are a tight, well-scoped surface for a thin model shim. The count is slightly thin but each tool earns its place; list_models is arguably redundant given the single-model aliasing, keeping it just below a 5.
Completeness4/5
The server covers the two dominant completion request shapes plus discovery, so core workflows are reachable. Minor gap: no streaming or token-counting option, and no way to introspect model capabilities, but agents can work around these.