Skip to main content
Glama

Pursuit MCP

MCP server providing Pursuit integration for PureScript documentation search.

Features

  • Search Pursuit for PureScript functions, types, modules, and packages

  • Type signature search support

  • Access to comprehensive PureScript package documentation

Related MCP server: Hoogle MCP Server

Usage

MCP Client Configuration

Add to your MCP client configuration (e.g., Claude Desktop):

{
  "mcpServers": {
    "pursuit": {
      "command": "nix",
      "args": ["run", "github:gawakawa/pursuit-mcp", "--"]
    }
  }
}

Available Tools

search_pursuit

Search Pursuit for PureScript functions, types, and documentation.

Parameters:

  • query (string): Search query (function name, type signature, or keyword)

  • limit (integer, optional): Maximum number of results to return (default: 10)

Examples:

  • Function name search: map

  • Type signature search: (a -> b) -> f a -> f b

  • Module search: Data.Array

  • Package search: prelude

Response Format: Each result includes:

  • package: Package name (e.g., "purescript-prelude")

  • version: Package version

  • info: Result type and metadata

    • For declarations: includes module, title, type signature

    • For packages: includes deprecation status

    • For modules: includes module name

  • text: Plain text documentation

  • url: Direct link to the documentation

  • markup: HTML-formatted documentation (optional)

License

MIT

Available Tools

1 tool
search_pursuitB

Search Pursuit for PureScript functions, types, and documentation.

Args: query: Search query (function name, type signature, or keyword) limit: Maximum number of results to return (default: 10)

Returns: Formatted search results from Pursuit as JSON string

Inputs: query (required), limit. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.3/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The tool has a single, clear purpose: searching the Pursuit database for PureScript-related content. An agent cannot misselect between non-existent alternatives.

    Naming Consistency5/5

    The single tool name 'search_pursuit' follows a consistent verb_noun pattern, using snake_case. There are no other tools to compare against, so no inconsistency can exist. The naming is clear and predictable for its isolated context.

    Tool Count2/5

    A single tool is too few for a server named 'Pursuit MCP', which suggests broader functionality related to PureScript's Pursuit ecosystem. While the tool covers search, obvious gaps exist (e.g., no tools for browsing packages, viewing documentation details, or managing favorites), making the server feel thin and incomplete for its implied domain.

    Completeness2/5

    The tool set is severely incomplete for a Pursuit-related server. It only provides search functionality, missing essential operations like retrieving detailed package information, listing categories or modules, or accessing documentation beyond search results. This creates significant gaps that will limit agent capabilities in handling PureScript queries effectively.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers