How to Connect Trybe to Microsoft Copilot via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Trybe, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

Trybe + Microsoft Copilot

Trybe performance-based UGC platform for brands: the creator roster and sample obligations, creator performance (earnings, GMV, ad spend, purchases and ROAS across Meta, TikTok and AppLovin) and the videos creators submit. Submission reviews are included, installed switched off.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

TRYBE_API_KEY

Step 1 — Get credentials

Setting up takes about 2 minutes. You need a Trybe brand account with Brand API access and a brand API key.

1. API access is a feature of the brand account. If every call answers 403 feature_not_enabled, ask your Trybe contact to enable the Brand API for your brand.
2. Create an API key for your brand in the Trybe brand portal, or ask your Trybe contact for one. It starts with tk_live_. Paste it into TRYBE_API_KEY.
3. Install the connector and run trybe_list_creators to check the key.

The key is sent as Authorization: Bearer tk_live_... and sees only your brand.

What it reads: the active creators of your brand, newest first, with their sample status at your brand (samples requested, approved, fulfilled and overdue, the sample to act on and the Sample Score), filterable by sample_obligation=overdue to find who owes a video; one creator's programs with their commission rules, e.g. 10% of GMV plus a flat amount per order; creator performance for a period (programs, last activity, earnings, Trybe conversions and GMV, new and active submissions, ads running their content, ad spend, purchases, purchase value and ROAS), ranked with sort_by or limited to one creator, one program or Meta, TikTok and AppLovin with platforms; and the content creators submit, video or image, with status (pending, approved, rejected, revision_requested), creator, program, products, angles, transcript, all-time ad usage, thumbnail and a download link. status=pending gives the review queue, and query finds videos that say a word.

Switched off at install: trybe_approve_submission, trybe_reject_submission and trybe_request_submission_revision, which needs a comment telling the creator what to change. The creator is notified at once and approval affects what they earn, so an administrator turns these on deliberately. Even then the AI shows you the submission and the comment and waits for your yes.

Reading the numbers: money fields end in _cents and are USD cents (spend_cents 250000 is 2,500.00 USD). Dates are UTC calendar days YYYY-MM-DD, and end_date cannot be in the future. Without dates, performance covers the last 30 complete UTC days; sorting by a metric or active_only=true caps the window at 90 days. roas is purchase value divided by spend, null without spend. A creator's samples block of zeros means no samples, while null means it could not be read on that request, so the AI retries instead of reading it as none.

Ids and ads: creators are creator_<uuid>, programs creator_program_<uuid>, submissions submission_<uuid>, products product_<uuid> and groups subgroup_<uuid>, used exactly as returned. A submission's trybe_id (its last 8 characters) must appear on the destination URL and ad name of every ad built from it: that is how Trybe attributes ads and pays creators.

Limits: lists return 20 rows by default and at most 100 (limit), and the AI pages with after = next_cursor while has_more is true. The API allows 300 requests per window and answers 429 rate_limit_exceeded above that. Download links in asset.url expire after about 20 minutes, so the AI fetches a fresh one instead of storing it.

Common errors: 401 invalid_api_key means a missing or wrong key. 403 feature_not_enabled means the Brand API is not enabled for your brand. 400 validation_error names the bad parameter, e.g. a start date after the end date. 404 on one id means it does not exist or belongs to another brand.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Microsoft Copilot

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Microsoft Copilot uses MCP servers through agents built in Copilot Studio: you add AnythingMCP to an agent as a tool, then publish the agent to Microsoft 365 Copilot and Teams. Copilot Studio connects from Microsoft's cloud over Streamable HTTP, which AnythingMCP supports.

1. In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
2. Enter a Server name (for example AnythingMCP), a Server description that says what the connector does, and the Server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server.
3. Under authentication, choose API key, set Type to Header and the header name to X-API-Key, then select Create.
4. In Add tool, choose Create a new connection, paste an MCP API key from AnythingMCP (MCP Servers → your server → API keys) and select Add to agent.
5. Try it in the agent's Test pane: ask for something that needs the Trybe tools.
6. Select Publish, then Channels → Microsoft 365 and Microsoft Teams, keep Make agent available in Microsoft Copilot selected and choose Add channel. See agent in Teams installs it for you; in Microsoft 365 Copilot, type @ and pick the agent.

Prefer per-user sign-in? Choose OAuth 2.0 → Dynamic discovery instead of an API key: each user then signs in to AnythingMCP the first time the agent calls it.

Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Copilot Studio connects from Microsoft's cloud, so localhost does not work.

Available tools

Example prompts

• "Which creators owe us a video right now? List them with their overdue samples."
• "Rank our creators by purchase value over the last 30 days and show spend and ROAS for each."
• "How did our creators perform on TikTok last month? Show earnings, ad spend and purchases."
• "List the pending submissions and summarise the transcript of each one."
• "Find submissions that mention free shipping and tell me how often ads have used them."

FAQ

Which Copilot is this for? Microsoft 365 Copilot at work, through agents built in Copilot Studio. The Microsoft Copilot app for personal accounts has no option to add your own MCP server.

What do I need? A work account with access to Copilot Studio (a license or a trial) to build the agent. People who use it in Microsoft 365 Copilot or Teams need access to the agent: share it with them, or ask an admin to publish it to the organization. If your organization applies data policies to Power Platform connectors, they cover MCP servers too.

The agent doesn't call the tools. Check that the header name is exactly X-API-Key and that the key belongs to the same MCP server as the URL, and make the server description specific: Copilot Studio uses it to decide when to call the server. Publish the agent again after each change; in an open chat, type "start over" to get the new version.

Next steps

• Connector landing page
• Connect to Claude
• Connect to ChatGPT
• Connect to Cursor
• Connect to Gemini
• Connect to Meta Muse