The TEC-CoWork MCP server (TEC-CoWork Connect) enables Zed 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 Zed 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

Add this to Zed settings.json:
mcp-remote handles the browser OAuth on an HTTP loopback callback, which TEC-CoWork accepts.

​
Switch organizations

Remove the stored MCP auth token for tec-cowork, then restart the server 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. Zed 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?”
  • “Assign Priya to the Sales team.”
  • “Search my org’s capabilities for calendar tools, then list tomorrow’s events.”
  • “Find the Q3 launch page in Notion and summarize it.”

​
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.