Skip to content

Commit 138e8f7

Browse files
committed
formatting
1 parent 559475f commit 138e8f7

1 file changed

Lines changed: 3 additions & 0 deletions

File tree

seps/2084-primitive-groups.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -29,6 +29,7 @@ Groups are named collections of MCP primitives: tools, prompts, resources, tasks
2929
Organizing a server's primitives by functionality or use case enables richer client workflows, wherein certain operations or settings can be applied to multiple primitives concurrently. Some use cases identified by the community include:
3030

3131
#### Client-Side & User Organization
32+
3233
- **Client-side Filtering:** Client UIs could display a list of groups and allow users to select/deselect specific groups to interact with or ignore. Primitives from deselected groups would not be presented to the LLM.
3334

3435
- **Library Management:** Enabling users to create and manage organized Prompt and Resource libraries that can be shared or reused across different sessions.
@@ -38,13 +39,15 @@ Organizing a server's primitives by functionality or use case enables richer cli
3839
- **Workflow-Specific Context:** Providing a model with a "set" of tools and tasks specifically curated for a particular workflow, rather than overwhelming it with every available primitive.
3940

4041
#### Server-Side & Architectural Patterns
42+
4143
- **Gateway Facades:** Using a Gateway Server to wrap various backend services (REST APIs, databases, or legacy systems) into a single cohesive facade. For example, a group might dynamically expose a mix of tools from different MCP servers, APIs, REST services, etc.
4244

4345
- **Dynamic Orchestration:** Supporting the ability to add or remove groups and tools without restarting the server, which is essential for high-availability gateway environments.
4446

4547
- **Task Management:** Grouping the new Task primitive alongside tools and prompts to manage long-running workflows, sequencing, and concurrency.
4648

4749
#### Governance & Development Lifecycle
50+
4851
- **Governance and Security:** Providing a standardized mechanism for server-side governance of who can access specific sets of tools and resources.
4952

5053
- **Ecosystem Tooling:** Supporting broader developer workflows such as debugging, automated testing, and documentation by grouping related diagnostic tools together.

0 commit comments

Comments
 (0)