Connect your AI assistant to real team context.
WorkBeam exposes a secure Model Context Protocol server so Cursor, Claude, VS Code, Windsurf, and other clients can answer questions from your team's actual work: projects, meetings, workflows, knowledge, and productivity signals.
MCP Setup
Three steps from WorkBeam API key to an AI assistant with live team context.
Server configuration
Use the WorkBeam MCP endpoint with a bearer token generated from your API Keys page. Your assistant only gets the data available to that account and key.
https://ai.workbeam.ai/mcp/team-informationClient JSON
replace token before use{
"mcpServers": {
"workbeam-team-information": {
"url": "https://ai.workbeam.ai/mcp/team-information",
"headers": {
"Authorization": "Bearer tx_your_api_key_here"
}
}
}
}Need the complete product setup flow? Start with the WorkBeam setup guide, then return here to connect MCP.
What your assistant can do
MCP turns WorkBeam into a live context source for AI tools, without manual copy-paste.
Scoped by your account
MCP access follows the same account and team boundaries as WorkBeam. API keys are revocable, and the token should be treated like a password.
Built for grounded answers
Assistants can retrieve WorkBeam context instead of relying on stale prompts or copied snippets. For privacy details, read the WorkBeam data policy.
Keep exploring
Learn how WorkBeam captures context, compare plans, or jump back to the homepage MCP section.