Skip to main content
Glama
161,728 tools. Last updated 2026-05-30 05:34

"PureScript" matching MCP tools:

  • Extract 'where' clauses from PureScript functions to identify local helper functions and variables, aiding in understanding function implementation details.
    MIT
  • Verify running IDE server processes to prevent resource conflicts. Checks Tree-sitter parser status and purs IDE server availability. Use before starting new IDE servers to ensure no duplicate processes.
    MIT
  • Launch the PureScript IDE server to enable type checking, auto-completion, and error detection. Automatically stops existing servers to prevent conflicts, selects a random port, and requires an absolute project path. Essential for pursIde* tools functionality.
    MIT
  • Gracefully shut down the PureScript IDE server using its built-in quit command, ensuring resource release without abrupt termination.
    MIT
  • Clear all loaded modules from the PureScript IDE server's memory to aid in switching projects or handling major code changes. Ensures a clean slate before reloading with pursIdeLoad.
    MIT

Matching MCP Servers

  • Load PureScript modules into the IDE server to enable type checking and code completions. Essential first step after starting the IDE server for proper functionality of other development tools.
    MIT
  • Verify MCP server functionality by sending a message and receiving an immediate echo response. A simple test tool to ensure server communication is working correctly.
    MIT
  • Identify all instances where a specific function, type, or value is used across a PureScript project using the PureScript MCP Server. Ensures accurate refactoring by showing the impact of changes across modules.
    MIT
  • Recompile a single PureScript module to check for errors, providing immediate feedback during code editing. Requires IDE server and loaded modules, faster than full project rebuild.
    MIT
  • Extract PureScript module names from files or code snippets to analyze code structure without requiring an IDE server. Supports absolute file paths or direct code input.
    MIT
  • Extract and filter top-level declarations in PureScript code to retrieve names, types, and full source code. Supports regex-based filtering for precise analysis of functions, data types, or classes.
    MIT
  • Extract top-level declaration names (functions, data types, type classes) from PureScript code or a file. Enables code analysis without requiring an IDE server, simplifying development tasks.
    MIT
  • Analyze PureScript code to extract all import statements, revealing external module dependencies. Works independently of IDE servers, supporting absolute file paths or direct code input.
    MIT
  • Extract function names from PureScript code snippets, focusing solely on functions while excluding data types and classes. Ideal for quick code analysis and understanding.
    MIT
  • Retrieve the current working directory used by the IDE server to understand project context. Requires the IDE server to be running. Part of the PureScript MCP Server tools for efficient development workflows.
    MIT
  • Retrieve type signatures of functions, variables, or values in PureScript code to understand input and output details. Requires an active IDE server and loaded modules for accurate lookups.
    MIT
  • Retrieve available modules or import lists in a PureScript project to analyze structure and dependencies. Requires IDE server running with modules loaded.
    MIT
  • Search PureScript documentation for functions, types, and packages using the Pursuit search engine to find relevant code examples and API references.