Public connector docs

Penny MCP connector

Connect a supported AI client to Penny memory tools through a remote MCP server. Penny uses OAuth discovery and dynamic client registration, so clients can authorize without a static client secret.

Connector URL

Use this URL when a client asks for a remote MCP server:

https://app.mypenny.ai/mcp

Direct engine installs at https://engine.mypenny.ai/mcpare supported for backend integrations, but public install instructions should use the app URL above.

Supported clients

  • Claude.ai and Claude Desktop custom connectors
  • ChatGPT custom MCP connectors
  • Perplexity custom MCP connectors
  • Other standards-compatible remote MCP clients

Client-specific walkthroughs are available in thePenny install guide.

OAuth discovery

Penny publishes OAuth protected-resource and authorization-server metadata for the connector. Leave manual OAuth client ID and client secret fields blank unless a client UI explicitly requires otherwise.

  • Dynamic client registration is supported.
  • PKCE S256 is required for dynamically registered clients.
  • Bearer tokens are sent in the Authorization header.
  • Revoked installations are blocked on later authenticated MCP calls.

Data boundary

Penny receives explicit MCP tool calls and the data needed to answer them. Tool descriptions in the client are the contract for what each call does.

Penny does not scrape the host application's memory, conversation summaries, uploaded files, or hidden chat history.

Disconnecting

Users can disconnect a client fromSettings > Connections. Once disconnected, the installation is marked revoked. Reconnecting creates a new authorized installation through the client's normal OAuth flow.

Quick check

After connecting a client, ask it:

What tags do I have in Penny?

A successful response means the client completed OAuth and reached the authenticated MCP tools.