Other MCP Clients

Propamp MCP is a standard remote MCP server, so any spec-compliant client needs nothing but the URL:


https://mcp.propamp.ai/mcp

Point the client at that URL and let it run the OAuth flow. Most clients — Cursor among them — ask for a name and a URL and handle the rest exactly as Claude does.

Transport

The server speaks Streamable HTTP: a single endpoint that accepts POST for all MCP traffic.

Method	Path	Behaviour
`POST`	`/mcp`	All MCP requests. Returns the session id in the `Mcp-Session-Id` header after `initialize`.
`DELETE`	`/mcp`	Terminates the session.
`GET`	`/mcp`	Returns `405` — there is no server-initiated stream.

Send subsequent requests with the Mcp-Session-Id header from initialize. Idle sessions expire after 60 minutes; an expired session returns 404, which is the signal to re-initialize.

ℹ️

A legacy HTTP+SSE transport also exists at GET /mcp/sse plus POST /mcp/message. It remains available for connectors created before the change, but it is not the recommended path and several clients cannot speak it at all. New integrations should use POST /mcp.

OAuth discovery

The server publishes standard discovery documents, so clients configure themselves:

Endpoint	Purpose
`/.well-known/oauth-protected-resource`	Resource metadata — identifies the resource and its authorization server
`/.well-known/oauth-authorization-server`	Authorization server metadata — endpoints, grant types, PKCE methods
`/oauth/authorize`	Authorization endpoint; serves the Propamp sign-in page
`/oauth/token`	Token exchange and refresh
`/oauth/register`	Dynamic client registration

What the flow supports:

Authorization code grant, with refresh tokens
PKCE — S256 recommended
Dynamic client registration, so a client can register itself with no manual setup
Token endpoint auth methods none and client_secret_post

An unauthenticated request to /mcp returns 401 with a WWW-Authenticate header naming the resource metadata URL. That header is how a compliant client knows where to start the sign-in — a client that ignores it will simply report the 401.

Verifying the server is reachable

This is a safe read-only check from any machine. A 401 here is the correct response — it proves the endpoint is live and asking for authorization:


curl -i -X POST https://mcp.propamp.ai/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"curl","version":"1"}}}'

Expect HTTP/2 401 with a www-authenticate header. Anything else — a timeout, a 404, a 502 — points at a network or DNS problem on your side rather than at your Propamp account.

n8n and other automation platforms

Connecting a shared automation platform, where one connection serves many users, works differently from a single-user AI client: it needs per-user token handling rather than one OAuth sign-in. Email [email protected] and we will walk you through the setup for your platform.