Skip to main content
The pctx MCP server gives an agent a single entry point to the context map, connected services, and indexed sources in your workspace.

​
What the gateway exposes

Context map

People, teams, systems, repositories, customers, and their relationships.

Connected services

Tools from services enabled by the workspace and connected by the current person.

Indexed sources

Document collections searched by meaning across one or more sources.

Workspace guidance

Instructions that tell the agent which sources to check and in what order.
The gateway reflects the signed-in person’s access. It does not turn one person’s provider connection into a shared credential.

​
How an agent finds an answer

1

Resolve the subject

Identify the relevant person, team, system, repository, or domain in the context map.
2

Collect local context

Retrieve ownership, relationships, indexed sources, and connected services around that subject.
3

Use the right source

Search documents or call a connected service only when the curated context is not enough.
A service can return data. The context map tells the agent what that data means, who owns it, and where to look next.

​
Tool discovery

The gateway advertises only the tools available to the current person and workspace. The list changes when:
  • An admin enables or disables a connected service
  • A person connects or disconnects a provider account
  • A team access rule changes
  • An indexed source becomes available
When code mode is enabled, the agent can batch typed calls and keep large intermediate results outside the model’s context window.

​
Endpoints

Both endpoints use remote HTTP MCP with OAuth.

Next: Context map

Model the organization so agents know what exists and how it relates.