[ AGENT SETUP ]
Connect LONA™ to your agents.
Choose the surface that matches your workflow: hosted ChatGPT app, public Claude Code skills, registry discovery, marketplace listing, or direct remote MCP setup.
[ CONNECTION PATHS ]
Choose a distribution path you can ship now.
This proposal prioritizes public surfaces that already exist, then layers a direct MCP path for teams integrating LONA™ into their own agent products.
ChatGPT
Use the hosted ChatGPT app
The cleanest path for end users. LONA™ is already live as a ChatGPT app with MCP-backed workflows and review-ready compliance work behind it.
Claude Code
Install the public agent skills repository
The `lona-agent-skills` repository gives Claude Code and related workflows a concrete GitHub installation target today, without waiting for a directory listing.
Marketplace
Share the MCP Marketplace profile
Use the marketplace page as a public credibility layer for buyers, UX review, and external partner conversations around MCP availability.
Registry
Import from the MCP Registry or custom clients
For teams using compatible MCP clients, the registry listing and direct remote endpoint provide a vendor-neutral connection story with OAuth discovery.
Use the remote MCP endpoint for compatible clients.
This is the setup path to highlight for commercial agents, internal copilots, and custom MCP clients that can consume streamable HTTP plus OAuth metadata.
Endpoint
Authorization server
https://mcp.lona.agency/.well-known/oauth-authorization-server
Protected resource
https://mcp.lona.agency/.well-known/oauth-protected-resource
{
"mcpServers": {
"lona": {
"url": "https://mcp.lona.agency/mcp"
}
}
}Keep the page focused on the remote endpoint, not a local npm flow. Today the remote/OAuth path is the strongest public setup story to sell and demo.
[ CURRENT STATUS ]
What is already public
The commercial page should distinguish between what is live now, what is public but unofficial, and what is still under review.
ChatGPT app
LONA™ is already publicly available through the ChatGPT app surface and can be used as an immediate end-user entry point.
MCP Registry
The registry entry for `agency.lona/trading` is active and points to the production remote MCP endpoint.
MCP Marketplace
The public marketplace listing is live and already useful for external credibility, screenshots, and onboarding references.
Claude Code skills repo
The public skills repository exists today and the plugin submission has already been filed, even though the official directory path is still catching up.
[ FAQ ]
What teams ask before connecting
Is LONA™ officially listed in Anthropic's directory already?
Not yet. The public skills repository and compatible MCP connection paths are already available, but the Anthropic directory review is still pending.
Do I need to install an npm package to connect LONA™?
No. The strongest public setup path today is the remote MCP endpoint with OAuth-capable clients, so teams can connect without relying on a local npm install flow.
Which clients can connect to LONA™ today?
ChatGPT is live today, Claude Code can use the public skills repository, and compatible MCP clients can connect through the registry listing or the direct remote endpoint.
What is the best path for end users versus integration teams?
End users should start with the hosted ChatGPT app. Teams embedding LONA™ into their own agent products should use the MCP endpoint, the partner setup flow, and the onboarding contact path.
COMMERCIAL ONBOARDING
Need a managed partner path?
If you're embedding LONA™ into a commercial product or an internal agent fleet, we can help with onboarding, documentation, and service-token based integration planning.