Perplexity Comet MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COMET_PATH | No | Custom path to Comet executable. Default: Auto-detected | |
| COMET_PORT | No | CDP debugging port. Default: 9223 | 9223 |
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
The tools cover distinct actions: connecting, asking, polling, stopping, screenshotting, tab management, mode switching, and file upload. However, ask, poll, and stop have some overlap in the task lifecycle, and poll's role is unclear without an explicit async task starter, which could cause misselection.
All tools share the comet_ prefix and use lowercase single-word actions, which is readable. However, comet_tabs and comet_mode are noun-based rather than verb-based, breaking the otherwise verb-like pattern.
8 tools is appropriate for a browser control/agent interface, covering the main operations without redundancy or bloat.
The surface covers connection, interaction, monitoring, control, and file upload, which are the core operations. Minor gaps like explicit navigation or tab close are handled indirectly through ask/manage, so agents can still achieve workflows.