# ClosedMCP

> ClosedMCP is one MCP connection to the tools a company allows each person. Every call runs as the signed-in person and is audited. Companies can also have ClosedMCP host MCP servers they write (Serverless MCPs).

These pages are plain markdown, the same text the `closedmcp_guide` MCP tool returns for each topic.

## Docs

- [Using ClosedMCP](https://closedmcp.com/docs/basics.md): find tools, connect apps, why a tool is missing or denied (topic `basics`)
- [Serverless MCPs](https://closedmcp.com/docs/serverless.md): build, test and publish an MCP server that ClosedMCP hosts (topic `serverless`)
- [The ClosedMCP library](https://closedmcp.com/docs/library.md): the headers a hosted app receives and the `_meta` keys it returns (topic `library`)
- [Event channels](https://closedmcp.com/docs/event-channels.md): let an AI agent wait for events from a hosted app (topic `channels`)
- [Monitors](https://closedmcp.com/docs/monitors.md): scripts that check tools on a timer and wake an agent; being rolled out (topic `monitors`)

## Optional

- [Documentation](https://closedmcp.com/docs): guides for people
- [SDK reference](https://closedmcp.com/docs/sdk): Log in with ClosedMCP SDKs for MCP servers you host yourself