MCP.so
Sign In

@niklaserik/effect-mcp

@niklaserik

About @niklaserik/effect-mcp

A mcp server for fetching the Effect-ts documentation

Basic information

Category

Other

License

MIT

Runtime

node

Transports

stdio

Publisher

niklaserik

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "effect-mcp": {
      "command": "node",
      "args": [
        "dist/index.js",
        "#",
        "stdio",
        "transport"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is @niklaserik/effect-mcp?

It is a Model Context Protocol (MCP) server that fetches the most current documentation from the Effect ecosystem. It integrates with AI assistants and tools like VS Code to provide real-time access to Effect package documentation for developers.

How to use @niklaserik/effect-mcp?

Install via pnpm add @niklaserik/effect-mcp, then build and run the server (node dist/index.js) over stdio transport. Connect with an MCP client (e.g., VS Code or MCP Inspector) and list resources or call tools like effect-documentation or effect-doc-links.

Key features of @niklaserik/effect-mcp

  • Real-time documentation access for Effect ecosystem
  • Supports both stable and experimental packages
  • Context-aware package detection based on imports
  • Seamless integration with VS Code and MCP clients
  • In-memory TTL cache (~10 minutes)
  • Lightweight retry on transient fetch errors

Use cases of @niklaserik/effect-mcp

  • Query an AI assistant for up-to-date API documentation on an Effect package
  • Automatically retrieve relevant docs for imported Effect packages in a code editor
  • Fetch documentation for multiple Effect libraries at once for a quick reference
  • Get plain documentation URIs to follow in a browser or other client

FAQ from @niklaserik/effect-mcp

How does the server fetch documentation?

It fetches documentation in real time directly from the Effect ecosystem, using an in-memory TTL cache (~10 minutes) to avoid refetching unchanged docs.

What transport does the server use?

It uses stdio transport by default and can be adapted to Streamable HTTP if needed.

Which Effect packages does it support?

It supports a curated list including effect, @effect/platform, @effect/sql, @effect/vitest, @effect/ai, @effect/cli, @effect/cluster, @effect/rpc, and @effect/typeclass.

Are there any runtime requirements?

The server requires Node.js, pnpm, and the @modelcontextprotocol/sdk v1.17.4+.

How does the server handle transient errors?

It applies lightweight retry with small backoff on transient fetch errors.

Comments

More Other MCP servers