Skip to main content
Triangle
All integrations

Other MCP clients

Connect Triangle to an AI assistant or application that supports remote MCP over HTTPS and OAuth. Use automatic registration when available, or create a public OAuth app for clients that require a Client ID.

Official Other MCP clients documentation

Before you start

  • A Triangle account with an active patient profile.
  • An MCP host that supports remote Streamable HTTP servers over HTTPS. A client that only launches local stdio commands cannot connect directly.
  • OAuth 2.1 support in the client. Triangle does not use pasted API keys or static bearer tokens for patient access.
  • The callback URL used by your MCP client if it requires you to create an OAuth app manually.

Connection fields

FieldValue
MCP server URLhttps://app.trianglehealth.com/mcp
OAuth server URLhttps://app.trianglehealth.com
AuthenticationOAuth 2.1 with PKCE
Client IDLeave blank for dynamic client registration; otherwise create a public app in the developer portal
Client SecretNot required for public PKCE clients; never put a confidential client secret in a desktop or local client
ScopesLeave blank when supported — permissions are selected on Triangle’s OAuth consent screen during authorization.

Setup steps

01.Confirm your client is compatible

Check the client’s documentation before configuring Triangle. “MCP support” may refer only to local stdio servers and does not always include remote authenticated servers.

  • Look for remote MCP or Streamable HTTP transport support.
  • Confirm the client supports OAuth authorization for remote MCP servers.
  • Prefer clients that support OAuth dynamic client registration (DCR).
  • Do not connect a client you do not trust with your health information.
Screenshot coming soon

02.Add Triangle as a remote server

Create a remote MCP connection named Triangle Health and use the Triangle MCP server URL. Field names vary by client.

  • Set the server or endpoint URL to https://app.trianglehealth.com/mcp.
  • Select Streamable HTTP, remote HTTP, or automatic transport if the client asks for a transport.
  • Select OAuth authentication. Do not paste an access token or add an Authorization header.
  • Leave Client ID, Client Secret, scopes, and OAuth endpoints blank when the client supports automatic discovery and registration.
Generic MCP configuration
{
  "mcpServers": {
    "triangle-health": {
      "url": "https://app.trianglehealth.com/mcp"
    }
  }
}

03.Create a Client ID only when required

Skip this step if your client registers automatically. If it requires a Client ID, create a public PKCE app in Triangle’s developer portal and register the callback base used by the client.

  • Open https://app.trianglehealth.com/developer/apps and create a public OAuth app.
  • Enter the client’s exact https callback origin or http loopback base, including its port. Register the shortest base that safely contains the callback path.
  • Copy the Client ID into the MCP client. A public PKCE client does not use a Client Secret.
  • If the client asks for an authorization server or issuer, use https://app.trianglehealth.com.
Screenshot coming soon

04.Authorize and test the connection

Finish authorization in your browser, then make a read-only Triangle request before using tools that change data.

  • Sign in to Triangle when the client opens the authorization page.
  • Review the requested permissions and click Accept.
  • Return to the client and confirm that Triangle tools are listed.
  • Try: “Use Triangle to list my health topics.”
  • Disconnect anytime from https://app.trianglehealth.com → Settings → AI Services.
Screenshot coming soon

What you can do after connecting

  • Use compatible AI assistants and custom applications with Triangle’s remote MCP tools.
  • Authorize access without copying passwords, API keys, or long-lived tokens into the client.
  • Choose permissions for profile, topics, notes, medical records, and care-team data at consent.
  • Use dynamic client registration for supported hosts or a developer portal Client ID for public PKCE clients.
  • Revoke any connected client from Settings → AI Services in Triangle.

Troubleshooting