You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
🎉 Thank you for your interest in improving **rust-mcp-sdk**! Every contribution, big or small, is valuable and appreciated.
4
+
5
+
## **Code of Conduct**
6
+
7
+
We follow the [Rust Code of Conduct](https://www.rust-lang.org/policies/code-of-conduct). Please be respectful and inclusive when contributing.
8
+
9
+
## **How to Contribute**
10
+
11
+
### Participating in Tests, Documentation, and Examples
12
+
13
+
We highly encourage contributors to improve test coverage, enhance documentation, and introduce new examples to ensure the reliability and usability of the project. If you notice untested code paths, missing documentation, or areas where examples could help, consider adding tests, clarifying explanations, or providing real-world usage examples. Every improvement helps make the project more robust, well-documented, and accessible to others!
14
+
15
+
### Participating in Issues
16
+
17
+
You can contribute in three key ways:
18
+
19
+
1.**Report Issues** – If you find a bug or have an idea, open an issue for discussion.
20
+
2.**Help Triage** – Provide details, test cases, or suggestions to clarify issues.
21
+
3.**Resolve Issues** – Investigate problems and submit fixes via Pull Requests (PRs).
22
+
23
+
Anyone can participate at any stage, whether it's discussing, triaging, or reviewing PRs.
24
+
25
+
### **Filing a Bug Report**
26
+
27
+
When reporting a bug, use the provided issue template and fill in as many details as possible. Don’t worry if you can’t answer everything—just provide what you can.
28
+
29
+
### **Fixing Issues**
30
+
31
+
Most issues are resolved through a Pull Request. PRs go through a review process to ensure quality and correctness.
32
+
33
+
## **Pull Requests (PRs)**
34
+
35
+
We welcome PRs! Before submitting, please:
36
+
37
+
1.**Discuss major changes** – Open an issue before adding a new feature and opening a PR.
38
+
2.**Create a feature branch** – Fork the repo and branch from `main`.
39
+
3.**Write tests** – If your change affects functionality, add relevant tests.
40
+
4.**Update documentation** – If you modify APIs, update the docs.
41
+
5.**Run tests** – Make sure all tests succeed by running:
42
+
43
+
```sh
44
+
cargo make test
45
+
```
46
+
47
+
### **Commit Best Practices**
48
+
49
+
-**Relate PR changes to the issue** – Changes in a pull request (PR) should directly address the specific issue it’s tied to. Unrelated changes should be split into separate issues and PRs to maintain focus and simplify review.
50
+
-**Logically separate commits** – Keep changes atomic and easy to review.
51
+
-**Maintain a bisect-able history** – Each commit should compile and pass all tests to enable easy debugging with `git bisect` in case of regression.
52
+
53
+
## License
54
+
55
+
By contributing to rust-mcp-sdk, you acknowledge and agree that your contributions will be licensed under the terms specified in the LICENSE file located in the root directory of this repository.
Copy file name to clipboardExpand all lines: README.md
+15Lines changed: 15 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -213,6 +213,21 @@ The same principles outlined above apply to the client-side handlers, `mcp_clien
213
213
Use `client_runtime::create_client()` or `client_runtime_core::create_client()` , respectively.
214
214
Check out the corresponding examples at: [examples/simple-mcp-client](https://github.com/rust-mcp-stack/rust-mcp-sdk/tree/main/examples/simple-mcp-client) and [examples/simple-mcp-client-core](https://github.com/rust-mcp-stack/rust-mcp-sdk/tree/main/examples/simple-mcp-client-core).
215
215
216
+
## Contributing
217
+
218
+
We welcome everyone who wishes to contribute! Please refer to the [contributing](CONTRIBUTING.md) guidelines for more details.
219
+
220
+
Check out our [development guide](development.md) for instructions on setting up, building, testing, formatting, and trying out example projects.
221
+
222
+
All contributions, including issues and pull requests, must follow
223
+
Rust's Code of Conduct.
224
+
225
+
Unless explicitly stated otherwise, any contribution you submit for inclusion in rust-mcp-sdk is provided under the terms of the MIT License, without any additional conditions or restrictions.
226
+
227
+
## Development
228
+
229
+
Check out our [development guide](development.md) for instructions on setting up, building, testing, formatting, and trying out example projects.
230
+
216
231
## License
217
232
218
233
This project is licensed under the MIT License. see the [LICENSE](LICENSE) file for details.
2- Install dependencies: The Rust project uses Cargo for dependency management. To install dependencies, run:
23
+
24
+
```sh
25
+
cargo build
26
+
```
27
+
28
+
## Running Examples
29
+
30
+
Example projects can be found in the [/examples](/examples) folder of the repository.
31
+
Build and run instructions are available in their respective README.md files.
32
+
33
+
You can run examples by passing the example project name to Cargo using the `-p` argument, like this:
34
+
35
+
```sh
36
+
cargo run -p simple-mcp-client
37
+
```
38
+
39
+
You can build the examples in a similar way. The following command builds the project and generates the binary at `target/release/hello-world-mcp-server`:
40
+
41
+
```sh
42
+
43
+
cargo build -p hello-world-mcp-server --release
44
+
```
45
+
46
+
## Code Formatting
47
+
48
+
We follow the default Rust formatting style enforced by `rustfmt`. To format your code, run:
49
+
50
+
```sh
51
+
cargo fmt
52
+
```
53
+
54
+
Additionally, we use **Clippy** for linting Rust code. You can check for linting issues by running:
55
+
56
+
```sh
57
+
cargo make clippy
58
+
```
59
+
60
+
Please ensure your code is formatted and free of Clippy warnings before submitting any changes.
61
+
62
+
## Testing
63
+
64
+
We use [`cargo-nextest`](https://crates.io/crates/cargo-nextest) to run our test suite.
0 commit comments