rea
Reverse engineer anything with agents, from app behavior down to native binaries.
Delegate asynchronous coding jobs between Claude Code, Codex, Cursor Agent, and Pi.
Skills that teach the AI this kind of work; they work alongside this one
Reverse engineer anything with agents, from app behavior down to native binaries.
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 4/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 16/100 |
Quality: Passed 2/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Passed 2/3 checks · Runs on your computer
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
No key, nothing to install · Only the Claude desktop app (Windows or Mac), not the web or phone
Download the maker’s .mcpb file
The .mcpb file comes straight from the maker; we do not change it
Use LLM Provider MCP and tell me what you can do for me, then show me one thing✓ If Claude says it is using LLM Provider MCP or shows a LLM Provider MCP tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect LLM Provider MCP yet
LLM Provider MCP runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect LLM Provider MCP
B · Others in Developer tools that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Claude Code cannot connect LLM Provider MCP yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect LLM Provider MCP
Cursor cannot connect LLM Provider MCP yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect LLM Provider MCP
VS Code cannot connect LLM Provider MCP yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect LLM Provider MCP
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
JSON settings are under “For developers” below
mcpb: …/llm-provider-mcp_darwin_amd64.mcpbmcpb: …/llm-provider-mcp_darwin_arm64.mcpbmcpb: …/llm-provider-mcp_linux_amd64.mcpbBased on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account manishiitg, which owns the repo
Code last changed today
GitHub could not identify the licence type; open the file to check
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Not checked: only npm and PyPI packages with a version can be checked
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/manishiitg-llm-provider-mcp)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 2 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed today, and the latest version (0.7.3) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
In the same category: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Cloudflare MCP servers
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| This one LLM Provider MCP | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Cloud or install on your computer |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | Yes | No | No |
| Basic checks | 2/3 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| License | NOASSERTION | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
multi-llm-provider-go is a Go library for using hosted LLM APIs and local coding agents through a shared set of provider interfaces.
It supports two complementary ways to run a model:
The repository also includes llm-provider-mcp, an optional MCP server for delegating asynchronous work between coding agents. It is one way to expose the provider library—not the library's only use case.
Applications should be able to choose the right model and transport for each task without rebuilding their orchestration layer.
Use a direct API when you want a conventional request/response integration, predictable infrastructure, or model-level features such as structured output, embeddings, and media generation. Use a coding-agent CLI when you want an agent that can inspect a repository, edit files, run commands, and reuse an existing local subscription. Both fit behind the same Go model abstraction.
flowchart LR
App[Go application] --> Provider[Shared provider interfaces] Provider --> API[API and cloud adapters] Provider --> CLI[Local coding-agent adapters] API --> Hosted[Hosted models] CLI --> Native[SDK / app-server / RPC] CLI --> Tmux[Optional tmux sessions] Native --> Agents[Claude Code / Codex / Cursor / Pi] Tmux --> Agents MCP[Optional MCP server] --> CLI
The core InitializeLLM factory returns the same llmtypes.Model interface for text and coding-agent providers:
| Provider ID | Integration | Transport |
|---|---|---|
openai | OpenAI | OpenAI Go SDK |
anthropic | Anthropic | Anthropic Go SDK |
openrouter | OpenRouter | OpenAI-compatible API |
bedrock | AWS Bedrock | AWS SDK |
vertex | Google Vertex AI and Gemini | Google Gen AI SDK |
azure | Azure AI | Azure/OpenAI-compatible API |
z-ai | Z.AI | OpenAI-compatible API |
kimi | Kimi/Moonshot | OpenAI-compatible API |
minimax, minimax-coding-plan | MiniMax | Provider API |
claude-code | Claude Code | Agent SDK; optional tmux |
codex-cli | Codex CLI | app-server; optional tmux |
cursor-cli | Cursor Agent | Cursor SDK; optional ACP or tmux |
pi-cli | Pi | RPC |
Specialized factories expose capabilities that do not fit the text-model interface:
| Capability | Providers |
|---|---|
| Embeddings | OpenAI, OpenRouter, Vertex AI, Bedrock |
| Image generation | Vertex AI, MiniMax Coding Plan, Codex CLI |
| Video generation | Vertex AI (Veo and Gemini Omni) |
| Text to speech | Vertex AI, MiniMax, ElevenLabs, Deepgram |
| Audio transcription | Deepgram |
| Music generation | ElevenLabs, MiniMax |
Gemini models are available through Vertex AI for direct API access or through Pi as a coding agent. The old Gemini CLI adapter has been removed.
Provider support varies, but the shared interfaces cover:
Install the module:
go get github.com/manishiitg/multi-llm-provider-go@latest
The current module requires Go 1.25.12 or newer.
Initialize a provider and use the returned llmtypes.Model:
package main
import ( "context" "fmt" "log"
llmproviders "github.com/manishiitg/multi-llm-provider-go" "github.com/manishiitg/multi-llm-provider-go/llmtypes" )
func main() { model, err := llmproviders.InitializeLLM(llmproviders.Config{ Provider: llmproviders.ProviderOpenAI, ModelID: "gpt-4.1-mini", }) if err != nil { log.Fatal(err) }
response, err := model.GenerateContent( context.Background(), []llmtypes.MessageContent{ llmtypes.TextParts(llmtypes.ChatMessageTypeHuman, "Explain tmux in one sentence."), }, ) if err != nil { log.Fatal(err) }
if len(response.Choices) == 0 { log.Fatal("provider returned no choices") } fmt.Println(response.Choices[0].Content) }
Set the credential expected by the selected provider—for example, OPENAI_API_KEY for OpenAI. Credentials can also be supplied explicitly with Config.APIKeys. See the examples for streaming, tool calls, custom logging, Bedrock, and Vertex AI.
llmproviders.Config controls provider initialization:
| Field | Purpose |
|---|---|
Provider | Selects the API, cloud platform, or coding CLI |
ModelID | Selects a model; provider defaults apply when supported |
Temperature | Sets sampling temperature for providers that expose it |
APIKeys | Supplies credentials explicitly instead of using the environment |
MaxRetries | Configures retries on the selected model |
Logger / EventEmitter | Connects host logging, tracing, and model events |
Context | Controls initialization lifetime and cancellation |
Common credential sources include:
| Provider | Environment or native authentication |
|---|---|
| OpenAI | OPENAI_API_KEY |
| Anthropic | ANTHROPIC_API_KEY |
| OpenRouter | OPENROUTER_API_KEY |
| AWS Bedrock | Standard AWS credential chain and AWS_REGION |
| Vertex AI | VERTEX_API_KEY, GOOGLE_API_KEY, or Google application credentials |
| Azure AI | AZURE_AI_ENDPOINT and AZURE_AI_API_KEY |
| Z.AI / Kimi | ZAI_API_KEY, KIMI_API_KEY |
| MiniMax | MINIMAX_API_KEY or MINIMAX_CODING_PLAN_API_KEY |
| ElevenLabs / Deepgram | ELEVENLABS_API_KEY, DEEPGRAM_API_KEY |
| Coding-agent CLIs | Existing native CLI login or provider configuration |
See .env.example for common provider credentials. Model, endpoint, fallback, and test-specific variables are documented next to the provider adapters and tests that consume them.
Changing transports starts with changing the provider:
config.Provider = llmproviders.ProviderAnthropic // direct API
config.Provider = llmproviders.ProviderBedrock // cloud API config.Provider = llmproviders.ProviderCodexCLI // local coding agent config.Provider = llmproviders.ProviderCursorCLI // local coding agent
Bounded coding-agent calls can use the process working directory and a temporary session automatically. Long-lived host applications should explicitly pass CodingAgentWorkingDirOption, CodingAgentInteractiveSessionOption, and CodingAgentPersistentInteractiveOption. Provider-specific options additionally control the model, approval policy, resume ID, tools, and streaming behavior.
The coding-agent adapters turn native coding CLIs into providers without reimplementing their agent loops. They use each CLI's existing login and model access, and run in a local project with that CLI's native file and shell tools.
Native SDK and protocol transports are the defaults. Keep tmux available explicitly when a terminal session is needed:
| Provider | Default | Environment override |
|---|---|---|
| Claude Code | SDK | CLAUDE_CODE_TRANSPORT=sdk or tmux |
| Codex | app-server | CODEX_CLI_TRANSPORT=app-server or tmux |
| Cursor | SDK | CURSOR_CLI_TRANSPORT=sdk, acp or tmux |
| Pi | RPC | No terminal transport |
Set these variables on the backend and restart it. A native launch failure does not switch to tmux automatically. SDK modes require Node.js and the matching @anthropic-ai/claude-agent-sdk or @cursor/sdk package. The adapters look in the managed CLI installation prefix before the global npm prefix; explicit CLAUDE_AGENT_SDK_PATH and CURSOR_SDK_PATH overrides are also supported.
| CLI | Provider ID | Authentication |
|---|---|---|
| Claude Code | claude-code | Existing Claude Code login or scoped OAuth token |
| Codex CLI | codex-cli | Existing Codex login |
| Cursor Agent | cursor-cli | Existing Cursor login |
| Pi CLI | pi-cli | Existing Pi/provider configuration |
Requirements for the optional tmux transport:
The library exposes session lifecycle, resume, input, interrupt, pane capture, and cleanup helpers so a host application can manage coding agents as part of its own workflow.
multi-llm-provider-go/
├── providers.go # Provider IDs, configuration, initialization ├── provider_*.go # Shared provider behavior and media factories ├── interfaces/ # Logging, events, and public support contracts ├── llmtypes/ # Messages, responses, tools, streams, options ├── pkg/adapters/ # API, cloud, media, and coding-CLI adapters ├── pkg/codingagentjob/ # Durable asynchronous job execution ├── pkg/codingagentmcp/ # Optional MCP tool surface ├── pkg/tmuxcapture/ # Terminal progress capture and cleanup ├── cmd/llm-chat/ # Local provider chat client ├── cmd/llm-test/ # Manual provider contract runner └── cmd/llm-provider-mcp/ # Optional delegation MCP server
llmtypes.Model is the central text request/response interface. Additional interfaces cover embeddings, image generation, video generation, audio generation and transcription, and music generation.
llm-provider-mcp packages the coding-agent providers as a local stdio MCP server. A Codex or Claude Code host can queue work in another coding CLI, continue working, and retrieve the result later. Jobs are persisted in SQLite and executed in detached tmux sessions.
Install it in the project where you want delegation:
curl -fsSL https://raw.githubusercontent.com/manishiitg/llm-provider-mcp/main/scripts/install-mcp.sh | sh
The setup detects installed CLIs, registers selected hosts and targets for the current project, verifies authentication, and installs the delegation skill. The server is also published in the official MCP Registry as io.github.manishiitg/llm-provider-mcp.
It exposes five tools:
| Tool | Purpose |
|---|---|
list_coding_agents | List enabled targets and capabilities |
list_coding_agent_models | Discover available model selectors |
delegate_coding_agent | Start an asynchronous coding job |
get_coding_agent_job | Read progress, terminal output, or the final result |
cancel_coding_agent_job | Stop a queued or running job |
See Installation and Delegation workflow for the complete MCP workflow.