Pulsar MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TOPIC_NAME | No | Default topic name | |
| PULSAR_TOKEN | No | JWT token for authentication | |
| SUBSCRIPTION_NAME | No | Default subscription name | pulsar-mcp-subscription |
| SUBSCRIPTION_TYPE | No | Subscription type (Exclusive, Shared, Failover, Key_Shared) | Shared |
| PULSAR_SERVICE_URL | No | Pulsar broker service URL | pulsar://localhost:6650 |
| PULSAR_WEB_SERVICE_URL | No | Pulsar web service URL | http://localhost:8080 |
| IS_TOPIC_READ_FROM_BEGINNING | No | Whether to read from beginning | false |
| PULSAR_TLS_TRUST_CERTS_FILE_PATH | No | Path to TLS trust certificates file | |
| PULSAR_TLS_ALLOW_INSECURE_CONNECTION | No | Allow insecure TLS connection | false |
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 | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pulsar_publishB | Publish a message to a Pulsar topic |
| pulsar_consumeB | Consume messages from a Pulsar topic |
| pulsar_create_topicC | Create a new Pulsar topic |
| pulsar_delete_topicB | Delete an existing Pulsar topic |
| pulsar_list_topicsB | List all topics in the Pulsar cluster |
| pulsar_topic_statsB | Get statistics and metadata about a topic |
| pulsar_list_connectorsA | List all connectors of specified type (source or sink) |
| pulsar_connector_statusB | Get the status of a specific connector |
| pulsar_connector_configB | Get the configuration of a specific connector |
| pulsar_all_connectorsB | Get all connectors organized by type (source and sink) |
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 10 tools
All tools have clearly distinct purposes. The slight overlap between 'pulsar_all_connectors' and 'pulsar_list_connectors' is resolved by descriptions: one returns all connectors organized by type, the other lists connectors of a specified type.
All tool names follow the consistent pattern 'pulsar_<verb>_<noun>' (e.g., create_topic, list_connectors). The naming is uniform and predictable, aiding agent selection.
With 10 tools, the server is well-scoped for a Pulsar cluster management interface. Each tool serves a necessary function without redundancy.
The tool set covers core topic operations (CRUD, publish, consume, stats) and connector inspection. However, it lacks connector creation/deletion, which may be needed for full lifecycle management.