rskit-mcp 0.2.0-alpha.2

Bridge between rskit tool registry and Model Context Protocol (MCP)
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62

# rskit-mcp — Model Context Protocol bridge

`rskit-mcp` exposes an `rskit-tool` registry through MCP and can discover remote MCP tools for use inside rskit applications. It keeps tool execution policy in `rskit-tool::Envelope` while mapping MCP wire types at the boundary.

## Install

```toml
[dependencies]
rskit-mcp = "0.2.0-alpha.2"
rskit-tool = "0.2.0-alpha.3"
```

## Architecture

```mermaid
graph TD
    tool[rskit-tool]
    schema[rskit-schema]
    authz[rskit-authz]
    skill[rskit-skill]
    mcp[rskit-mcp]
    server[stdio/server adapters]
    client[remote client]
    registry[tool registry bridge]
    agent[rskit-agent]

    tool --> mcp
    schema --> mcp
    authz --> mcp
    skill --> mcp
    mcp --> server
    mcp --> client
    mcp --> registry
    registry --> agent
```

## Quick start

```rust
use std::sync::Arc;

use rskit_mcp::{ServerConfig, create_server};
use rskit_tool::Registry;

fn main() {
    let tools = Arc::new(Registry::new());

    let _handler = create_server(
        "example-mcp",
        "0.1.0-alpha.1",
        tools,
        ServerConfig {
            prefix: "local.".into(),
            ..ServerConfig::default()
        },
    );
}
```

## When to use

Use `rskit-mcp` when you need to expose a local tool registry through MCP or consume remote MCP tools without letting protocol concerns leak into the core tool layer.