Other MCP clients

Pollaris works with MCP clients that support both:

1. The Streamable HTTP transport.
2. A custom HTTP Authorization header or Bearer-token setting.

Generic connection profile

Name: Pollaris
Transport: Streamable HTTP
URL: https://mcp.pollaris.cc/mcp
Authorization: Bearer plr_mcp_v1_REPLACE_ME

If the client accepts JSON, its shape is commonly similar to:

{
  "mcpServers": {
    "pollaris": {
      "type": "http",
      "url": "https://mcp.pollaris.cc/mcp",
      "headers": {
        "Authorization": "Bearer plr_mcp_v1_REPLACE_ME"
      }
    }
  }
}

The exact property names and config-file location belong to the client, not the MCP protocol. Check that client's documentation before copying this generic shape.

HTTP behavior

• Send the key on every MCP HTTP request as Authorization: Bearer <key>.
• Do not use X-API-Key, query parameters, cookies, or tool arguments.
• The endpoint returns JSON responses and is stateless; clients must not depend on a persistent Pollaris session ID.
• Request bodies larger than 1 MiB are rejected.
• Browser-based clients must originate from an origin allowed by the Pollaris deployment.

Compatibility test

After connecting, the client should initialize the server as Pollaris Form Authoring and discover these tools:

list_workspaces
list_forms
get_form_draft
compile_form_dsl
validate_form_definition
generate_form_preview
create_form_draft
save_form_draft

Call list_workspaces first. If it succeeds, transport and authentication are working. If the client supports tools but cannot attach a custom Bearer token to Streamable HTTP requests, it cannot currently connect to Pollaris.