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
The goal of the Model Context Protocol open source project (the “Project”) is to develop a universal standard for model-to-world interactions, including enabling LLMs and agents to seamlessly connect with and utilize external data sources and tools. The purpose of this Antitrust Policy (the “Policy”) is to avoid antitrust risks in carrying out this pro-competitive mission.
10
+
11
+
Participants in and contributors to the Project (collectively, “participants”) will use their best reasonable efforts to comply in all respects with all applicable state and federal antitrust and trade regulation laws, and applicable antitrust/competition laws of other countries (collectively, the “Antitrust Laws”).
12
+
13
+
The goal of Antitrust Laws is to encourage vigorous competition. Nothing in this Policy prohibits or limits the ability of participants to make, sell or use any product, or otherwise to compete in the marketplace. This Policy provides general guidance on compliance with Antitrust Law. Participants should contact their respective legal counsel to address specific questions.
14
+
15
+
This Policy is conservative and is intended to promote compliance with the Antitrust Laws, not to create duties or obligations beyond what the Antitrust Laws actually require. In the event of any inconsistency between this Policy and the Antitrust Laws, the Antitrust Laws preempt and control.
16
+
17
+
**Participation**
18
+
19
+
Technical participation in the Project shall be open to all, subject only to compliance with the provisions of the Project’s charter and other governance documents.
20
+
21
+
**Conduct of Meetings**
22
+
23
+
At meetings among actual or potential competitors, there is a risk that participants in those meetings may improperly disclose or discuss information in violation of the Antitrust Laws or otherwise act in an anti-competitive manner. To avoid this risk, participants must adhere to the following policies when participating in Project-related or sponsored meetings, conference calls, or other forums (collectively, “Project Meetings”).
24
+
25
+
Participants must not, in fact or appearance, discuss or exchange information regarding:
26
+
27
+
- An individual company’s current or projected prices, price changes, price differentials, markups, discounts, allowances, terms and conditions of sale, including credit terms, etc., or data that bear on prices, including profits, margins or cost.
28
+
- Industry-wide pricing policies, price levels, price changes, differentials, or the like.
29
+
- Actual or projected changes in industry production, capacity or inventories.
30
+
- Matters relating to bids or intentions to bid for particular products, procedures for responding to bid invitations or specific contractual arrangements.
31
+
- Plans of individual companies concerning the design, characteristics, production, distribution, marketing or introduction dates of particular products, including proposed territories or customers.
32
+
- Matters relating to actual or potential individual suppliers that might have the effect of excluding them from any market or of influencing the business conduct of firms toward such suppliers.
33
+
- Matters relating to actual or potential customers that might have the effect of influencing the business conduct of firms toward such customers.
34
+
- Individual company current or projected cost of procurement, development or manufacture of any product.
35
+
- Individual company market shares for any product or for all products.
36
+
- Confidential or otherwise sensitive business plans or strategy.
37
+
38
+
In connection with all Project Meetings, participants must do the following:
39
+
40
+
- Adhere to prepared agendas.
41
+
- Insist that meeting minutes be prepared and distributed to all participants, and that meeting minutes accurately reflect the matters that transpired.
42
+
- Consult with their respective counsel on all antitrust questions related to Project Meetings.
43
+
- Protest against any discussions that appear to violate these policies or the Antitrust Laws, leave any meeting in which such discussions continue, and either insist that such protest be noted in the minutes.
44
+
45
+
**Requirements/Standard Setting**
46
+
47
+
The Project may establish standards, technical requirements and/or specifications for use (collectively, “requirements”). Participants shall not enter into agreements that prohibit or restrict any participant from establishing or adopting any other requirements. Participants shall not undertake any efforts, directly or indirectly, to prevent any firm from manufacturing, selling, or supplying any product not conforming to a requirement.
48
+
49
+
The Project shall not promote standardization of commercial terms, such as terms for license and sale.
50
+
51
+
**Contact Information**
52
+
53
+
To contact the Project regarding matters addressed by this Antitrust Policy, please send an email to antitrust@modelcontextprotocol.io, and reference “Antitrust Policy” in the subject line.
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+89-32Lines changed: 89 additions & 32 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,11 @@
1
1
# Contributing to Model Context Protocol
2
2
3
-
Thank you for your interest in contributing to the Model Context Protocol specification!
3
+
Thank you for your interest in contributing to the Model Context Protocol specification, schemas, or docs!
4
4
This document outlines how to contribute to this project.
5
5
6
-
## Prerequisites
6
+
Also see the [overall MCP communication guidelines in our docs](https://modelcontextprotocol.io/community/communication), which explains how and where discussions about changes happen.
7
+
8
+
## General prerequisites
7
9
8
10
The following software is required to work on the spec:
9
11
@@ -13,57 +15,72 @@ The following software is required to work on the spec:
13
15
-[Mintlify](https://mintlify.com/) (optional, for docs)
14
16
- nvm (optional, for managing Node versions)
15
17
16
-
## Getting Started
18
+
### Getting Started
19
+
20
+
1.[Fork the repository](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo)
Note that schema changes are made to `schema.ts`, and `schema.json` is generated from
36
-
`schema.ts`.
42
+
## Schema changes
37
43
38
-
1. Create a new branch:
44
+
Schema changes go in `schema/draft/schema.ts`. To validate your changes, run:
39
45
40
46
```bash
41
-
git checkout -b feature/your-feature-name
47
+
npm run check:schema:ts
42
48
```
43
49
44
-
2. Make your changes.
45
-
46
-
3. Validate schema changes and generate `schema.json`:
50
+
`schema/draft/schema.json` and `docs/specification/draft/schema.mdx` are generated from `schema/draft/schema.ts`; do not edit them directly. To generate them, run:
47
51
48
52
```bash
49
-
npm run check:schema:ts
50
53
npm run generate:schema
51
54
```
52
55
53
-
4. Validate documentation changes and apply formatting:
56
+
## Documentation changes
57
+
58
+
Documentation is written in MDX format and in the [`docs`](./docs) directory.
59
+
60
+
You can preview documentation changes locally by running:
61
+
62
+
```bash
63
+
npm run serve:docs
64
+
```
65
+
66
+
And lint them with:
54
67
55
68
```bash
56
69
npm run check:docs
57
70
npm run format
58
71
```
59
72
60
-
5. Preview documentation locally (optional):
73
+
## Blog changes
74
+
75
+
The blog is built using [Hugo](https://gohugo.io/installation/) and located in the [`blog`](./blog) directory.
76
+
77
+
To preview blog changes locally:
61
78
62
79
```bash
63
-
npm run serve:docs
80
+
npm run serve:blog
64
81
```
65
82
66
-
###Documentation Guidelines
83
+
## Documentation Guidelines
67
84
68
85
When contributing to the documentation:
69
86
@@ -79,9 +96,9 @@ When contributing to the documentation:
0 commit comments