dpella-mcp

Document MCP API conventions and transport patterns for Haskell integrations.

954|78|Updated May 9, 2021
One-click install
npx skills add https://github.com/srid/emanote --skill dpella-mcp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dpella-mcp
Source: https://github.com/srid/emanote/tree/main/.apm/skills/dpella-mcp
Command: npx skills add https://github.com/srid/emanote --skill dpella-mcp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reference for the dpella/mcp Haskell library — types, handler shape, transports, and the conventions Emanote uses. Load this before adding MCP resources/tools/subscriptions so you don't re-discover the API by WebFetch.

Core Features & Use Cases

  • Provides canonical MCP API conventions for consistent integration
  • Documents available transports (HTTP + JWT, Simple HTTP, Stdio) and server shapes
  • Use Case: align your MCP server wiring in a Haskell project to avoid API drift with client tooling

Quick Start

Load and consult this dpella/mcp reference before adding MCP resources to ensure API alignment.

Frequently Asked Questions about dpella-mcp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What transports are available for an MCP server in Haskell?

MCP server implementations in Haskell support HTTP + JWT, Simple HTTP, and Stdio transports. The reference details required types and server shapes for wiring these communication channels into your service.

How do I wire an MCP server in a Haskell application?

Wiring an MCP server in Haskell involves initializing MCP.Server with required types and handler definitions. This reference documents the expected field definitions and helper patterns to ensure proper server setup.

Does the Haskell MCP library support Stdio transport?

Yes, the Haskell MCP library supports Stdio transport alongside HTTP + JWT and Simple HTTP options. It provides the necessary conventions and initialization patterns for integrating Stdio communication.

What API conventions does Emanote use for MCP integration?

Emanote uses canonical MCP API conventions for consistent integration, documenting required types, handler shapes, and field definitions. This ensures alignment between your Haskell MCP server and client tooling.

Why align my Haskell MCP server wiring with documented API conventions?

Aligning your Haskell MCP server wiring with documented API conventions prevents API drift with client tooling. The reference provides canonical patterns for adding MCP resources, tools, and subscriptions.

Can I use HTTP and JWT for authentication in a Haskell MCP server?

Yes, HTTP + JWT is one of the supported transports for Haskell MCP servers. The reference covers the server shapes and initialization required to implement HTTP with JWT authentication.