Connection and client setup
The Potloc MCP server is a remote server reached over Streamable HTTP at one URL:
https://mcp.potloc.comIn 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
Section titled “Claude Desktop and claude.ai”- Open Settings → Connectors.
- Find Potloc in the connector directory.
- Select Connect.
- 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
Section titled “Claude Code”Add the server from the CLI:
claude mcp add --transport http potloc https://mcp.potloc.comThen run /mcp in a session and select potloc to sign in.
ChatGPT
Section titled “ChatGPT”- Open Settings → Apps & connectors → Advanced settings and turn on Developer mode. On a Business or Enterprise workspace, an admin allows custom connectors first.
- Back in Apps & connectors, select Create.
- Enter a name,
https://mcp.potloc.comas the MCP server URL, and OAuth as the authentication. - 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.
Microsoft 365 Copilot
Section titled “Microsoft 365 Copilot”Microsoft 365 Copilot connects to Potloc through an agent built in Copilot Studio. Your organization needs Copilot Studio, and an admin may have to allow the connection in its Power Platform data policy first.
- In Copilot Studio, open or create an agent and go to its Tools page.
- Select Add a tool → New tool → Model Context Protocol.
- Enter a name and a description,
https://mcp.potloc.comas the Server URL, and OAuth 2.0 with the Dynamic discovery type as the authentication. - Select Create, then Create a new connection.
- Sign in with your Potloc account in the browser window that opens, and authorize.
- Select Add to agent.
In the tool’s settings, set Credentials to use to End user credentials. Each person who uses the agent then signs in to Potloc with their own account and sees only what their own permissions allow. With maker-provided credentials, everyone would act as the person who set up the connection.
Publish the agent to Microsoft 365 Copilot and Teams to use it there.
Any other MCP client
Section titled “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
Section titled “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.