MCP
MCP bridges
Application Namer does not run an MCP server. It is an MCP client: three Providers reach Claude Code, Codex CLI and Copilot CLI through local MCP bridges.
What an MCP bridge is
An MCP bridge is a locally running mcp-agent-bridge server that exposes Claude Code, Codex CLI or Copilot CLI over MCP. Each one backs exactly one MCP Provider.
How the app calls it
Streamable HTTP at <bridge URL>/mcp. The app sends initialize to get an MCP session id, then tools/call with that session id, and reads the answer from the event stream.
To list Providers, the app tries initialize on each bridge with a 2-second timeout; a bridge that answers is reachable. A Suggestions call may take up to 60 seconds.
Setting it up
Install and run mcp-agent-bridge on the machine that runs Application Namer, on the default ports (8960, 8961, 8962) or on URLs you set in MCP_CLAUDE_URL, MCP_CODEX_URL and MCP_COPILOT_URL. Reachable bridges appear in the Provider dropdown.
The three MCP Providers
- 01
Claude (MCP)
Tool
ask, default http://localhost:8960. Suggestions from Claude Code through a locally running MCP bridge. No API key in the app. - 02
Codex (MCP)
Tool
codex, default http://localhost:8961. Suggestions from Codex CLI through a locally running MCP bridge. - 03
Copilot (MCP)
Tool
ask, default http://localhost:8962. Suggestions from Copilot CLI through a locally running MCP bridge.