#general
Hi i have been testing out archestra to see if it would fit our companies needs, but i have a couple of question i cant figure out.
1. When i create an mcp registry and attach it to a gateway is there a way of having for each user it's own "identity"/"credentials" that the mcp from the registry could connect to or do i need to register for each user its own mcp (example is linear mcp). The goal is that if user X uses the mcp gateway it will use the registered linear mcp with his credentials instead of a shared one. Would we register for each user it's own MCP of linear?
2. Is there anything on the roadmap for having more layers than organizational - team - personal? We would love to have nested teams/projects
👋2
6 repliesRead-only live mirror of Archestra.AI Slack
👋Join the discussion withAI enthusiasts!Hi i have been testing out archestra to see if it would fit our companies needs, but i have a couple of question i cant figure out.
1. When i create an mcp registry and attach it to a gateway is there a way of having for each user it's own "identity"/"credentials" that the mcp from the registry could connect to or do i need to register for each user its own mcp (example is linear mcp). The goal is that if user X uses the mcp gateway it will use the registered linear mcp with his credentials instead of a shared one. Would we register for each user it's own MCP of linear?
2. Is there anything on the roadmap for having more layers than organizational - team - personal? We would love to have nested teams/projects
👋2
6 replies
hey! welcome to the community. nice to meet you 👋
for #1 - you only need one Linear MCP registry entry.
tl;dr use the “Resolve at call time” credential option (docs).
basically each user would add their personal Linear connection (I imagine Linear is oauth based), and Agents / MCP gateways would authenticate with the calling-user's credentials (or prompt them to authenticate if they don't yet have a credential).
does that make sense?
regrading nested teams/projects. what would you use nested teams or projects for - organizing resources, access control, or something else?
could you tell me a bit more about your use-case?
Thanks for the quick reply and i will try out the "Resolve at call time"
For the nested teams the idea is the following:
we have within the company departements which have teams in there and those again have teams. Per departement this can go a couple layers deep or just one layer.
We would love to be able that a user is connected to one of those layers and from there can use the stuff connected to his layer but also the layers under him. See the image for a quick visual. We would love to be able to control skills, agents, knowledge bases per level.
It is hard to explain easily so please ask me anything if it does not make sense 🙂
hmm I think that makes sense.
so Skills assigned to the Client X team, wouldn't be visible to team members just in Client Y team (unless a user is explicitly in both teams (or a "super admin"))
but both Client X and Client Y teams could see skills assigned to "Project teams" team
Yes for skills, agents and mcp gateways.
This would resolve duplicating and creating allot of extra teams where a user has to be attached to multiple teams
👍1