MCP

Other MCP Clients

Connect MCP-capable developer tools and agent clients using the same authentication, tool, and connection-testing model.

Connect MCP-capable developer tools and agent clients using the same Kommon Poll authentication, connection testing, and tool-use model.

Platform details checked: 2026-09-02.

Use this page as the compact setup guide for developer clients that accept remote HTTP MCP servers. Link back to the canonical authentication and tool reference pages instead of duplicating the full data model in each client guide.

1. Best-Fit Clients

Best-fit client types include:

  • Coding assistants.
  • IDE agent environments.
  • Local MCP clients.
  • Workflow agents.
  • Analysis tools.
  • Other developer clients that accept remote HTTP or Streamable HTTP MCP servers.

Use the Kommon Poll API instead when a workflow needs deterministic scheduling, strict retries, long-running exports, or application-owned credentials.

2. Generic Setup Pattern

  1. Open the MCP client's server or connector configuration.
  2. Add the Kommon Poll MCP server URL:
https://mcp.kommonpoll.com/mcp
  1. Choose the remote HTTP or Streamable HTTP transport expected by that client.
  2. Configure OAuth from client discovery when available.
  3. Save or reload the client configuration.
  4. Complete Kommon Poll sign-in and team selection.
  5. Check that Kommon Poll tools are listed.
  6. Run a safe saved-search listing prompt.

3. Example Configuration Shape

Use the exact format required by the client. A generic remote HTTP MCP entry may look like:

{
  "mcpServers": {
    "kommon_poll": {
      "type": "http",
      "url": "https://mcp.kommonpoll.com/mcp"
    }
  }
}

For Claude Code, the equivalent command is:

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

Do not put API keys, OAuth access tokens, client secrets, or authorization headers directly in shared configuration files.

4. Test Prompts

Show me the Kommon Poll tools available in this MCP client.
List the Kommon Poll saved searches this connection can access.
Use the selected saved search to summarize the last 7 days. State the tool calls, filters, and limitations.

5. Client-Specific Checklist

For each client, document:

  • Config file or settings location.
  • Remote MCP URL field.
  • Supported transport.
  • OAuth support.
  • Whether per-tool approvals are required.
  • How to reload or restart the client.
  • How to view available tools.
  • How to remove or revoke the connection.
  • Known limitations.

6. Troubleshooting

Issue What to check
Client cannot parse config Validate JSON, YAML, or TOML syntax based on the client.
Server is unreachable Confirm URL, transport, network access, and proxy settings.
Auth cannot complete Confirm the client supports OAuth discovery or configure the Kommon Poll OAuth endpoints manually if the client allows it.
Tools are listed but not used Ask explicitly to use Kommon Poll and provide a clear saved-search name.
Local client needs deterministic automation Use the Kommon Poll API instead of MCP.