# MCP servers

Register MCP servers with Straza, hold their credentials and decide which role reaches which tool.


- [Add a server](https://docs.straza.ai/guides/serve-mcp-apps/add-a-server/index.md) registers an MCP server, checks its connection and gives a role access to its tools.
- [Credentials](https://docs.straza.ai/guides/serve-mcp-apps/credentials/index.md) chooses who supplies an upstream server's credential and stores one shared secret for it.
- [Each caller's own credential](https://docs.straza.ai/guides/serve-mcp-apps/caller-credentials/index.md) lets each person reach an upstream server with their own token or sign-in.
- [Access per role](https://docs.straza.ai/guides/serve-mcp-apps/catalogs-per-role/index.md) gives a role access to selected tools and previews what its sessions see.
- [Limit a role to some objects](https://docs.straza.ai/guides/serve-mcp-apps/limit-a-role-to-some-objects/index.md) 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](https://docs.straza.ai/guides/serve-mcp-apps/git-through-straza/index.md) 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](https://docs.straza.ai/guides/serve-mcp-apps/show-views/index.md) 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](https://docs.straza.ai/guides/serve-mcp-apps/gitops-apps-directory/index.md) 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.


- [Add a server](https://docs.straza.ai/guides/serve-mcp-apps/add-a-server/index.md): Register an MCP server, check that Straza reaches it, and give a role access to its tools.
- [Credentials](https://docs.straza.ai/guides/serve-mcp-apps/credentials/index.md): Store one shared secret for an MCP server, so the gateway adds it to every call and no agent ever sees it.
- [Each caller's own credential](https://docs.straza.ai/guides/serve-mcp-apps/caller-credentials/index.md): Each person reaches an upstream MCP server with their own token or sign-in, and you decide what agents run on.
- [Access per role](https://docs.straza.ai/guides/serve-mcp-apps/catalogs-per-role/index.md): One application role reaches chosen tools of one MCP server, and you have read what its sessions see and why.
- [Limit a role to some objects](https://docs.straza.ai/guides/serve-mcp-apps/limit-a-role-to-some-objects/index.md): Pin the repositories ghapp reaches, give Straza its listing credential, then give each role the repositories it covers, so an agent with write tools writes only where one of its roles allows.
- [Git through Straza](https://docs.straza.ai/guides/serve-mcp-apps/git-through-straza/index.md): Let agents run plain git against GitHub with no GitHub credential on their machines, while Straza decides each fetch and push on ghapp with the roles, repositories and approvals of any tool call.
- [Show MCP Apps views](https://docs.straza.ai/guides/serve-mcp-apps/show-views/index.md): Let one MCP server show its interactive views in a chat app, with every click decided, held or refused like any other tool call.
- [The apps directory](https://docs.straza.ai/guides/serve-mcp-apps/gitops-apps-directory/index.md): A manifest file you keep under version control proposes a draft, a person publishes it, and deleting the file proposes the server's removal.
