Streamtime

@streamtime list all roles in our organization and show me which ones have project management permissions

Based on your Streamtime organization, here are the roles configured: • **Project Manager** – Full project access, can create/edit jobs, assign resources • **Senior Designer** – Can view all projects, edit assigned jobs, limited admin access • **Junior Designer** – View-only on unassigned projects, edit access on assigned work • **Account Manager** – Client-facing access, can view financials and timelines • **Admin** – Full system access including billing and user management The Project Manager and Admin roles have the broadest project management permissions. Would you like details on a specific role's capabilities?

This example demonstrates the List Roles tool, which requires a valid API key with read access to organizational settings. Useful for auditing team permissions or onboarding new members. Note that role structures vary significantly between Streamtime accounts — your organization may have custom roles with different names and permission sets.

@streamtime get the details for our 'Senior Designer' role and tell me what access level it has for time tracking

Here are the details for the **Senior Designer** role (ID: role_8x4k2): **Permissions:** • Time Tracking: Full access — can log time to any assigned project • Job Management: Edit assigned jobs, cannot create new jobs • Resource Scheduling: View-only access to team calendar • Financial Data: Cannot view rates or project budgets • Client Portal: No access This role can track time against their assigned work but won't see billing rates or profitability metrics. Time entries are visible to Project Managers and Admins for approval.

This uses the Get Role tool, which requires knowing the role ID (typically obtained from List Roles first). Demonstrates how to drill into specific permission details. Be aware that Streamtime's permission model is granular — a role's capabilities depend on both its base permissions and any project-specific overrides your organization has configured.

@streamtime show me all saved segments for user ID 'usr_9m3p' and summarize what kinds of reports they typically run

User **usr_9m3p** (Sarah Chen) has 5 saved segments: 1. **Active Client Projects** – Filters for in-progress jobs with external clients 2. **Overdue Tasks This Week** – Tasks past deadline in the last 7 days 3. **My Billable Hours** – Personal time entries marked billable, grouped by project 4. **Design Team Capacity** – Resource allocation view for the design department 5. **Q1 Revenue Pipeline** – Jobs with estimated close dates in Q1, sorted by value Sarah appears to focus on operational reporting — tracking team workload, deadline adherence, and revenue forecasting. The segments suggest she's in a project management or team lead role.

This example pairs the List Saved Segments tool with AI synthesis to extract workflow insights. Requires the user ID (not email address) and read access to that user's saved views. Saved segments are personal to each Streamtime user — you can't modify another user's segments through the API, only view them if you have appropriate admin permissions.

When Streamtime wins for mid-sized creative shop resourcing

A 12-person design agency uses Streamtime to track who's booked on which client projects through the quarter. Before pitching a new retainer, the account lead needs to know if the team has 40 hours/week to spare in March. The List Roles tool pulls current team structure, then Get Role confirms each person's capacity tier. The MCP surfaces this in a Switchy thread where the whole BD team can see it and decide whether to pitch aggressively or push the start date. This works because Streamtime already holds the single source of truth for project assignments. If your agency runs resourcing in a spreadsheet or splits it across Asana and Harvest, the MCP can't help—you need consolidated data first. For shops already on Streamtime, this is the fastest way to get capacity answers into a shared decision thread.

Pull custom client views into standup without logging in

A 6-person production studio runs a Monday standup where they review active client projects by segment: broadcast work, social content, and post-production. Each segment is a saved filter in Streamtime that groups jobs by deliverable type. The List Saved Segments tool exposes those filters to the MCP, so the studio manager can ask Switchy to pull the broadcast segment and see which jobs are due this week. The team discusses blockers in the thread, tags the relevant producer, and moves on—no one opens Streamtime during the meeting. This scenario assumes you've already built meaningful segments in Streamtime; if your jobs aren't tagged or segmented, the MCP just returns a flat list of everything. For studios that rely on segment-based reporting, this cuts 5 minutes of tab-switching out of every standup.

Verify role setup before a contractor's first day

A 20-person marketing agency hires a freelance copywriter for a 3-month project starting Monday. The ops lead needs to confirm the contractor's Streamtime role is configured with the right permissions and hourly rate before kickoff. In a Switchy thread with the project manager and finance lead, the ops lead uses Get Organisation Details to confirm the correct Streamtime account, then Get Role to pull the contractor's role config. If the rate is wrong or the role is missing, the thread becomes the decision log for who fixes it and when. This works because Streamtime roles are the source of truth for billing and access. If your agency manages contractor rates in a separate system or doesn't use Streamtime roles consistently, the MCP won't catch mismatches. For agencies that do role-based onboarding in Streamtime, this is a 2-minute check that prevents billing errors downstream.