pctx gateway.
Workspace access and personal access
Port of Context separates service availability from personal authorization.1
An admin enables the service
The service becomes available in the workspace catalog. Team policies can narrow who may use it.
2
Each person connects their account
Members sign in from the Connections page. One person’s provider session is never shared with another.
3
The gateway exposes allowed tools
The next MCP request resolves the current catalog, connection state, and access rules.
Authentication types
Custom MCP servers
Admins can add a compatible remote MCP server to the workspace catalog. A custom server follows the same user and team controls as built-in services. Prepare these values before adding one:- A stable lowercase slug and user-facing name
- The remote MCP endpoint
- An authentication method
- A category that tells members what the server is for
If a source has a queryable API or MCP server, connect it. If it is a document set with no query API, publish it as an indexed source.
Change access
- Disable a service to remove its tools from the workspace.
- Use team rules to allow or deny a service or individual tool.
- Disconnect a personal account to revoke that member’s provider access.
Next: Indexed sources
Make document collections searchable by meaning through the gateway.