Other MCP Clients

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

Last verified: confirm before publishing for each client.

MCP client behavior changes quickly. Treat this page as a compact setup guide for verified developer clients, and link back to the canonical authentication and tool reference pages instead of duplicating details.

1. Best-Fit Clients

This page can cover MCP-capable tools such as:

• Coding assistants.
• IDE agent environments.
• Local MCP clients.
• Workflow agents.
• Analysis tools.
• Other developer clients where verified support exists.

Only publish client-specific steps after confirming the client's current MCP support, transport type, OAuth behavior, and configuration location.

2. Generic Setup Pattern

1. Open the MCP client's server or connector configuration.
2. Add the Kommon Poll MCP server URL provided by Kommon Poll.
3. Choose the supported transport type.
4. Configure OAuth if the client supports remote OAuth.
5. Save or reload the client configuration.
6. Complete Kommon Poll sign-in and team selection.
7. Verify that Kommon Poll tools are listed.
8. Run a safe saved-search listing prompt.

3. Example Configuration Shape

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

{
  "mcpServers": {
    "kommon-poll": {
      "type": "remote",
      "url": "https://mcp.kommonpoll.example/mcp",
      "auth": "oauth"
    }
  }
}

Replace the example URL with the production MCP server URL provided by Kommon Poll.

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

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

Before publishing instructions for a client, confirm:

• 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