Effect Q&A MCP Server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Effect Q&A MCP Serverget categories summary"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Effect Q&A MCP Server
A Model Context Protocol (MCP) server that exposes a single tool: get-categories-summary. Fetches category data from a Q&A service API and returns a markdown summary grouped by category.
Quick Start
# Install dependencies
bun install
# Start the MCP server (requires QA_SERVICE_URL)
QA_SERVICE_URL=https://your-qa-api.example.com bun run index.ts
# Run tests
bun run test
# Type-check
npx tsc --noEmit
# Format code
bun run fmtRelated MCP server: Document360 MCP Server
Architecture Overview
Component Diagram
graph TB
subgraph "MCP Client"
Client[MCP Client<br/>(Claude, Cursor, etc.)]
end
subgraph "MCP Server Process"
Server[McpServer.layerHttp<br/>:3000/mcp]
Tool[get-categories-summary<br/>Tool Handler]
ApiClient[ApiClient Service<br/>fetchCategories]
HttpClient[NodeHttpClient.layer<br/>Platform HTTP]
end
subgraph "External"
QA_API[Q&A Service API<br/>GET /api/v1/categories]
end
Client <-- MCP over HTTP --> Server
Server --> Tool
Tool --> ApiClient
ApiClient --> HttpClient
HttpClient --> QA_APILayer Stack (Inner → Outer)
The server is composed as an Effect Layer stack. Each layer provides services to the layers above it.
graph TB
subgraph "Layer Stack"
L5[Layer 5: registerTool<br/>Tool Registration]
L4[Layer 4: ApiClient.Default<br/>Q&A API Client]
L3[Layer 3: McpServer.layerHttp<br/>MCP Protocol @ /mcp]
L2[Layer 2: NodeHttpServer.layer<br/>Node HTTP Server]
L1[Layer 1: NodeHttpClient.layer<br/>Platform HTTP Transport]
end
L1 --> L2
L2 --> L3
L3 --> L4
L4 --> L5
style L1 fill:#f9f,stroke:#333
style L2 fill:#bbf,stroke:#333
style L3 fill:#bfb,stroke:#333
style L4 fill:#ff9,stroke:#333
style L5 fill:#f96,stroke:#333Layer | Responsibility | Provides |
1. | Platform HTTP transport (fetch, connections, pooling) |
|
2. | Node.js HTTP server listening on |
|
3. | MCP protocol handler at |
|
4. | Q&A API client with config ( |
|
5. | Wires | — (side effect) |
Module Structure
src/
├── index.ts — MCP server setup, layer composition, entry point
├── api-client.ts — Effect.Service for Q&A API (errors, HTTP adapter)
├── summary.ts — Pure function: Category[] → markdown string
├── types.ts — Effect Schema definitions (Category, CategoriesResponse)
└── services.ts — Reserved for future top-level services
test/
├── index.test.ts — buildSummary tests + handler with nock
└── summary.test.ts — buildSummary edge casesData Flow
sequenceDiagram
participant Client as MCP Client
participant Server as MCP Server
participant Tool as get-categories-summary
participant ApiClient as ApiClient
participant HttpClient as HttpClient
participant QA as Q&A API
Client->>Server: POST /mcp {method: "tools/call", params: {name: "get-categories-summary"}}
Server->>Tool: invoke handler
Tool->>ApiClient: fetchCategories()
ApiClient->>HttpClient: execute GET /api/v1/categories
HttpClient->>QA: HTTP Request
QA-->>HttpClient: 200 OK {data: [...]}
HttpClient-->>ApiClient: HttpClientResponse
ApiClient->>ApiClient: filterStatusOk → decode JSON → Schema.decode
ApiClient-->>Tool: CategoriesResponse
Tool->>Tool: buildSummary(categories.data)
Tool-->>Server: CallToolResult {content: [TextContent]}
Server-->>Client: MCP ResponseConfiguration
Environment Variable | Required | Description |
| Yes | Base URL of Q&A API (e.g., |
| No | Bearer token for authenticated requests |
| No | HTTP listen port (default: |
Error Handling
The tool handler folds all errors into CallToolResult with isError: true:
Error Type | Trigger | User-Facing Message |
| Non-2xx HTTP status |
|
| Schema validation failed |
|
| Transport/DNS/timeout/JSON parse |
|
Tool Specification
get-categories-summary
Description: Fetches categories from the Q&A service and returns a narrative summary grouped by category
Input: None (empty object)
Annotations:
readOnlyHint: true— clients may cache/replayOutput: Markdown string via
TextContent
Example Output:
Found 3 categories across 2 groups.
## bugs (2)
- **Login Issue**: Cannot log in
- **Crash**: App crashes on start
## features (1)
- **Dark Mode**: Add dark themeTesting
# Unit tests (pure functions)
bun run test
# With coverage
bun run test:coverageTest strategy:
buildSummary— pure function tests (empty, single, multi-category)Handler — integration test with
nockintercepting HTTP toQA_SERVICE_URL
Development
# Format check
bun run fmt:check
# Type-check
npx tsc --noEmit
# Regenerate docs
bun run docsDependencies
Runtime
@effect/ai— MCP server implementation@effect/platform-node— Node.js platform layers (HTTP client/server)effect— Core Effect-TS (services, layers, schemas, errors)
Dev
@effect/vitest— Effect-native testing (it.effect,assert)nock— HTTP mocking for integration testsoxfmt— Formatter (printWidth 120, no semicolons)@effect/language-service— IDE support via tsconfig plugin
License
Private — internal tooling.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/forthy/effect-qa-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server