scenario-team-admin

Use when administering a Scenario team from an agent through MCP: restricting which models a team or project can run (model access control, allowlist, blocklist), inviting or removing team and project members, changing roles, capping a member's Creative Unit spend, creating or deleting projects, auditing API keys and their roles or scopes, or attributing consumption per user or model. Keywords: governance, model control, consumption cap, spend limit, API key hygiene, team admin, enterprise.

Install

KitScout test notes

Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.

Similar tools

• to-spec 323,485 ★
  Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synt
• to-tickets 323,485 ★
  Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocki
• issue-triage 113,555 ★
  Triage Paperclip inbox issues that are stale, blocked, in-review, or assigned-but-not-progressing, and decide
• deck-guizang-editorial 107,474 ★
  OpenDesign's FY26 marketing plan: brand-to-pipeline — audience, offer, channel mix, and the launch calendar th
• flowai-live-dashboard-template 107,474 ★
  Team-management dashboard skill in the FlowAI aesthetic — three tabs (Team Members, Team Details, Activity Log