Crate rmcp_macros 

rmcp-macros

Procedural macros for the RMCP SDK. Most users should depend on rmcp with the macros feature (enabled by default) rather than using this crate directly.

For getting started and full MCP feature documentation, see the main README.

Available Macros

Macro	Description
#[tool]	Mark a function as an MCP tool handler
#[tool_router]	Generate a tool router from an impl block (optional server_handler flag elides a separate #[tool_handler] block for tools-only servers)
#[tool_handler]	Generate call_tool and list_tools handler methods
#[prompt]	Mark a function as an MCP prompt handler
#[prompt_router]	Generate a prompt router from an impl block
#[prompt_handler]	Generate get_prompt and list_prompts handler methods
#[task_handler]	Wire up the task lifecycle on top of an OperationProcessor

Quick Example

Tools-only server with a single impl block (server_handler expands #[tool_handler] in a second macro pass):

use rmcp::{tool, tool_router};

#[derive(Clone)]
struct MyServer;

#[tool_router(server_handler)]
impl MyServer {
    #[tool(description = "Say hello")]
    async fn hello(&self) -> String {
        "Hello, world!".into()
    }
}

If you need custom #[tool_handler(...)] arguments (e.g. instructions, name, or stacked #[prompt_handler] on the same impl ServerHandler), use two blocks instead:

use rmcp::{tool, tool_router, tool_handler, ServerHandler};

#[derive(Clone)]
struct MyServer;

#[tool_router]
impl MyServer {
    #[tool(description = "Say hello")]
    async fn hello(&self) -> String {
        "Hello, world!".into()
    }
}

#[tool_handler]
impl ServerHandler for MyServer {}

See the full documentation for detailed usage of each macro.

License

This project is licensed under the terms specified in the repository’s LICENSE file.

Attribute Macros

prompt

prompt

prompt_handler

prompt_handler

prompt_router

prompt_router

task_handler

task_handler

tool

tool

tool_handler

tool_handler

tool_router

tool_router