# feat\(pi\): inject the T3 MCP server into Pi sessions · stienswout/t3code

[View on GitCafe](https://git.cafe/stienswout/t3code/commit/ee5c83395f708b833aa3b6880cd77eea0aec9e36)

Repository: [stienswout/t3code](https://git.cafe/stienswout/t3code)

Visibility: public

Requested revision: ee5c83395f708b833aa3b6880cd77eea0aec9e36

Requested commit: ee5c83395f708b833aa3b6880cd77eea0aec9e36

Commit: ee5c83395f708b833aa3b6880cd77eea0aec9e36

Tree: 5b51d84492474f43276783154ff7191011cd61e0

Author: Mike Olson

Committer: Wout Stiens

## Message

```
feat(pi): inject the T3 MCP server into Pi sessions

Pi core has no MCP client. V2 already minted a scoped t3-code bearer
before openSession. This writes a T3-owned extension into the server
cache and spawns pi --mode rpc --extension <that file> with T3_MCP_URL
and T3_MCP_BEARER_TOKEN. Each MCP tool is registered under its original
name. User launchArgs are preserved. The first turn receives the shared
orchestration instructions.

```

## Parents

- [f0c70b6f6e4be4e935d89c8734ca422fa26c9f90](https://git.cafe/stienswout/t3code/commit/f0c70b6f6e4be4e935d89c8734ca422fa26c9f90?format=markdown)

[Source at this commit](https://git.cafe/stienswout/t3code/tree/ee5c83395f708b833aa3b6880cd77eea0aec9e36?format=markdown)