MCP AI Bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ask_openaiB | Ask OpenAI GPT models a question |
| ask_geminiC | Ask Google Gemini AI a question |
| server_infoB | Get server status and configuration |
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 3 tools
Each tool has a clearly distinct purpose: ask_gemini and ask_openai target different AI providers with no overlap in functionality, while server_info serves a completely separate administrative role. There is no ambiguity that could lead to misselection between these tools.
All tools follow a consistent verb_noun pattern with snake_case naming: ask_gemini, ask_openai, and server_info. The naming is predictable and readable throughout the set, with no deviations in style or convention.
With only 3 tools, the set feels thin for a server named 'MCP AI Bridge', which suggests broader AI integration capabilities. While the tools cover basic querying and server info, the scope might be underdeveloped, lacking operations like model listing, configuration updates, or multi-turn conversations.
The tool surface covers basic AI querying and server status, but there are notable gaps for a comprehensive AI bridge. Missing operations include listing available models, managing API keys, handling conversation contexts, or supporting other AI providers beyond Gemini and OpenAI, which limits agent workflows.