Perplexity-Comet-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| comet_connectA | Connect to Comet browser (auto-starts if needed) |
| comet_askA | Send a prompt to Comet/Perplexity and wait for the complete response (blocking). Ideal for tasks requiring real browser interaction (login walls, dynamic content, filling forms) or deep research with agentic browsing. |
| comet_pollA | Check agent status and progress. Call repeatedly to monitor agentic tasks. |
| comet_stopA | Stop the current agent task if it's going off track |
| comet_screenshotB | Capture a screenshot of current page |
| comet_tabsA | View and manage browser tabs. Shows all open tabs with their purpose, domain, and status. Helps coordinate multi-tab workflows without creating duplicate tabs. |
| comet_modeA | Switch Perplexity search mode. Modes: 'search' (basic), 'research' (deep research), 'labs' (analytics/visualization), 'learn' (educational). Call without mode to see current mode. |
| comet_uploadA | Upload a file to a file input on the current page. Use this to attach images, documents, or other files to forms, posts, or upload dialogs. The file must exist on the local filesystem. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose with no ambiguity. For example, comet_ask is for sending prompts, comet_connect handles browser connection, comet_mode switches search modes, and comet_upload manages file uploads. The descriptions clearly differentiate their functions, preventing misselection.
All tool names follow a consistent 'comet_' prefix with descriptive suffixes (e.g., ask, connect, mode, poll). This verb_noun or action-based pattern is uniform across all eight tools, making them predictable and easy to understand.
With 8 tools, the count is well-scoped for a browser interaction and research assistant server. Each tool serves a specific role in managing browser sessions, handling tasks, and interacting with content, with no redundancy or missing core functions.
The tool set provides complete coverage for browser-based research and interaction tasks. It includes connection management (comet_connect), task execution (comet_ask, comet_poll, comet_stop), mode switching (comet_mode), tab management (comet_tabs), and file handling (comet_upload, comet_screenshot), leaving no obvious gaps.