rustapi-mcp 0.1.550

Native Model Context Protocol (MCP) support for RustAPI - expose your endpoints as tools for LLMs and AI agents
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
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81

# rustapi-mcp

Native [Model Context Protocol (MCP)](https://modelcontextprotocol.io) integration for RustAPI.

This crate allows you to expose your existing RustAPI routes as **discoverable tools** for LLMs and AI agents (Claude, Cursor, custom agents, etc.) with full respect for your middleware, validation, auth, and observability layers.

## Status

**Core implementation complete** (discovery, `tools/list`, real `tools/call` via proxy into normal RustAPI pipeline, HTTP JSON-RPC transport, concurrent runner with `run_rustapi_and_mcp`).

See the [Native MCP Orchestration Plan](../../memories/native_mcp_orchestration_plan.md) for the original milestone breakdown. Polish items (docs, snapshots, tests, auth) remain before full release.

## Goals (v1)

- Opt-in via `protocol-mcp` feature
- Automatic tool discovery from your route metadata + OpenAPI schemas
- Tool invocations execute through the **normal** RustAPI request pipeline (no bypass)
- Support for the recommended HTTP + SSE transport (stdio later)
- Strong security defaults (explicit exposure control, never auto-expose everything)

## Usage (planned shape)

```rust
use rustapi_rs::prelude::*;
use rustapi_rs::protocol::mcp::{McpConfig, McpServer};

#[rustapi_rs::get("/users/{id}")]
async fn get_user(Path(id): Path<u64>) -> Json<User> { /* ... */ }

#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error + Send + Sync>> {
    let app = RustApi::auto();

    // Run your normal HTTP API + MCP side-by-side (similar to gRPC)
    let mcp = McpServer::new(
        McpConfig::new()
            .name("my-api")
            .version("1.0.0")
            .enable_tools(true)
            // Control what gets exposed as tools
            .allowed_tags(["public", "agent"])
            .admin_token("secret-for-mcp-clients"),
    );

    // Example concurrent runner (exact API will be refined)
    rustapi_mcp::run_rustapi_and_mcp(app, "0.0.0.0:8080", mcp).await?;
    Ok(())
}
```

## Feature Flag

In `rustapi-rs`:

```toml
[dependencies]
rustapi-rs = { version = "...", features = ["protocol-mcp"] }
```

Or with the meta feature:

```toml
rustapi-rs = { version = "...", features = ["protocol-all"] }
```

## Design Principles

- Follows the same facade contract as the rest of RustAPI.
- New internal crate (`rustapi-mcp`) behind the `protocol-mcp` feature.
- Tool calls **must** go through existing `Router`, layers, interceptors, extractors, and validation.
- Explicit exposure model by default (no accidental leakage of internal routes).

## Related

- Main roadmap: see top-level `README.md`
- Detailed plan: `memories/native_mcp_orchestration_plan.md`
- Master task list: `memories/TASKLIST.md`

## License

MIT OR Apache-2.0 (same as the rest of the workspace)