MCP

Claude Setup

Connect Kommon Poll MCP to Claude where supported and use Projects, Research, and reusable monitoring instructions.

Connect Kommon Poll MCP to Claude where supported and use Claude conversations, Projects, Research, and reusable monitoring instructions.

Last verified: confirm before publishing.

Claude support for remote MCP connectors, tool approvals, Projects, Research workflows, Skills, and developer surfaces can vary by plan, organization policy, and product mode. Verify the exact setup flow before publishing screenshots or plan-specific claims.


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

Use the current Claude connector or MCP setup flow.

  1. Open Claude settings for connectors, tools, or organization-managed integrations.
  2. Add Kommon Poll using the MCP server details provided by Kommon Poll.
  3. Start authorization.
  4. Sign in to Kommon Poll.
  5. Select the team or workspace.
  6. Review scopes and approve.
  7. Return to Claude.
  8. Enable Kommon Poll tools where the conversation, project, or research mode requires explicit tool selection.

Use screenshots after the final Claude UI is verified.


3. Verify 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.

4. 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.

5. Skills And Research Workflows

Where supported, 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 the client supports those tools. Label Kommon Poll-observed data separately from external research.


6. 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.

Use the same OAuth, scope, and team-selection rules as normal Claude conversations.


7. Troubleshooting

Issue What to check
Connector cannot be added Confirm plan, organization policy, and supported MCP transport.
Tools are disabled Enable Kommon Poll tools in the current conversation, Project, or Research mode.
Wrong team is visible Reconnect and select the intended Kommon Poll team.
Claude does not call the tool Ask explicitly to use Kommon Poll and provide the saved-search name.
Scheduling is requested Verify native scheduling support. If unavailable, use an external automation or the API.