Skip to content

Commit 10648cc

Browse files
authored
Move registry contribution to the concepts page (#62)
1 parent bf16755 commit 10648cc

File tree

2 files changed

+24
-24
lines changed

2 files changed

+24
-24
lines changed

docs/toolhive/concepts/registry-criteria.md

Lines changed: 19 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,17 +5,32 @@ description: Criteria for adding MCP servers to the ToolHive registry
55

66
The ToolHive registry is a curated list of MCP servers that meet specific
77
criteria. We aim to establish a curated, community-auditable list of
8-
high-quality MCP servers through clear, observable, and objective criteria. Here
9-
are the criteria for adding an MCP server to the ToolHive registry:
8+
high-quality MCP servers through clear, observable, and objective criteria.
109

11-
## Heuristics
10+
## Contribute to the registry
11+
12+
If you have an MCP server that you'd like to add to the ToolHive registry, you
13+
can
14+
[open an issue](https://github.com/stacklok/toolhive/issues/new?template=add-an-mcp-server.md)
15+
or submit a pull request to the ToolHive GitHub repository. The ToolHive team
16+
will review your submission and consider adding it to the registry.
17+
18+
Criteria for adding an MCP server to the ToolHive registry are outlined below.
19+
These criteria ensure that the servers in the registry meet the standards of
20+
security, quality, and usability that ToolHive aims to uphold.
21+
22+
Registry entries are defined in the
23+
[`pkg/registry/data/registry.json`](https://github.com/stacklok/toolhive/blob/main/pkg/registry/data/registry.json)
24+
file in the ToolHive repository.
25+
26+
## Criteria for MCP servers
1227

1328
### Open source requirements
1429

1530
- Must be fully open source with no exceptions
1631
- Source code must be publicly accessible
1732
- Must use an acceptable open source license (see
18-
[Acceptable licenses](#acceptable-licenses) below)
33+
[Acceptable licenses](#acceptable-licenses))
1934

2035
### Security
2136

docs/toolhive/guides-cli/registry.md

Lines changed: 5 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -3,9 +3,11 @@ title: Explore the registry
33
description: How to use the built-in registry to find MCP servers.
44
---
55

6-
ToolHive includes a built-in registry of MCPs with verified configurations,
7-
allowing you to discover and deploy MCP servers effortlessly. Simply select one
8-
from the list and run it securely with a single command.
6+
ToolHive includes a built-in registry of MCP servers with verified
7+
configurations that meet a
8+
[minimum quality standard](../concepts/registry-criteria.md), allowing you to
9+
discover and deploy high-quality tools effortlessly. Simply select one from the
10+
list and run it securely with a single command.
911

1012
## Find MCP servers
1113

@@ -174,23 +176,6 @@ thv config unset-registry-url
174176

175177
This restores the default behavior of using ToolHive's built-in registry.
176178

177-
## Contribute to the registry
178-
179-
If you have an MCP server that you'd like to add to the ToolHive registry, you
180-
can
181-
[open an issue](https://github.com/stacklok/toolhive/issues/new?template=add-an-mcp-server.md)
182-
or submit a pull request to the ToolHive GitHub repository. The ToolHive team
183-
will review your submission and consider adding it to the registry.
184-
185-
Criteria for adding an MCP server to the ToolHive registry are outlined in
186-
[Registry criteria](../concepts/registry-criteria.md). These criteria ensure
187-
that the servers in the registry meet the standards of security, quality, and
188-
usability that ToolHive aims to uphold.
189-
190-
Registry entries are defined in the
191-
[`pkg/registry/data/registry.json`](https://github.com/stacklok/toolhive/blob/main/pkg/registry/data/registry.json)
192-
file in the ToolHive repository.
193-
194179
## Next steps
195180

196181
See [Run MCP servers](./run-mcp-servers.mdx) to run an MCP server from the

0 commit comments

Comments
 (0)