Use Logling with an MCP client
Logling provides a private remote Model Context Protocol (MCP) server. A compatible client can use it to inspect the schemas available to your account, find and read your entries, and create new entries from a conversation.
For client-specific steps, see Connect Logling to ChatGPT or Connect Logling to Claude Code.
Check that your client is compatible
Your client needs all of the following:
- A remote Streamable HTTP or HTTP MCP connection, rather than a local stdio-only server.
- OAuth authorization-code sign-in with PKCE, and support for the OAuth resource indicator.
- OAuth metadata discovery, or fields for manually entering the authorization details below.
- A supported way to identify itself to Logling: a built-in client profile, or a user-supplied OAuth client ID.
Logling does not offer Dynamic Client Registration, API-key authentication, or a shared client secret. A client that requires one of those options cannot connect yet.
Add the MCP server
In your client, add a remote MCP server or connector.
Choose HTTP, Streamable HTTP, or the equivalent remote transport. Do not choose SSE, WebSocket, or local stdio.
Enter this server URL:
https://mcp.logling.com/mcpSelect OAuth when your client asks how to authenticate. Do not paste an access token or password into the server configuration.
The client should discover the remaining OAuth settings automatically. If it asks for them, use these values:
| Setting | Value |
|---|---|
| Protected-resource metadata | https://mcp.logling.com/.well-known/oauth-protected-resource/mcp |
| Authorization-server metadata | https://auth.logling.com/.well-known/oauth-authorization-server |
| Authorization URL | https://auth.logling.com/v1/oauth/authorize |
| Token URL | https://auth.logling.com/v1/oauth/token |
| Resource | https://mcp.logling.com/mcp |
| Token endpoint authentication | none |
Identify your client
Logling needs to recognize the client before it can send you to sign in. Choose the option that matches your MCP client:
| Client | What to do |
|---|---|
| ChatGPT | Follow the ChatGPT guide, which supplies ChatGPT’s registered client ID and callback URL. |
| Claude Code | Follow the Claude Code guide. Claude Code uses Logling’s supported client-metadata profile. |
| Another compatible client | Create a personal OAuth application as described below, then enter its client ID in the client’s OAuth settings. |
Register a personal OAuth application
For a client without a built-in Logling profile:
- Sign in to Logling and open Settings.
- Under Personal OAuth applications, enter a descriptive application name.
- Enter the client’s callback address exactly as it reports it, one HTTPS redirect URI per line.
- Select Register application, then copy the generated client ID into the MCP client’s OAuth client-ID setting.
- Leave the client-secret field empty. Personal applications do not use a client secret.
Only the Logling account that registered a personal application can authorize it. A personal application’s redirect URIs must be exact HTTPS URLs; a desktop client that only supplies a localhost callback needs its own supported profile instead.
Approve the requested access
Complete the browser sign-in flow when your MCP client opens it. For full Logling functionality, approve these scopes:
| Scope | Allows the client to |
|---|---|
schemas:read | Inspect the available entry schemas and their fields. |
entries:read | Find tags and entries, and read matching entry data. |
entries:write | Create new schema-valid entries. |
The connection cannot update or delete entries. Logling identifies the account from the OAuth grant, so a client never needs your Logling user ID.
Use Logling effectively
Start by asking the client which Logling schemas are available. Before it creates a structured entry, it should retrieve the versioned schema it plans to use and ask you for any required information it does not have.
You can then ask it to:
- Find entries by a tag, date range, schema, or text in the entry name or description.
- Retrieve a matching entry after a search returns it.
- Create a new entry with tags and schema-valid data.
When you describe a relative date such as “yesterday,” confirm that the client resolves it to the intended calendar date before it creates an entry.
Manage or remove access
Disconnect the server in your MCP client when you no longer use it. To immediately invalidate an authorization, open Settings in Logling and remove the client from Connected applications.
If you created a personal OAuth application, revoking or changing it in Personal OAuth applications also invalidates its existing authorizations.
Troubleshoot a connection
- The client asks to dynamically register itself: Logling does not support Dynamic Client Registration. Use a built-in profile or register a personal OAuth application, if the client lets you enter a client ID.
- Logling rejects the callback URL: Copy the redirect URI exactly from the client. Personal applications accept HTTPS callback URLs only.
- The client connects but cannot find or create entries: Reconnect and approve the scopes it needs. Existing authorizations keep their previously granted scopes.
- The client asks for an API key or client secret: It is not compatible with Logling’s OAuth connection.
Get what you needed?