Mcp | Alepha

alepha@docs:~/docs/packages/alepha$
cat mcp.md
2 min read
Last commit: 
#Alepha - Mcp
#InstallationPart of the alepha package. Import from alepha/mcp.

      
    
npm install alepha
#OverviewCore MCP module with primitives and server provider.
This module registers the $tool, $resource, and $prompt primitives
and the McpServerProvider. You need to add a transport module
(AlephaMcpStdio or AlephaMcpSse) for actual communication.
ts
import { Alepha, run } from "alepha";import { AlephaMcp, AlephaMcpStdio, $tool, t } from "alepha/mcp"; class MyMcpServer {  add = $tool({    description: "Add two numbers",    schema: {      params: t.object({ a: t.number(), b: t.number() }),      result: t.number(),    },    handler: async ({ params }) => params.a + params.b,  });} run(  Alepha.create()    .with(AlephaMcp)    .with(AlephaMcpStdio)    .with(MyMcpServer));
#API Reference
#PrimitivesPrimitives are functions that define and configure various aspects of your application. They follow the convention of starting with $ and return configured primitive instances.
For more details, see the Primitives documentation.
#$prompt()Creates an MCP prompt primitive for defining reusable prompt templates.
Prompts allow you to define templated messages that can be filled in
with arguments at runtime. They're useful for creating consistent
interaction patterns.
ts
      
class Prompts {  greeting = $prompt({    description: "Generate a personalized greeting",    args: t.object({      name: t.text({ description: "Name of the person to greet" }),      style: t.optional(t.enum(["formal", "casual"])),    }),    handler: async ({ args }) => [      {        role: "user",        content: args.style === "formal"          ? `Please greet ${args.name} in a formal manner.`          : `Say hi to ${args.name}!`,      },    ],  });   codeReview = $prompt({    description: "Request a code review",    args: t.object({      code: t.text({ description: "The code to review" }),      language: t.text({ description: "Programming language" }),    }),    handler: async ({ args }) => [      {        role: "user",        content: `Please review this ${args.language} code:

${args.code}`,      },    ],  });}
#$resource()Creates an MCP resource primitive for exposing read-only data.
Resources represent any kind of data that an LLM might want to read,
such as files, database records, API responses, or computed data.
Key Features
URI-based identification for resources
Support for text and binary content
MIME type specification
Lazy loading via handler function
ts
class ProjectResources {  readme = $resource({    uri: "file:///readme",    description: "Project README file",    mimeType: "text/markdown",    handler: async () => ({      text: await fs.readFile("README.md", "utf-8"),    }),  });   config = $resource({    uri: "config://app",    name: "Application Configuration",    mimeType: "application/json",    handler: async () => ({      text: JSON.stringify(this.configService.getConfig()),    }),  });}
#$tool()Creates an MCP tool primitive for defining callable functions.
Tools are the primary way for LLMs to interact with external systems through MCP.
Each tool has a name, description, typed parameters, and a handler function.
Key Features
Full TypeScript inference for parameters and results
Automatic schema validation using TypeBox
JSON Schema generation for MCP protocol
Integration with MCP server provider
ts
      
class CalculatorTools {  add = $tool({    description: "Add two numbers together",    schema: {      params: t.object({        a: t.number(),        b: t.number(),      }),      result: t.number(),    },    handler: async ({ params }) => {      return params.a + params.b;    },  });   greet = $tool({    description: "Generate a greeting message",    schema: {      params: t.object({        name: t.text(),      }),      result: t.text(),    },    handler: async ({ params }) => {      return `Hello, ${params.name}!`;    },  });}
#ProvidersProviders are classes that encapsulate specific functionality and can be injected into your application. They handle initialization, configuration, and lifecycle management.
For more details, see the Providers documentation.
#McpServerProviderCore MCP server provider that handles protocol messages.
This provider maintains registries of tools, resources, and prompts,
and routes incoming JSON-RPC requests to the appropriate handlers.
It is transport-agnostic - actual communication is handled by
transport providers like StdioMcpTransport or SseMcpTransport.
On This Page
No headings found...

ready
│main│TypeScript
│UTF-8│packages_alepha_mcp.md│