Use an MCP client that supports Streamable HTTP and MCP OAuth 2.1 discovery. Enter only the endpoint URL. The client registers with the Formlism authorization server, then opens a browser for Formlism sign-in and explicit capability consent. Do not add a Developer API key or a static Authorization header.
Connection values
| Name | Value |
|---|---|
| URL | https://mcp.formlism.com/mcp |
| Transport | streamable_http |
| Authorization | OAuth 2.1 (automatic discovery) |
Example configuration
{
"mcpServers": {
"formlism": {
"url": "https://mcp.formlism.com/mcp"
}
}
}Consent
Review the client name and requested Formlism capabilities in the browser. Keep publish, delete, and response access disabled unless the client genuinely needs them. Tokens are audience-bound to the production or UAT MCP endpoint and cannot be reused as Developer API credentials.
Health check
The endpoint accepts MCP JSON-RPC over POST. Plain GETand DELETE requests return a JSON-RPC method-not-allowed response.