Other clients
Copilka’s server is standard remote MCP over HTTP, with OAuth for signing in, so clients other than Claude can connect. Claude on the web, in the desktop app and in Claude Code are the ones Copilka is tested with; anything else has to meet the requirements below.
The server
Section titled “The server”- Address:
https://mcp.copilka.app/mcp. - Transport: Streamable HTTP, without sessions. Requests are POSTs; there is no separate event stream to subscribe to. Both the current MCP revision and the 2025 revision are answered.
- Discovery:
https://mcp.copilka.app/.well-known/oauth-protected-resourceand/.well-known/oauth-authorization-serverdescribe the server and its authorization endpoints,/authorize,/tokenand/register.
Signing in
Section titled “Signing in”The server is its own OAuth 2.1 authorization server. A client must:
- register itself at
/registerbefore its first sign-in, giving its redirect address and a name. The name is what the connect page shows you, and what Settings → Connections calls the connection; a client that gives none is an assistant. - use a redirect address that is
https, orhttponlocalhostor127.0.0.1. A custom scheme such asmyapp://is refused. - use PKCE, with the S256 method.
- accept an access token that lasts a year with no refresh token. After a year, the person connects again.
Sign-in on the connect page is by email code, to the address of the Copilka account. The granted permissions are the ones ticked on the page, not the ones the client asked for.
Requests from a browser
Section titled “Requests from a browser”Requests that carry a browser Origin are accepted only from Claude’s own sites. A web app running anywhere else, including on localhost, is refused with 403. Requests without an Origin, which is what desktop apps, command-line tools and servers send, are accepted. The OAuth endpoints do not answer cross-origin browser requests at all.
So a browser-only MCP tool cannot connect directly. The MCP Inspector works in its proxy mode, which sends no Origin.
Not supported
Section titled “Not supported”- ChatGPT. Copilka does not offer the
searchandfetchtools ChatGPT’s connectors require. - A local server over stdio: the server is remote only.
- Personal access tokens: there is no way to make a long-lived token yourself. Signing in through the connect page is the only way in.
After connecting
Section titled “After connecting”Whatever the client, it appears on Settings → Connections under its registered name, and Disconnect there ends it. See Connect Claude and Permissions and safety.