What is MCP?
Model Context Protocol (MCP) is an open standard that lets AI assistants like Claude, chatgpt and other AI agents connect directly to external tools and services. Once connected, Claude can take actions inside Trupeer on your behalf, no copy-pasting, no tab-switching.
What can you do with the Trupeer MCP?
Search your Trupeer knowledge base
Ask LLM/agents any questions and get answers drawn directly from your Trupeer video docs and guides.
Find specific tutorials or walkthroughs
Locate the right video or document without manually browsing your library.
Look up onboarding materials
Quickly surface the right training content for new team members.
Video Search with Exact timestamps
Ability to search the video with exact timestamp basis on the queries.
Available MCP tools
| Tool | Description |
|---|
search_knowledge_base | Search for ranked results across your Trupeer knowledge base by keyword or phrase. |
answer_query_from_knowledge_base | Ask a natural-language question and get a synthesized answer with sources drawn from your knowledge base. |
Both tools are served over Streamable HTTP and secured with OAuth 2.0.
How to connect
Example — How to connect with Claude
2
Click Add integration and enter the following:NameTrupeerURLapi.trupeer.ai/mcp
3
Claude will prompt you to sign in to your Trupeer account via OAuth. Follow the on-screen steps.
4
Once connected, you can start using Trupeer tools in any Claude conversation.
Claude Code
Add Trupeer to your MCP config:
{
"mcpServers": {
"trupeer": {
"url": "api.trupeer.ai/mcp"
}
}
}Other AI Tools
You can manually connect to the Trupeer MCP using the public URL https://api.trupeer.ai/mcp as a custom connection.
Your AI tool must support:
- MCP client protocol using Streamable HTTP transport
- OAuth 2.0 authentication — the server uses browser-based OAuth (with RFC 9728 metadata discovery and bearer token validation), so your tool needs to be able to open a browser window for the user to sign in to Trupeer. After sign-in, the tool receives a bearer token to include in subsequent requests.
Each user authenticates individually through the browser OAuth flow. There is no API key or service account access method for MCP.
How can We connect to Glean MCP?
You can connect Trupeer's video knowledge into the Glean Enterprise Graph. This allows Glean to "read" your Trupeer tutorials and include them in company-wide search results.
Option A: Glean as the "Host" (Trupeer → Glean)
Use this if you want the Glean Assistant to find Trupeer videos.
1
In the Glean Admin Console, go to Platform > Actions.
2
Select New Action and choose Custom MCP Tool.
3
Enter the Trupeer MCP URL: https://api.trupeer.ai/mcp.
4
Configure authentication using OAuth 2.0 as detailed in the Technical Reference.
Option B: Unified Assistant (Claude + Both)
Connect both to a single assistant by updating your mcpServers config:
{
"mcpServers": {
"trupeer": { "url": "api.trupeer.ai/mcp" },
"glean": { "url": "https://[your-company]-be.glean.com/mcp/default" }
}
}
Example prompts to try
"Search my knowledge base for 'How to change colors for prototypes'."
"Find any guides about adding APIs with the client MCP."
"Using my docs, answer: how do I connect an ElevenLabs voice?"
"Summarize what our knowledge base says about onboarding new users."
Troubleshooting
MCP tools not working
If you're getting a message that your AI assistant can't access your Trupeer knowledge base or use the MCP tools, try re-authenticating.
Claude shows "No tools available"
3
Click the three-dot menu in the top-right.
5
Without refreshing the page or navigating away, choose Connect again and complete authentication.
💡 If you're on a Claude Team or Enterprise plan, you may need a workspace admin to disconnect and reconnect Trupeer for you.
"Unauthorized: user has not created a Trupeer account yet"
If you see this error after completing the OAuth sign-in flow, you may have authenticated with a different email address than the one your Trupeer account is registered under.
To check which email your Trupeer account uses, open the Trupeer app and go to Settings (⌘ + , on macOS, Ctrl + , on Windows). Your account email is shown under your profile picture in the top left.
When reconnecting MCP, make sure you sign in with that same email address during the OAuth flow.
FAQ
Do I need a Trupeer account?+
Yes, an active account and an existing Knowledge Base (KB) are required.
Can I use a different email for my AI tool?+
Yes. You will be asked to authenticate specifically with your Trupeer credentials during setup.
Is there a rate limit?+
Yes, there is a limit of 100 requests per minute.
Do I have to use the same email address for my AI tool and Trupeer?+
No, you can use different accounts for your AI tool and Trupeer. You'll authenticate the Trupeer account you want your AI tool to have access to. To verify which email your Trupeer account uses, open the Trupeer app and go to Settings (⌘ + , on macOS, Ctrl + , on Windows) — your account email is shown under your profile picture in the top left.
Can I connect Trupeer MCP to my own internal AI tool?+
Yes — any tool that implements the MCP client specification with Streamable HTTP transport can connect to Trupeer MCP. Your tool will need to handle the OAuth 2.0 browser authentication flow (including RFC 9728 metadata discovery) so that each user can sign in to their Trupeer account. See the "Other AI tools" section above for technical details. If you're building a custom integration and need help, reach out to support@trupeer.ai.
Technical reference
MCP endpoint
https://api.trupeer.ai/mcpTransport: Streamable HTTP · Auth: OAuth 2.0 with RFC 9728 metadata discovery and bearer token validation
Rate limits
| Plan | Rate Limit |
|---|
| All plans | 100 requests per minute |
If you exceed the rate limit, you'll receive a 429 Too Many Requests response. Wait until the next minute window to resume.
Authentication flow
1
The client discovers OAuth metadata via RFC 9728 (.well-known/oauth-authorization-server).
2
The user is redirected to a browser window to sign in to their Trupeer account.
3
After sign-in, the client receives a bearer token to include in the Authorization header of subsequent MCP requests.
4
Tokens are validated on the server using Trupeer's existing JWT validation logic.
There is no API key or service account authentication method — each user authenticates individually.
Available tools
search_knowledge_baseSearches the knowledge base for ranked results by keyword or phrase.
{ "query": "how to record a video with Trupeer" }Returns: Ranked list of results with URL, title, and excerpt.
answer_query_from_knowledge_baseAnswers a natural-language question using knowledge base content.
{ "query": "How do I add an AI avatar to my Trupeer video?" }Returns: Synthesized answer with source references (page URL, title, path). When the source is video-backed, also returns a videoUrl with startTime/endTime in milliseconds for deep-linking to the relevant clip.
Knowledge base lookup behavior
If a specific knowledge base ID (kbID) is not provided in a tool call, the MCP layer will automatically look up the knowledge base using the authenticated user's ownerID. This means users can query their knowledge base without needing to know or supply their kbID explicitly.
