foreign-llm-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FOREIGN_LLM_HOME | No | Override the data directory (default: ~/.foreign-llm-mcp/). Holds the Chrome profile with logged-in sessions (profile/) and generated images (out/). |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| askB | One-shot question to a free web LLM (new chat each call). Good for summarize/translate/ small code/second opinion/web lookup. Returns the reply text. |
| generate_imageC | Generate an image on the web LLM; returns the saved file path under ./out/. |
| list_providersB | Providers and whether each is logged in (error code if not). |
| loginA | Open the provider's site in the browser so the user can sign in. Blocks until the user closes that tab (ask the user to do so when finished), then use list_providers to verify. |
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 4 tools
The four tools cover clearly separate actions: browser sign-in, one-shot text query, image generation, and provider status listing. Login and list_providers sit in the same auth lifecycle, but the login description explicitly points to list_providers for verification, so the boundary is clear.
All names are lowercase snake_case with verb or verb_noun form (login, ask, generate_image, list_providers). Minor deviation: 'login' and 'ask' are bare/ambiguous verb-nouns while the other two follow verb_noun, but the set is still predictable and readable.
Four tools is on the lean side but fits a narrow purpose: authenticate, delegate a question, delegate an image request, and check provider state. Nothing extraneous, though it sits near the thin end of the 3-15 range.
Core flows (sign in, ask, generate image, verify status) are covered, but the auth lifecycle has no logout/switch-provider tool, and there is no way to discover providers or models before a query without trial and error. These gaps are workaroundable but notable for the stated purpose.