MCP servers
Register MCP servers with Straza, hold their credentials and decide which role reaches which tool.
- Add a server registers an MCP server, checks its connection and gives a role access to its tools.
- Credentials chooses who supplies an upstream server’s credential and stores one shared secret for it.
- Each caller’s own credential lets each person reach an upstream server with their own token or sign-in.
- Access per role gives a role access to selected tools and previews what its sessions see.
- Limit a role to some objects pins the repositories a server such as ghapp reaches and gives each role the repositories it covers, so an agent writes only where one of its roles allows.
- Git through Straza lets agents run plain git against GitHub with no credential on their machines, while Straza decides each fetch and push on ghapp like a tool call.
- Show MCP Apps views lets a chat app render a server’s interactive views through the server’s own endpoint, with every click decided like any other tool call.
- The apps directory keeps server manifests in a directory under version control, where a file proposes a draft that a person publishes.
Registering a server makes none of its tools visible to a person or an agent. A session lists and calls them only after a role it holds has access.