MCP

Choose between the public documentation server and authenticated product tools.

Influence has two separate MCP endpoints. Choose the one that matches the assistant’s task.

Server	Access and purpose
`https://docs.influence.so/mcp`	Public documentation: read and search these guides. No Influence account or product API key is required. It cannot read a workspace, upload files or publish posts.
`https://influence.so/api/mcp`	Product tools: authenticated access to the authorized workspace. Tools and actions depend on the connection’s permissions and enabled features.

Add https://docs.influence.so/mcp as a remote MCP server in a compatible client, then let the client discover its documentation tools. Client support varies; a successful connection in one client does not qualify another.

For product tools at https://influence.so/api/mcp, use the client’s supported Influence sign-in flow or a scoped API key from Influence settings. Keep the key in the client’s secret environment. Existing grants do not gain new permissions when tools are refreshed.

Product MCP mutations prepare first without _confirmationCapability or _idempotencyKey. Confirm with the same business input plus the returned _confirmationCapability and a stable caller-generated _idempotencyKey. These MCP argument names differ from the HTTP headers. Publishing still requires the exact human review described in the HTTP API guide.

Use profileGet to identify the connected account and workspace, and connectionStatusGet to inspect access and expiry. Refresh the client’s tool catalog if an authenticated read works but tools are missing. Reconnect for authentication or missing permissions; refreshing discovery alone cannot add access.