pulsar-edit

This MCP server provides an interface for controlling the Pulsar Editor via an LLM-enabled chat experience. It exposes text-editing and file-navigation capabilities that map to Pulsar actions, such as replacing text, inserting lines, deleting lines, opening files, and querying document metadata. The server is designed to be used with a chat client (either built-in Pulsar chat or an external client like AnythingLLM) so the assistant can perform scripted editing tasks, retrieve context around matches, and apply targeted edits within the current project. Supported commands cover a broad range of editor interactions, including Replace Text, Get Context Around, Find Text, Replace Document, Insert Line, Delete Line, Get Document, Open File, and navigation helpers like Get Filename and Get Project Files. These commands are intended to be invoked by the MCP protocol, allowing your LLM client to send a structured request and receive a structured response containing the relevant editor state or results.

Prerequisites:

• Pulsar editor installed and accessible
• Node.js (for the MCP server runtime) or an environment capable of running the chosen runtime
• Basic familiarity with MCP (Model Context Protocol) and your preferred MCP client

Installation steps:

1. Ensure Pulsar is installed and the MCP Server feature is enabled in the editor, and that you have a running LPC (Listening MCP) endpoint as described in the Pulsar docs.

2. Install the MCP server package (as documented in the repository you provided). Example (adjust per your environment):

   ppm install https://github.com/drunnells/pulsar-edit-mcp-server

3. Place the MCP server in a known location and ensure the server can be started by Node.js using the path to the server entry point. If using the suggested placeholder path, replace it with your actual built server path.

4. Start the MCP server. For example, if you use Node.js directly:

   node path/to/server.js

5. In Pulsar (or your MCP client), configure the MCP server URL to http://localhost:3000/mcp (adjust port/path if you customize it). Ensure the server is reachable from the Pulsar editor.

6. Test a basic request from your MCP client to verify connectivity and basic command execution.

Notes:

• If you later ship a Docker, npx, or other runtime configuration, you can adapt the mcp_config accordingly.
• The README indicates this server is experimental; proceed with testing in a safe project workspace.

Tips and considerations:

• This server is described as an early, experimental integration for Pulsar with LLMs. Expect incomplete feature parity and potential instability during development.
• Ensure the MCP client you use is configured to connect to the server at the specified URL (default http://localhost:3000/mcp). The client’s mcpServers config should include the server entry with type: "streamable" or as appropriate for your client.
• Environment variables like PULSAR_HOST and PULSAR_PORT may need adjustment to match your Pulsar installation. Update these in the mcp_config env section accordingly.
• When building or debugging, log the MCP requests and responses to understand command behavior and edge cases (e.g., multi-file edits, large document edits).
• If you switch from the built-in Pulsar chat to an external client (AnythingLLM, etc.), ensure the client supports the supported commands and respects the expected input/output structure.