Connect to HQ with MCP
HQ exposes an authenticated Model Context Protocol endpoint:
https://seo.pulpsense.com/api/mcpUse an MCP-compatible client that supports HTTP servers and your selected authentication method. The server follows the MCP initialization and tool discovery protocol; this URL is not an anonymous JSON tool-list endpoint.
Personal token connection
Section titled “Personal token connection”Create a personal API token in HQ, then configure your client with
the server URL and an Authorization bearer header.
{ "url": "https://seo.pulpsense.com/api/mcp", "headers": { "Authorization": "Bearer YOUR_HQ_TOKEN" }}This is the connection information, rather than a universal client config file. Map it to your client’s HTTP-server settings and store the token using its supported secret mechanism.
After connecting, initialize the MCP session and call tools/list. The server
exposes the operations your credential is permitted to use. Tool schemas
describe each operation’s arguments; use those current schemas when calling
tools/call.
Hosted OAuth connection
Section titled “Hosted OAuth connection”For the supported ChatGPT hosted connection, use these settings when prompted:
| Setting | Value |
|---|---|
| Server | https://seo.pulpsense.com/api/mcp |
| Client type | User-defined OAuth client |
| Client ID | pulpsense-chatgpt-hq |
| Token endpoint authentication | none |
| Scopes | hq:mcp offline_access |
An HQ administrator must register the exact callback displayed by the current connector draft through Settings → Hosted connection. Sign in and consent with your approved HQ account after the registration matches. A changed callback requires administrator configuration before connecting again.
Access and operations
Section titled “Access and operations”Your connection inherits your current HQ role and resource assignments. Personal tokens also retain their selected permission ceiling. Connecting does not grant access to other businesses, financial data or publishing operations you were not already allowed to use.
Discover the available tools for tasks, business context, delivery, reporting, content and other enabled HQ features. Treat each tool’s current schema and result as its operation contract. A successful content save or completed task does not itself establish that a website was published.
For agency content integrations confined to one website, use the Website Publishing API instead.