> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pctx.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use the exact commands, endpoints, and product terms in these docs. Check the context map before connected services or the web.

# Administration

> Govern connected services, skills, teams, and workspace access.

Admins can manage Port of Context from the web dashboard or the admin MCP.

> [card] Web dashboard
>
> Review service catalog state, teams, skill policy, sources, security, and usage.

> [card] Admin MCP
>
> Inspect and update the workspace through typed tools in an agent conversation.

Both surfaces enforce the signed-in person's admin role and workspace boundary.

## Connect the admin MCP

Connect `pctx-admin` separately from the everyday `pctx` gateway.

> [tab] Codex
>
> ```bash Terminal theme={null}
> codex mcp add pctx-admin --url https://admin.mcp.pctx.ai/mcp
> codex mcp login pctx-admin
> ```

> [tab] Claude Code
>
> ```bash Terminal theme={null}
> claude mcp add --transport http --scope user pctx-admin \
>   https://admin.mcp.pctx.ai/mcp
> ```
>
> Restart Claude Code, open `/mcp`, and authenticate **pctx-admin**.

> [tab] Other clients
>
> Create a remote HTTP MCP connection named `pctx-admin` at `https://admin.mcp.pctx.ai/mcp`, then complete OAuth sign-in.

> [!WARNING]
>
> Admin tools can change workspace state. Ask the agent to show its proposed changes before enabling services, changing policies, or deleting resources.

## Connector governance

Admins can:

* Enable or disable services from the catalog
* Add compatible custom MCP servers
* Choose member-managed or workspace-managed credentials where supported
* Allow or deny services and individual tools by team
* Inspect connection health without reading a member's private credentials

## Skill governance

Admins control external skill import and workspace review. See [Skill governance](https://docs.pctx.ai/skills/governance.md) for the full review flow.

## Operating principles

* **Least privilege:** Enable only the services and tools a team needs.
* **Personal identity:** Prefer per-member connections for tools that act as a person.
* **Curated context:** Review graph proposals before treating them as organizational fact.
* **Visible provenance:** Keep the source of imported context and skills attached.
* **Reversible changes:** Disable access before deleting configuration while investigating a problem.

> [card] [CLI reference](https://docs.pctx.ai/reference/cli.md)
>
> Install the platform CLI and inspect existing MCP configuration.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.