ArticlesInstall
How to add Agentik’s remote MCP server
You add a remote MCP server by pointing the host at https://mcp.agentik-os.com/api/mcp. agentik-os.com is the site. It is not the endpoint.
One URL
The public MCP URL is https://mcp.agentik-os.com/api/mcp. The CLI base is the same origin, path /api/cli. OAuth discovery uses the MCP origin, never the marketing apex.
Sign-in and the app stay on mcp.agentik-os.com. www.agentik-os.com redirects to the apex. That split is intentional.
How to set up the Model Context Protocol
The Model Context Protocol is the control plane. You do not install it as a second app. You add Agentik as a remote MCP server at https://mcp.agentik-os.com/api/mcp. Claude, Cursor, ChatGPT, Codex, and Hermes each have their own button. The URL does not change.
OAuth is how the host proves who you are. A paid plan, or an official OS you already unlocked, is what can() checks before a tool runs. The marketing site does not serve that call.
Per host, the same endpoint
In Claude, add it as an MCP connector. In Cursor, add it as an MCP server. In ChatGPT, use the connector flow. In Codex, add the MCP server. Hermes uses the same URL. The click labels differ. The endpoint does not.
If the host asks for a command, the install surface on agentik-os.com copies the npx line for the host you picked. Copy from there rather than from an old blog that still points at the apex.
Questions
What URL do I paste?
https://mcp.agentik-os.com/api/mcp
Why does the site redirect me when I open the MCP host in a browser?
The MCP host keeps the protocol, OAuth, sign-in, and the app. Marketing pages live on https://agentik-os.com.