Connection and client setup

The Potloc MCP server is a remote server reached over Streamable HTTP at one URL:

https://mcp.potloc.com

In Claude Desktop and claude.ai the server is listed in the connector directory, so there is nothing to paste. Every other client takes that URL and an OAuth sign-in. Nothing else: no API key to generate, no client id to request from us, no configuration file to hand-edit.

Claude Desktop and claude.ai

1. Open Settings → Connectors.
2. Find Potloc in the connector directory.
3. Select Connect.
4. Sign in with your Potloc account in the browser window that opens, and authorize.

The connector then appears in the tool menu of any conversation.

Claude Code

Add the server from the CLI:

claude mcp add --transport http potloc https://mcp.potloc.com

Then run /mcp in a session and select potloc to sign in.

ChatGPT

1. Open Settings → Apps & connectors → Advanced settings and turn on Developer mode. On a Business or Enterprise workspace, an admin allows custom connectors first.
2. Back in Apps & connectors, select Create.
3. Enter a name, https://mcp.potloc.com as the MCP server URL, and OAuth as the authentication.
4. Sign in with your Potloc account in the browser window that opens, and authorize.

The connector then appears in the tools menu of a conversation.

Any other MCP client

Point the client at https://mcp.potloc.com as a remote server with Streamable HTTP transport and OAuth authentication, then follow its own custom-connector flow.

A client that implements RFC 8414 discovery and RFC 7591 dynamic registration configures itself from the URL alone. One that does not will ask you for the endpoints; they are listed in Authentication.

One constraint decides whether a client can connect at all: it must use PKCE, and register as a public client with no secret. Prefer S256.

Your own code

Once you hold a token, the server is an ordinary JSON-RPC endpoint. Listing the tools:

curl -sS https://mcp.potloc.com/ \
  -H "Authorization: Bearer $POTLOC_MCP_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "MCP-Protocol-Version: 2025-06-18" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

And calling one:

curl -sS https://mcp.potloc.com/ \
  -H "Authorization: Bearer $POTLOC_MCP_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "MCP-Protocol-Version: 2025-06-18" \
  -d '{
        "jsonrpc": "2.0",
        "id": 2,
        "method": "tools/call",
        "params": { "name": "list_surveys", "arguments": { "per_page": 5 } }
      }'

Every request carries its own bearer token and the server keeps no session, so requests are independent: there is nothing to open, keep alive or resume. Server-initiated notification streams are not supported, and a method that would open one is refused with a JSON-RPC Method not found.