J

ModelContextProtocol.jl

...
Created 12/11/2024byJuliaSMLM

Language:

Julia

Stars:

1

Forks:

0

ModelContextProtocol

Stable Dev Build Status Coverage

A Julia implementation of the Model Context Protocol (MCP), enabling integration with Large Language Models (LLMs) like Anthropic's Claude by providing standardized access to tools, resources, and prompts.

Overview

The Model Context Protocol allows applications to provide context and capabilities to LLMs in a standardized way. This package implements the full MCP specification in Julia, with mcp_server() as the main entry point for creating and configuring servers.

The mcp_server() function provides a flexible interface to:

  • Create MCP servers with custom names and configurations
  • Register tools, resources, and prompts manually or automatically
  • Configure server capabilities and behavior
  • Set up directory-based component organization

Example:

server = mcp_server(
    name = "my-server",
    version = "2024-11-05",
    tools = my_tool,              # Single tool or vector of tools
    resources = my_resource,      # Single resource or vector of resources
    prompts = my_prompt,         # Single prompt or vector of prompts
    description = "Server description",
    auto_register_dir = "path/to/components"  # Optional auto-registration
)

The package enables you to:

  • Create MCP servers that expose tools, resources, and prompts

              - Define custom tools that LLMs can interact with
    
  • Organize and auto-register components from directory structures

  • Handle all MCP protocol messages and lifecycle events

Core Components

The package provides three main types that can be registered with an MCP server:

  1. MCPTool: Represents callable functions that LLMs can use

    • Has a name, description, parameters, and handler function
    • LLMs can invoke tools to perform actions or computations
  2. MCPResource: Represents data sources that LLMs can read

    • Has a URI, name, MIME type, and data provider function
    • Provides static or dynamic data access to LLMs
  3. MCPPrompt: Represents template-based prompts

    • Has a name, description, and parameterized message templates
    • Helps standardize interactions with LLMs

Quick Start

Installation

using Pkg
Pkg.add("ModelContextProtocol")

Basic Example: Manual Tool Setup

Here's a minimal example creating an MCP server with a single tool:

using ModelContextProtocol
using JSON3
using Dates

# Create a simple tool that returns the current time
time_tool = MCPTool(
    name = "get_time",
    description = "Get current time in specified format",
    parameters = [
        ToolParameter(
            name = "format",
            type = "string",
            description = "DateTime format string",
            required = true
        )
    ],
    handler = params -> TextContent(
        type = "text",
        text = JSON3.write(Dict(
            "time" => Dates.format(now(), params["format"])
        ))
    )
)

# Create and start server with the tool
server = mcp_server(
    name = "time-server",
    description = "Simple MCP server with time tool",
    tools = time_tool
)

# Start the server
start!(server)

Directory-Based Organization

You can also organize your MCP components in a directory structure and auto-register them:

my_mcp_server/
├── tools/
│   ├── time_tool.jl
│   └── math_tool.jl

            
        
            
                ├── resources/
│   └── data_source.jl
└── prompts/
    └── templates.jl
using ModelContextProtocol

# Create and start server with all components
server = mcp_server(
    name = "full-server",
    description = "MCP server with auto-registered components",
    auto_register_dir = "my_mcp_server"
)

start!(server)

The package will automatically scan the directory structure and register all components:

  • tools/: Contains tool definitions (MCPTool instances)
  • resources/: Contains resource definitions (MCPResource instances)
  • prompts/: Contains prompt definitions (MCPPrompt instances)

Each component file should export one or more instances of the appropriate type. They will be automatically discovered and registered with the server.

Component Structure

Tools

Tools are functions that LLMs can call. Each tool must define:

  • Name and description
  • Input parameters with types and descriptions
  • Handler function that processes the inputs

Example tool file (tools/calculator.jl):

using ModelContextProtocol
using JSON3

calculator_tool = MCPTool(
    name = "calculate",
    description = "Perform basic arithmetic",
    parameters = [
        ToolParameter(
            name = "expression",
            type = "string",
            description = "Math expression to evaluate",
            required = true
        )
    ],
    handler = params -> TextContent(
        type = "text",
        text = JSON3.write(Dict(
            "result" => eval(Meta.parse(params["expression"]))
        ))
    )
)

Using with Claude

To use your MCP server with Claude, you need to:

  1. Configure Claude Desktop: Add to claude_desktop_config.json:

    {
      "mcpServers": {
        "my-server": {
          "command": "julia",
          "args": ["--project=/path/to/project", "server_script.jl"],
          "env": {
            "JULIA_DEPOT_PATH": "/path/to/julia/depot"
          }
        }
      }
    }
    
             2. Start a conversation with Claude and tell it to use your server:
    
    Please connect to the MCP server named "my-server" and list its available tools.
    
  2. Claude will connect to your server and can then:

    • List available tools using the server's capabilities
    • Call tools with appropriate parameters
    • Access resources and prompts
    • Report results back to you

License

This project is licensed under the MIT License - see the LICENSE file for details.

Last updated: 2/2/2025

Publisher info

JuliaSMLM's avatar

JuliaSMLM

Julia based tools for single molecule localization microscopy

3
followers
0
following
10
repos

More MCP servers built with Julia

No other servers with Julia found.