MCP ServerResources
Process Trace
Follow execution flows through your code
See the exact sequence of function calls in an execution flow.
URI
map://{repository}/process/{process_id}Response
{
"id": "proc_login",
"label": "UserLogin",
"process_type": "cross_community",
"communities": ["API", "Authentication", "DataAccess"],
"trace": [
{ "step": 1, "name": "handleLoginRequest", "location": "src/api/auth.ts:45" },
{ "step": 2, "name": "authenticateUser", "location": "src/auth/authenticate.ts:67" },
{ "step": 3, "name": "getUserByEmail", "location": "src/data/users.ts:23" },
{ "step": 4, "name": "createSession", "location": "src/auth/session.ts:89" }
],
"related": [
{ "id": "proc_signup", "label": "UserSignup" }
]
}Key Fields
| Field | Description |
|---|---|
process_type | intra_community (localized) or cross_community (wider impact) |
communities | Which communities this process touches |
trace | Ordered function calls with file locations |
related | Similar processes sharing entry points |
Usage
Ask your agent:
"Trace the login process"
"Which communities does this process touch?"
"What processes are similar to the signup flow?"
Related
- Community Detail - Find process IDs
- Cypher Query - Query process steps