The TEC-CoWork MCP server (TEC-CoWork Connect) enables Gemini CLI to use the TEC-CoWork capabilities your organization has made available to you: Gmail read/search, Calendar list/create, Drive search/read, Gmail draft creation, shared MCP connections such as Notion, Linear, Slack, Stripe, Exa, and Context7, shared skills, and TEC-CoWork Cloud resources like skills, plugins, marketplaces, workers, members, roles, teams, and LLM providers. The server exposes only search_capabilities and execute_capability, so Gemini CLI searches what you can access and runs exact capability names instead of loading hundreds of tool definitions into context.

​
Server URL

OAuth sign-in uses your TEC-CoWork account, and the organization you pick is pinned into the token. If you do not have an account, create a free TEC-CoWork account.

​
Setup

  1. Add TEC-CoWork Connect as a remote HTTP MCP server:
  2. Start Gemini CLI:
  3. Authenticate TEC-CoWork inside Gemini:
  4. Finish the browser sign-in and choose your organization.

​
Switch organizations

Remove the stored MCP auth token for tec-cowork, then run /mcp auth tec-cowork again and choose the organization you want during browser sign-in.
This is a setup guide. These steps match TEC-CoWork Connect’s OAuth profile: HTTPS or HTTP loopback callbacks, PKCE S256, and dynamic client registration fallback. Gemini CLI is listed as setup only because native proof is not complete. See the client support status table.

​
What you can ask

  • “Which TEC-CoWork organization am I connected to?”
  • “Add omar@example.com to my organization.”
  • “Search my org’s capabilities for calendar tools, then list tomorrow’s events.”
  • “Create a skill that writes weekly status reports and share it with my whole organization.”

​
What’s next

  • Read the hub overview for OAuth, token, server exposure, and troubleshooting details.
  • Publish Notion, Linear, Slack, and other shared tools with shared MCP connections.