Claude Setup

Connect Kommon Poll MCP to Claude with custom connectors, Claude Desktop, Claude Code, Projects, Research, and reusable monitoring instructions.

Platform details checked: 2026-09-02.

Claude custom connectors using remote MCP are available on Claude, Cowork, and Claude Desktop for Free, Pro, Max, Team, and Enterprise plans. Free users are limited to one custom connector. Team and Enterprise organizations require an Owner or Primary Owner to add a custom connector before members connect and enable it individually.

1. What This Enables

When connected, Claude can use Kommon Poll tools to:

• Discover saved searches available to the authorized user or team.
• Retrieve overview analytics for a selected saved search.
• Retrieve mentions for examples and qualitative evidence.
• Produce briefs, research summaries, report drafts, and monitoring analyses.
• Apply standing project instructions for repeatable brand, competitor, or campaign workflows.

2. Connect Kommon Poll In Claude

Use Claude's custom connector flow for remote MCP.

1. Open Customize > Connectors.
2. Select the plus button next to Connectors.
3. Choose Add custom connector.
4. Enter Kommon Poll as the connector name.
5. Enter the remote MCP server URL:

https://mcp.kommonpoll.com/mcp

1. Leave advanced OAuth client ID and client secret fields empty unless your organization has issued static OAuth credentials for Claude.
2. Add the connector.
3. Follow the connection flow, sign in to Kommon Poll, select the team or workspace, review scopes, and approve access.
4. Enable Kommon Poll tools in the conversation, Project, Research workflow, or Cowork task where tool selection is explicit.

3. Connect Kommon Poll In Claude Code

For Claude Code, add the remote HTTP MCP server:

claude mcp add --transport http kommon_poll https://mcp.kommonpoll.com/mcp

Then start Claude Code and open the MCP panel:

/mcp

Complete the browser sign-in flow from the panel, or run:

claude mcp login kommon_poll

Use claude mcp get kommon_poll to inspect the stored configuration and connection status.

4. Test The Connection

List the Kommon Poll saved searches available to this connection and identify which one looks like the main brand monitoring search.

Use the main brand monitoring saved search and summarize the last 7 days. Include the date range, filters, and Kommon Poll tools used.

5. Claude Projects Pattern

For a Claude Project focused on monitoring, add instructions like:

Use Kommon Poll as the primary evidence source for claims about monitored conversation. When the saved search is ambiguous, list available searches and ask which one to use. For every analysis, state the search, period, timezone, filters, and limitations. Use overview data for metrics and mention records for examples. Separate findings, interpretation, and recommendations.

Recommended project documents:

• Brand or campaign brief.
• Competitor list.
• Reporting template.
• Escalation definitions.
• Tone and audience guidelines.

6. Skills And Research Workflows

Create reusable workflows for:

• Weekly executive briefs.
• Crisis monitoring.
• Competitor summaries.
• Voice of Customer clustering.
• Media and PR briefings.
• Report drafting.

Research workflows can combine Kommon Poll conversation evidence with other sources when those tools are enabled. Label Kommon Poll-observed data separately from external research.

7. Developer Use

For developer-oriented Claude clients or coding environments, Kommon Poll MCP can support:

• Analysis scripts.
• Report-generation pipelines.
• Notebook-style exploration.
• Data transformation from mention pages.
• Prompt and workflow testing.

Claude remote connectors originate from Anthropic's cloud infrastructure, not the local device. The Kommon Poll MCP endpoint must remain reachable over the public internet. Local Claude Desktop MCP servers configured with claude_desktop_config.json are separate from this remote connector pattern.

8. Troubleshooting