Runtime configuration
BYOK · MCP over HTTPS
This is your own key (BYOK) for a chat completion‑style endpoint.
MCP endpoints
Tools
Expected: an HTTPS endpoint that speaks MCP‑style JSON (e.g. listTools, callTool).
MCP servers are treated as tool providers. The agent can decide when to call them based on the conversation.
Idle · configure your runtime and MCP endpoints.
Tip: nothing is stored server‑side; this is a pure client app.
Chat / agent interface
Agent: ready
System
Bring your own key, wire up MCP endpoints, and talk to your agent.
Configurable runtime MCP tools available when registered
Idle
Tools: 0 · MCP endpoints: 0