> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/user-guide/integrations/mcp/public-vs-private-mcp-servers.md).

# Public vs Private MCP Servers

### Overview

MCP servers generally fall into two categories: public and private. Public MCP servers are hosted by third parties and are often preconfigured for common APIs, making them easy to set up and quick to integrate for example, a GitHub MCP server for accessing repository data. Private MCP servers, on the other hand, run inside your own environment, such as Docker, Kubernetes, or a VM. While they require more setup and maintenance, they give you full control over access policies and security, which makes them especially suitable for handling sensitive or production-level data.

### Comparison

| Aspect          | Public MCP Server     | Private MCP Server    |
| --------------- | --------------------- | --------------------- |
| Setup           | Ready to use          | You manage deployment |
| Security        | Shared / less control | Full control          |
| Customizability | Limited               | Highly customizable   |

{% hint style="info" %}

#### Helpful Tools

* [**Waystation**](https://github.com/waystationai/waystation)**:** Discover, test, and manage MCP servers.
* [**Smithery**](https://smithery.ai/)**:** Browse and publish MCP servers with hosting options.

Both platforms support different authentication methods like API keys, OAuth, or environment variables.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.jetadmin.io/user-guide/integrations/mcp/public-vs-private-mcp-servers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.