One read of Model Context Protocolmcp-20260928T230714Z
16 pages moved out of 349 read.
Pages moved
16
significant first
Pages read
349
in this capture
Captured
23:07 UTC
Corpus hash
e4ab62a1551b
corpus-hash
What this read moved
1-16 of 16community/sep-guidelines Changed · +26 / -21 lines
from line 69
6969
7070### Step-by-Step Process
7171
72<Note>
73 To improve your chances of a SEP being accepted:
72**Prior discussion is required.** SEP authors must discuss the idea with the relevant [working or interest group](/community/working-interest-groups) in [Discord](/community/communication#discord) before opening the SEP pull request, and the PR description must link to that discussion (a Discord thread, WG/IG meeting notes, or a GitHub Discussion). A SEP without a linked prior discussion is not accepted. If no relevant group exists, start a conversation in [GitHub Discussions](https://github.com/modelcontextprotocol/modelcontextprotocol/discussions) or the `#general` channel in [Discord](/community/communication#discord) instead. If there is enough interest, it may be worth [creating a new IG or WG](/community/working-interest-groups#creating-an-interest-group). The effort involved in finding sponsors and facilitators is a good signal of whether the idea has sufficient traction.
7473
75 * **Discuss your idea with the relevant [working or interest group](/community/working-interest-groups) in [Discord](/community/communication#discord) first.** This is the single best way to refine your proposal and build early support.
76 * **If no relevant group exists, start a conversation in [GitHub Discussions](https://github.com/modelcontextprotocol/modelcontextprotocol/discussions) or the `#general` channel in [Discord](/community/communication#discord).** If there is enough interest, it may be worth [creating a new IG or WG](/community/working-interest-groups#creating-an-interest-group) — the effort involved in finding sponsors and facilitators is a good signal of whether the idea has sufficient traction, and is still preferable to a cold submission.
77 * **Check alignment with [Core Maintainer](/community/governance#roles) priorities and [design principles](/community/design-principles).** Priorities are generally reflected in the [project roadmap](/development/roadmap). Proposals outside current priorities or that conflict with design principles are more likely to face delays or additional friction in the review process.
74<Note>
75 To improve your chances of a SEP being accepted, check alignment with [Core
76 Maintainer](/community/governance#roles) priorities and [design
77 principles](/community/design-principles). Priorities are generally reflected
78 in the [project roadmap](/development/roadmap). Proposals outside current
79 priorities or that conflict with design principles are more likely to face
80 delays or additional friction in the review process.
7881</Note>
7982
801. **Draft your SEP** as a markdown file named `0000-your-feature-title.md`, using `0000` as a placeholder. Follow the [SEP format](#sep-format) below.
831. **Discuss with the relevant group**: Bring your idea to the matching [working or interest group](/community/working-interest-groups) and refine it there. Keep a link to the discussion (a Discord thread, meeting notes, or a GitHub Discussion) so you can include it in the PR description.
8184
822. **Create a pull request** adding your SEP file to the `seps/` directory in the [specification repository](https://github.com/modelcontextprotocol/modelcontextprotocol).
852. **Draft your SEP** as a markdown file named `0000-your-feature-title.md`, using `0000` as a placeholder. Follow the [SEP format](#sep-format) below.
8386
843. **Update the SEP number**: Once your PR is created, rename the file using the PR number (e.g., PR #1850 becomes `1850-your-feature-title.md`) and update the SEP header.
873. **Create a pull request** adding your SEP file to the `seps/` directory in the [specification repository](https://github.com/modelcontextprotocol/modelcontextprotocol). The repository accepts pull requests from collaborators only.
8588
864. **Find a Sponsor**: Tag a Core Maintainer or Maintainer from [the maintainer list](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/MAINTAINERS.md). Choose someone whose area relates to your proposal. Tips:
894. **Update the SEP number**: Once your PR is created, rename the file using the PR number (e.g., PR #1850 becomes `1850-your-feature-title.md`) and update the SEP header.
90
915. **Find a Sponsor**: Tag a Core Maintainer or Maintainer from [the maintainer list](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/MAINTAINERS.md). Choose someone whose area relates to your proposal. Tips:
8792 * Tag 1-2 relevant maintainers, not everyone
8893 * Share your PR in the relevant Discord channel
8994 * If no response after 2 weeks, ask in `#general`
9095
915. **Sponsor assigns themselves**: When a sponsor agrees, they assign themselves to the PR and update the SEP status to `draft`.
966. **Sponsor assigns themselves**: When a sponsor agrees, they assign themselves to the PR and update the SEP status to `draft`.
9297
936. **Informal review**: The sponsor reviews the proposal and may request changes. Discussion happens in PR comments.
987. **Informal review**: The sponsor reviews the proposal and may request changes. Discussion happens in PR comments.
9499
957. **Formal review**: When ready, the sponsor updates the status to `in-review`. The SEP enters formal review by Core Maintainers (meetings every two weeks).
1008. **Formal review**: When ready, the sponsor updates the status to `in-review`. Before doing so, the sponsor confirms that the group discussion happened and is linked in the PR description. The SEP enters formal review by Core Maintainers (meetings every two weeks).
96101
978. **Resolution**: The SEP may be `accepted`, `rejected`, or returned for revision. The sponsor updates the status.
1029. **Resolution**: The SEP may be `accepted`, `rejected`, or returned for revision. The sponsor updates the status.
98103
999. **Finalization**: Once accepted, the reference implementation must be completed. For Standards Track SEPs with observable protocol behavior, a [conformance test](#conformance-test-requirement) must also be merged. The author adds the specification changes (schema changes, specification text, and a changelog entry) to the SEP's pull request. SDK implementations are not required for a SEP to become `final`. When this work is complete, the sponsor updates the status to `final` and the SEP's PR can be merged. Merged SEPs are published in the [SEP index](/seps/index), and each one is reachable by number at `modelcontextprotocol.io/seps/<number>` (for example, [/seps/1850](/seps/1850)).
10410. **Finalization**: Once accepted, the reference implementation must be completed. For Standards Track SEPs with observable protocol behavior, a [conformance test](#conformance-test-requirement) must also be merged. The author adds the specification changes (schema changes, specification text, and a changelog entry) to the SEP's pull request. SDK implementations are not required for a SEP to become `final`. When this work is complete, the sponsor updates the status to `final` and the SEP's PR can be merged. Merged SEPs are published in the [SEP index](/seps/index), and each one is reachable by number at `modelcontextprotocol.io/seps/<number>` (for example, [/seps/1850](/seps/1850)).
100105
101106### SEP Statuses
102107
community/working-groups/file-uploads Changed · +1 / -1 lines
from line 43
4343* **MCP Apps WG** — embedded app UIs may surface their own file pickers; the descriptor format
4444 should be reusable in that context.
4545* **Security WG** — host-side validation requirements for user-supplied file content (the SEP
46 references [OWASP ASVS V5](https://owasp.org/www-project-application-security-verification-standard/)
46 references [OWASP ASVS V5](https://owasp.org/projects/asvs)
4747 for general upload hygiene).
4848* **Tool Annotations IG** — file input descriptors are a form of input-parameter metadata and should
4949 remain consistent with the broader annotation taxonomy.
community/working-interest-groups Changed · +1 / -1 lines
from line 277
277277
278278### Do I need to be in a WG to submit a SEP?
279279
280No. Anyone can submit a SEP. However, WG collaboration can strengthen your proposal and help it find a sponsor.
280No. Anyone can submit a SEP, and group membership is not required. The proposal must still be brought to the relevant group's Discord channel before the SEP pull request is opened, as described in the [SEP guidelines](/community/sep-guidelines#step-by-step-process). Beyond that requirement, closer WG collaboration can strengthen your proposal and help it find a sponsor.
281281
282282### What if my IG discussion leads to a concrete solution?
283283
docs/2024-11-05/develop/build-server Changed · +1 / -1 lines
from line 1070
10701070
10711071 When you start your client application, the auto-configuration will automatically create MCP clients from the claude\_desktop\_config.json.
10721072
1073 For more information, see the [MCP Client Boot Starters](https://docs.spring.io/spring-ai/reference/api/mcp/mcp-server-boot-client-docs.html) reference documentation.
1073 For more information, see the [MCP Client Boot Starters](https://docs.spring.io/spring-ai/reference/api/mcp/mcp-client-boot-starter-docs.html) reference documentation.
10741074
10751075 ## More Java MCP Server examples
10761076
docs/2024-11-05/develop/connect-remote-servers Changed · +2 / -2 lines
from line 19
1919With Custom Connectors, you can:
2020
2121* [Connect Claude to existing remote MCP servers](https://support.anthropic.com/en/articles/11175166-getting-started-with-custom-connectors-using-remote-mcp) provided by third-party developers
22* [Build your own remote MCP servers to connect with any tool](https://support.anthropic.com/en/articles/11503834-building-custom-connectors-via-remote-mcp-servers)
22* [Build your own remote MCP servers to connect with any tool](/docs/2024-11-05/develop/build-server)
2323
2424## Connecting to a Remote MCP Server
2525
from line 96
9696Now that you've connected Claude to a remote MCP server, you can explore its capabilities in your conversations. Try using the connected tools to automate tasks, access external data, or integrate with your existing workflows.
9797
9898<CardGroup cols={2}>
99 <Card title="Build your own remote server" icon="cloud" href="https://support.anthropic.com/en/articles/11503834-building-custom-connectors-via-remote-mcp-servers">
99 <Card title="Build your own remote server" icon="cloud" href="/docs/2024-11-05/develop/build-server">
100100 Create custom remote MCP servers to integrate with proprietary tools and
101101 services
102102 </Card>
docs/2025-03-26/develop/build-server Changed · +1 / -1 lines
from line 1070
10701070
10711071 When you start your client application, the auto-configuration will automatically create MCP clients from the claude\_desktop\_config.json.
10721072
1073 For more information, see the [MCP Client Boot Starters](https://docs.spring.io/spring-ai/reference/api/mcp/mcp-server-boot-client-docs.html) reference documentation.
1073 For more information, see the [MCP Client Boot Starters](https://docs.spring.io/spring-ai/reference/api/mcp/mcp-client-boot-starter-docs.html) reference documentation.
10741074
10751075 ## More Java MCP Server examples
10761076
docs/2025-03-26/develop/connect-remote-servers Changed · +2 / -2 lines
from line 19
1919With Custom Connectors, you can:
2020
2121* [Connect Claude to existing remote MCP servers](https://support.anthropic.com/en/articles/11175166-getting-started-with-custom-connectors-using-remote-mcp) provided by third-party developers
22* [Build your own remote MCP servers to connect with any tool](https://support.anthropic.com/en/articles/11503834-building-custom-connectors-via-remote-mcp-servers)
22* [Build your own remote MCP servers to connect with any tool](/docs/2025-03-26/develop/build-server)
2323
2424## Connecting to a Remote MCP Server
2525
from line 96
9696Now that you've connected Claude to a remote MCP server, you can explore its capabilities in your conversations. Try using the connected tools to automate tasks, access external data, or integrate with your existing workflows.
9797
9898<CardGroup cols={2}>
99 <Card title="Build your own remote server" icon="cloud" href="https://support.anthropic.com/en/articles/11503834-building-custom-connectors-via-remote-mcp-servers">
99 <Card title="Build your own remote server" icon="cloud" href="/docs/2025-03-26/develop/build-server">
100100 Create custom remote MCP servers to integrate with proprietary tools and
101101 services
102102 </Card>
docs/2025-06-18/develop/build-server Changed · +1 / -1 lines
from line 1070
10701070
10711071 When you start your client application, the auto-configuration will automatically create MCP clients from the claude\_desktop\_config.json.
10721072
1073 For more information, see the [MCP Client Boot Starters](https://docs.spring.io/spring-ai/reference/api/mcp/mcp-server-boot-client-docs.html) reference documentation.
1073 For more information, see the [MCP Client Boot Starters](https://docs.spring.io/spring-ai/reference/api/mcp/mcp-client-boot-starter-docs.html) reference documentation.
10741074
10751075 ## More Java MCP Server examples
10761076
docs/2025-06-18/develop/connect-remote-servers Changed · +2 / -2 lines
from line 19
1919With Custom Connectors, you can:
2020
2121* [Connect Claude to existing remote MCP servers](https://support.anthropic.com/en/articles/11175166-getting-started-with-custom-connectors-using-remote-mcp) provided by third-party developers
22* [Build your own remote MCP servers to connect with any tool](https://support.anthropic.com/en/articles/11503834-building-custom-connectors-via-remote-mcp-servers)
22* [Build your own remote MCP servers to connect with any tool](/docs/2025-06-18/develop/build-server)
2323
2424## Connecting to a Remote MCP Server
2525
from line 96
9696Now that you've connected Claude to a remote MCP server, you can explore its capabilities in your conversations. Try using the connected tools to automate tasks, access external data, or integrate with your existing workflows.
9797
9898<CardGroup cols={2}>
99 <Card title="Build your own remote server" icon="cloud" href="https://support.anthropic.com/en/articles/11503834-building-custom-connectors-via-remote-mcp-servers">
99 <Card title="Build your own remote server" icon="cloud" href="/docs/2025-06-18/develop/build-server">
100100 Create custom remote MCP servers to integrate with proprietary tools and
101101 services
102102 </Card>
docs/2025-11-25/develop/build-server Changed · +1 / -1 lines
from line 1070
10701070
10711071 When you start your client application, the auto-configuration will automatically create MCP clients from the claude\_desktop\_config.json.
10721072
1073 For more information, see the [MCP Client Boot Starters](https://docs.spring.io/spring-ai/reference/api/mcp/mcp-server-boot-client-docs.html) reference documentation.
1073 For more information, see the [MCP Client Boot Starters](https://docs.spring.io/spring-ai/reference/api/mcp/mcp-client-boot-starter-docs.html) reference documentation.
10741074
10751075 ## More Java MCP Server examples
10761076
docs/2025-11-25/develop/connect-remote-servers Changed · +2 / -2 lines
from line 19
1919With Custom Connectors, you can:
2020
2121* [Connect Claude to existing remote MCP servers](https://support.anthropic.com/en/articles/11175166-getting-started-with-custom-connectors-using-remote-mcp) provided by third-party developers
22* [Build your own remote MCP servers to connect with any tool](https://support.anthropic.com/en/articles/11503834-building-custom-connectors-via-remote-mcp-servers)
22* [Build your own remote MCP servers to connect with any tool](/docs/2025-11-25/develop/build-server)
2323
2424## Connecting to a Remote MCP Server
2525
from line 96
9696Now that you've connected Claude to a remote MCP server, you can explore its capabilities in your conversations. Try using the connected tools to automate tasks, access external data, or integrate with your existing workflows.
9797
9898<CardGroup cols={2}>
99 <Card title="Build your own remote server" icon="cloud" href="https://support.anthropic.com/en/articles/11503834-building-custom-connectors-via-remote-mcp-servers">
99 <Card title="Build your own remote server" icon="cloud" href="/docs/2025-11-25/develop/build-server">
100100 Create custom remote MCP servers to integrate with proprietary tools and
101101 services
102102 </Card>
docs/2026-07-28/develop/build-server Changed · +1 / -1 lines
from line 1067
10671067
10681068 When you start your client application, the auto-configuration will automatically create MCP clients from the claude\_desktop\_config.json.
10691069
1070 For more information, see the [MCP Client Boot Starters](https://docs.spring.io/spring-ai/reference/api/mcp/mcp-server-boot-client-docs.html) reference documentation.
1070 For more information, see the [MCP Client Boot Starters](https://docs.spring.io/spring-ai/reference/api/mcp/mcp-client-boot-starter-docs.html) reference documentation.
10711071
10721072 ## More Java MCP Server examples
10731073
docs/2026-07-28/develop/connect-remote-servers Changed · +2 / -2 lines
from line 19
1919With Custom Connectors, you can:
2020
2121* [Connect Claude to existing remote MCP servers](https://support.anthropic.com/en/articles/11175166-getting-started-with-custom-connectors-using-remote-mcp) provided by third-party developers
22* [Build your own remote MCP servers to connect with any tool](https://support.anthropic.com/en/articles/11503834-building-custom-connectors-via-remote-mcp-servers)
22* [Build your own remote MCP servers to connect with any tool](/docs/2026-07-28/develop/build-server)
2323
2424## Connecting to a Remote MCP Server
2525
from line 103
103103Now that you've connected Claude to a remote MCP server, you can explore its capabilities in your conversations. Try using the connected tools to automate tasks, access external data, or integrate with your existing workflows.
104104
105105<CardGroup cols={2}>
106 <Card title="Build your own remote server" icon="cloud" href="https://support.anthropic.com/en/articles/11503834-building-custom-connectors-via-remote-mcp-servers">
106 <Card title="Build your own remote server" icon="cloud" href="/docs/2026-07-28/develop/build-server">
107107 Create custom remote MCP servers to integrate with proprietary tools and
108108 services
109109 </Card>
docs/draft/develop/build-server Changed · +1 / -1 lines
from line 1067
10671067
10681068 When you start your client application, the auto-configuration will automatically create MCP clients from the claude\_desktop\_config.json.
10691069
1070 For more information, see the [MCP Client Boot Starters](https://docs.spring.io/spring-ai/reference/api/mcp/mcp-server-boot-client-docs.html) reference documentation.
1070 For more information, see the [MCP Client Boot Starters](https://docs.spring.io/spring-ai/reference/api/mcp/mcp-client-boot-starter-docs.html) reference documentation.
10711071
10721072 ## More Java MCP Server examples
10731073
docs/draft/develop/connect-remote-servers Changed · +2 / -2 lines
from line 19
1919With Custom Connectors, you can:
2020
2121* [Connect Claude to existing remote MCP servers](https://support.anthropic.com/en/articles/11175166-getting-started-with-custom-connectors-using-remote-mcp) provided by third-party developers
22* [Build your own remote MCP servers to connect with any tool](https://support.anthropic.com/en/articles/11503834-building-custom-connectors-via-remote-mcp-servers)
22* [Build your own remote MCP servers to connect with any tool](/docs/draft/develop/build-server)
2323
2424## Connecting to a Remote MCP Server
2525
from line 103
103103Now that you've connected Claude to a remote MCP server, you can explore its capabilities in your conversations. Try using the connected tools to automate tasks, access external data, or integrate with your existing workflows.
104104
105105<CardGroup cols={2}>
106 <Card title="Build your own remote server" icon="cloud" href="https://support.anthropic.com/en/articles/11503834-building-custom-connectors-via-remote-mcp-servers">
106 <Card title="Build your own remote server" icon="cloud" href="/docs/draft/develop/build-server">
107107 Create custom remote MCP servers to integrate with proprietary tools and
108108 services
109109 </Card>
examples Changed · +1 / -1 lines
from line 87
8787
8888Visit the [MCP Servers Repository (Resources section)](https://github.com/modelcontextprotocol/servers?tab=readme-ov-file#-resources) for a collection of other resources and projects related to MCP.
8989
90Visit our [GitHub Discussions](https://github.com/orgs/modelcontextprotocol/discussions) to engage with the MCP community.
90Visit our [GitHub Discussions](https://github.com/modelcontextprotocol/modelcontextprotocol/discussions) to engage with the MCP community.
9191