Skip to main content
Conical

Other MCP clients

Forum’s connector is a standard remote MCP server, so other MCP clients can use it too. We have tested it with Claude. We have not verified any other client, so treat this page as the technical contract, not a promise that a particular product works.

For what a connection is and the permissions you control, see Connect your AI.

Connection details

Server URLhttps://forum.conical.tech/mcp
TransportStreamable HTTP, stateless (no session)
AuthenticationOAuth 2.1 authorization code flow with PKCE (S256), or an API key (below)
OAuth scopesrecord:read, record:write

Signing in with OAuth

A client connects the way the MCP authorization specification describes:

  1. An unauthenticated request to /mcp returns 401 with a WWW-Authenticate header whose resource_metadata points at Forum’s protected resource metadata.
  2. The client reads that, then Forum’s authorization server metadata at https://forum.conical.tech/.well-known/oauth-authorization-server.
  3. The user signs in to Forum and approves the consent screen, where they choose permissions and domains.
  4. The client receives an access token and a refresh token (refresh tokens rotate on use).

Client registration

  • Client ID Metadata Documents (CIMD) are supported. The client’s client_id is an HTTPS URL that serves its metadata, including its redirect URIs.
  • Dynamic Client Registration (DCR) is currently turned off. A client that can only register itself through DCR cannot connect today.

If your client needs a different registration method, email contact@conical-tech.com.

Whichever method a client uses, the user’s account still needs connector access enabled.

Signing in with an API key

A client that can send an Authorization header can use a Forum API key instead of OAuth:

  1. In Forum, go to Account → API Keys and generate a key. It starts with ak_.
  2. Send it as Authorization: Bearer ak_... on requests to the server URL.

An API key has the full access of your account: it is not limited by the read/write and domain choices on the OAuth consent screen. Treat it like a password, give it a recognizable label, and revoke it from the same page when you no longer need it. Prefer OAuth where your client supports it.

What the client gets

The same tools as any other connection, filtered by what was granted. See Connector tools. On connect, the server also returns short instructions that tell the assistant when to use your record and what never to do (for example, never reveal personality scores).

Not covered

We do not currently document step-by-step setup for other products. When we have tested a client, it will get its own page.