About Effect MCP
Effect MCP is an MCP server published by niklaserik in the Developer Tools category: a mcp server for fetching the Effect-ts documentation. It has been installed 0 times through Conduid.
The repository has 42 stars and 6 forks, with the last commit a year ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues (0) before depending on it in production.
Install
npx effect-mcpThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Ask AI
Ask AI about Effect MCP
Powered by Claude · Grounded in docs
Security checks
- ·README presentNot checked yet.
- ·License declaredNot checked yet.
- ·Tests presentNot checked yet.
- ·Dependencies pinnedNot checked yet.
- ·No dynamic code executionNot checked yet.
- !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.
README
@niklaserik/effect-mcp
A Model Context Protocol (MCP) server dedicated to fetching the most current documentation from the Effect ecosystem.
Purpose
This MCP server provides real-time access to Effect documentation for AI assistants and tools. It enables VS Code extensions and other MCP clients to retrieve accurate and up-to-date Effect package documentation to assist developers with questions about:
- The core
effectpackage - Ecosystem packages (
@effect/platform,@effect/ai, etc.) - Both stable and unstable Effect packages
The server intelligently detects imported Effect packages in your code and fetches the most relevant documentation to answer your queries.
Features
- Real-time documentation access for Effect ecosystem
- Support for both stable and experimental packages
- Context-aware package detection based on imports
- Seamless integration with VS Code and other MCP-compatible clients
- Helps answer API usage questions for Effect developers
What this server exposes
- Resources (preferred)
- Dynamic template:
effect-docs://{libId} - Completions on
{libId}and resource listing are supported - Static aliases for discovery:
effect-docs://effect,effect-docs://@effect-platform, etc. - Supported libraries (as of now):
effect@effect/platform@effect/sql@effect/vitest@effect/ai@effect/cli@effect/cluster@effect/rpc@effect/typeclass
- Dynamic template:
- Tools (for compatibility)
effect-documentation: fetch docs for selected libraries and return concatenated markdowneffect-doc-links: return plain URIs to the resources above so clients can follow them
Caching & Retry
- In-memory TTL cache (~10 minutes) to avoid refetching unchanged docs.
- Lightweight retry with small backoff on transient fetch errors.
Installation
pnpm add @niklaserik/effect-mcp
Usage
For usage in VS Code or other MCP clients, refer to the client's documentation for adding custom MCP servers.
Quick test locally:
pnpm install
pnpm build
node dist/index.js # stdio transport
Then connect with an MCP client (e.g., MCP Inspector) over stdio and try:
- List resources and read
effect-docs://effect - Call tool
effect-doc-linkswith{ "libraries": ["effect", "@effect/platform"] }
Initialization instructions
- The server publishes short usage instructions via MCP initialize for clients that display them.
Development
# Install dependencies
pnpm install
# Build the project
pnpm build
# Run in development mode with auto-reload
pnpm dev
Notes:
- Built with
@modelcontextprotocol/sdk@^1.17.4using the modernregisterResource/registerToolAPIs. - Transport: stdio by default; can be adapted to Streamable HTTP if needed.
License
MIT
README mirrored from the source repository 4 months ago. The original is authoritative.